On Thu, Dec 14, 2017 at 12:02:13PM +0100, Kashyap Chamarthy wrote:
> On Wed, Dec 13, 2017 at 05:17:26PM +0100, Thierry Carrez wrote:
[...]
> > What it means:
> >
> > - We'd only do one *coordinated* release of the OpenStack components
> > per year, and maintain one stable branch per year
Thinking a bit more, the above reminds of this[*] by DanPB a couple of
years ago, where Dan's 'Modest Proposal' was: "switch to a development
cycle that is exactly 2 months".
But one pontential question that comes to mind from that old thread is
how is this new proposal of 'one coordinated release per year' going to
address the following:
If your spec didn't make into this year's coordiated release, then
does it have to 'sit out' for one whole year?
The shorter release cycle argument addresses that by not coupling specs
to a single release -- where specs can be submitted regardless of a
release in question. Meanwhile, code development of the feature can
happen over several cycles. And periodically re-evaluate it in light of
new evidence and design discussions.
As it stands[2], this problem seems mitgated by moving specs across
releases and re-approving them (insofar as they make sense). Maybe in
current times, the above specs issue is 'non-problem'. Happy to be
corrected.
[1] http://lists.openstack.org/pipermail/openstack-dev/2015-February/057614.html
-- Re-evaluating the suitability of the 6 month release cycle
[2] https://specs.openstack.org/openstack/nova-specs/readme.html
--
/kashyap
__________________________________________________________________________
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
