Excerpts from Chris Jones's message of 2017-12-13 19:25:03 +0000: > Hey > > On 13 December 2017 at 17:31, Thierry Carrez <thie...@openstack.org> wrote: > > > See attached for the PDF strawman the release team came up with when > > considering how that change would roll out in practice... > > > > [in which the final stage of the release is 8 weeks, therefore shorter than > the other 10/11 week stages] > > I'm not going to go on about this beyond this mail, since I've been roundly > shot down about this before, but please could we have the gap between the > final milestone and the release, be longer? Every extra week there is more > release quality :) >
I want to believe that is true. However I have no real evidence that it is. What class of users runs RC's in OpenStack? With narrower scoped projects, running RC's is pretty common. If you're a PHP shop, you might have automated testing setup to test your code with the RC so you can upgrade sooner. But you might not bother to run RC's of MySQL, because you're happy with the feature set and comfortable with the amount of time the release you're running is supported. However, with OpenStack's "upgrade all the things" approach to coordinated releases and testing, this becomes a much higher bar for running an RC. My somewhat educated guess is that our automated CI is about the only thing beyond a few developers testing their own new features that will run this code before it is released. __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev