Public bug reported:
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-heimdal:amd64 1.7~git20160703+dfsg-1 in
proposed, which is not in the release pocket because it is broken (see
bug 1617963).
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: ubuntu
Importance: Undecided
Status: Confirmed
** Tags: bot-stop-nagging
** Package changed: heimdal (Ubuntu) => ubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to heimdal in Ubuntu.
https://bugs.launchpad.net/bugs/1634201
Title:
Release process leaves stable -proposed with broken packages, breaking
users who volunteer to test stable -proposed for SRU verification
purposes
Status in Ubuntu:
Confirmed
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-heimdal:amd64 1.7~git20160703+dfsg-1
in proposed, which is not in the release pocket because it is broken
(see bug 1617963).
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?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1634201/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
