On Fri, Aug 21, 2015 at 11:35:50AM -0700, Steve Langasek wrote: > This all sounds completely reasonable to me. Thanks for letting us > know.
Great! Thank you for confirming. > At some point during the release cycle I imagine you'll want to start using > the SRU process anyway instead of pushing into release, so that you have the > added flexibility and protection of -updates in the event of regressions. I > assume you will let us know when you get to that point, if you need to do > any uploads of juju-core in this window before the release. If I understand you correctly, I think we have the flexibility/protection you suggest by virtue of our current process, which doesn't need the -updates pocket during the development release at all. Please could you confirm? The original thread discussing this is at [1], but here's a summary of what we're doing based on that thread: We've been using the 'block-proposed' tag in our tracking bugs, thus holding the upload (the proposed upstream release) in the -proposed pocket in the development release in combination with holding the update in the -proposed pocket in stable releases as part of the normal SRU verification process. Then, if any tests fail (eg. SRU verification failure), the idea is that upstream won't release that particular version at all (burning the upstream version number) and we won't have regressed anything. We can fail the SRU process and continue to block proposed migration in the development release until we have a newer proposed release from upstream ready. If tests pass, then upstream release and then we remove 'block-proposed' and add 'verification-done'. In practice due to sponsorship delays we often don't have uploads ready before upstream have released quite yet, but we hope to close this gap soon. In the meantime it doesn't actually make any difference in Ubuntu since if necessary we would still fail SRU verification and development release proposed migration after testing anyway. Once we've closed the gap then upstream releases will be more closely synced to availability in the Ubuntu archives (both development and stable -updates pockets). [1] https://lists.ubuntu.com/archives/ubuntu-release/2014-October/003041.html -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
