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

Emmet Hikory persia at shipstone.jp
Wed Dec 13 18:26:42 UTC 2017

Dirk Müller wrote:

> 2017-12-13 17:17 GMT+01:00 Thierry Carrez <thierry at openstack.org>:
> > - We'd only do one *coordinated* release of the OpenStack components per
> > year, and maintain one stable branch per year
> > - We'd elect PTLs for one year instead of every 6 months
> > - We'd only have one set of community goals per year
> > - We'd have only one PTG with all teams each year
> Well, I assume there would still be a chance to have a mid-cycle PTG
> independent of the 1 year release schedule proposal if there
> is a need for it.

    I wonder if we may find it easier to take opinions on this if we separate the ideas of “we should only have one formal coordinated release a year, because teams are finding the cadence too fast to do the sort of work required in each release, and consumers are finding the cadence too fast to prepare downstream editions of each release” from “we should reduce the frequency of in-person meetings”.  From my perspective, both are important debates to have, and both potential decisions have wide-ranging consequences, but I find the conflation to distract from reasoned consideration of each.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20171213/dd376e30/attachment.html>

More information about the OpenStack-dev mailing list