Support a version to live published per release
Bug #1463872 reported by
Sergio Schvezov
on 2015-06-10
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | Software Center Agent |
Undecided
|
Unassigned | ||
Bug Description
Phrased in the form of a question:
if I have snappy package N available for release X and X+1, upload N+1 and only tag it for X+1, what happens to N that was on X?
Ideally N on X would still be available and not all of the sudden in a fake unpublished state.
To post a comment you must log in.
This behaviour was based on the framework spec where we wanted to avoid developer neglecting old versions for his packages when they moved to a new framework.
If we want a different semantic for releases, we'll need to define how releases with play with channels. Added his item to Online Services backlog.