In case people don't follow the OpenStack development mailing list, I'd like to 
point out a current discussion: 
http://lists.openstack.org/pipermail/openstack-dev/2017-December/125473.html

The discussion is about a possible move to a once per year release cycle for 
OpenStack with one Project Team Gathering (PTG) per year at the start of the 
release cycle. Individual OpenStack projects would be free to do intermediate 
releases, and the current use of milestones within a release would continue but 
with perhaps an 8 week spacing between milestones. The discussion also touches 
upon providing a longer interval for functional testing prior to release.

The OpenContrail TSC and/or GWG should discuss whether it would make sense to 
align the OpenContrail release cycle with the new OpenStack release cycle 
(assuming that OpenStack does move to the once a year model, right now it's 
just a mailing list discussion, I don't think it has been voted on yet by the 
OpenStack TC). Two possible options are to align OpenContrail functional 
testing and release candidates to the same time period as OpenStack and release 
at the same time, or to choose a fixed offset. For example, set OpenContrail 
release 2 or 4 weeks after OpenStack release.

Of course it's not necessary for OpenContrail to coordinate release schedule at 
all with OpenStack, but if OpenStack does move to a one release per year cycle 
it's at least worth discussing the pros and cons of aligning OpenContrail to 
the same calendar.

--
Paul Carver
VoIP: 732-545-7377
Cell: 908-803-1656
E: pcar...@att.com<mailto:pcar...@att.com>
Q Instant Message<qto://talk/pc2929>
It is difficult to make predictions. Especially about the future.


_______________________________________________
Dev mailing list
Dev@lists.opencontrail.org
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org

Reply via email to