Release process leaves stable -proposed with broken packages, breaking users who volunteer to test stable -proposed for SRU verification purposes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
During development, we have packages in -proposed that fail to migrate, as expected, for good reason.
At release time, these packages are still present. For example, Yakkety released with libhcrypto4-
I think we should be encouraging users to volunteer to risk testing proposed in stable releases. This helps with SRU verification.
However, our current release process breaks these users when they upgrade to a new release (which, given that they are testing the cutting edge, they are likely to do early, before the proposed pocket has been cleaned out).
This means that users, instead of being encouraged, are being discouraged from testing the SRU proposed pocket since we are breaking them with known bugs but delaying removal of those breakages.
How can we adjust our release process to stop this happening?
affects: | heimdal (Ubuntu) → ubuntu |
Status changed to 'Confirmed' because the bug affects multiple users.