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

Jay S Bryant jungleboyj at gmail.com
Wed Dec 13 17:25:04 UTC 2017


If we are reworking the schedule it is a good idea to leave more 
stabilization time at the end and try to wrap things up before the end 
of the year when people disappear.

As far as releases go ... other teams have been doing frequent 
intermediate releases and have benefited from it.  Just takes a bit more 
discipline and leadership from the PTL and Cores.


On 12/13/2017 11:21 AM, Sean McGinnis wrote:
> On Wed, Dec 13, 2017 at 04:49:24PM +0000, Jeremy Stanley wrote:
>> On 2017-12-13 16:45:14 +0000 (+0000), Chris Jones wrote:
>> [...]
>>> For me the first thing that comes to mind with this proposal, is
>>> how would the milestones/FF/etc be arranged within that year?
>> [...]
>> Excellent point. If it's not too much work for the Release team, it
>> would be very helpful to have a straw man release schedule for a
>> year-long Rocky so we can see what that might look like.
>> -- 
>> Jeremy Stanley
> We did map out a straw man schedule, but I don't currently have access to that.
> IIRC, we ended up on ~8 week periods between milestones. This actually worked
> quite well as far as common holidays and other breaks.
> But also keep in mind that the milestones would be somewhat "checkpoints" along
> the way. Teams would be encouraged to do releases through out the year as
> needed, with the once yearly one being a coordinated release to get everyone in
> sync.
> Sean
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

More information about the OpenStack-dev mailing list