[openstack-dev] [all] Switching to longer development cycles

Dmitry Tantsur dtantsur at redhat.com
Fri Dec 15 11:58:18 UTC 2017

On 12/15/2017 11:00 AM, Luigi Toscano wrote:
> ----- Original Message -----
>> On 12/14/2017 9:38 AM, Luigi Toscano wrote:
>>> And the QE in me says that there are enough moving parts around for the
>>> integration testing (because CD yes, but the resources are limited) that a
>>> longer cycle with a longer time between freeze and release is better to
>>> refine the testing part. The cycle as it is, especially for people working
>>> both upstream and downstream at the same time, is complicated enough.
>> Nothing in this proposal is talking about a longer time between feature
>> freeze and release, as far as I know (maybe I missed that somewhere).
> It does not talk about this. But I think that it does not make sense without that.
>> In that regard, the one year cycle does not make the release any more
>> stable, it just means a bigger pile of stuff dumped on you when you
>> finally get it and upgrade.
> Not if you commit to work on stabilization only (which in turn would allow us to be more confident that PASS jobs means that things are really working not just in DevStack).

If people could commit to work on stabilization only, we could do the same even 
with 3 months cycle. 2 months for features, 1 month for stabilization could 
actually work very well.

But so far 100% of people I've seen talking about stabilization only talked 
about it when it did not cut their features.

More information about the OpenStack-dev mailing list