Staging changes for future SRU landings

Julian Andres Klode julian.klode at canonical.com
Wed Aug 28 19:24:10 UTC 2019


On Wed, Aug 28, 2019 at 06:32:13PM +0100, Robie Basak wrote:
> Finally, please note that it is essential to carry out SRU verification
> on the bug as usual as soon as it enters proposed because we do not want
> to burden a future SRUer with verification of your bug. If timely
> verification is not performed, then as usual the "staged" upload is a
> candidate for deletion, and a future SRUer is quite entitled to base
> their upload on the version prior to your staged upload instead. If this
> happens, the future SRU will not include your changes.

Does this work sensibly, though? AFAIUI, the tools will set the bug
back to verification once you upload a follow up (at least if you
pass -v<version in -updates> to dpkg-buildpackage, which IIRC is
kind of expected, as otherwise bug closure emails end up weird).

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer                              i speak de, en
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/ubuntu-devel/attachments/20190828/8f1fcc9c/attachment.sig>


More information about the ubuntu-devel mailing list