Excerpts from Ed Leafe's message of 2017-12-13 16:07:50 -0600: > On Dec 13, 2017, at 12:13 PM, Tim Bell <tim.b...@cern.ch> wrote: > > > There is a risk that deployment to production is delayed, and therefore > > feedback is delayed and the wait for the ‘initial bug fixes before we > > deploy to prod’ gets longer. > > There is always a rush at the Feature Freeze point in a cycle to get things > in, or they will be delayed for 6 months. With the year-long cycle, now > anything missing Feature Freeze will be delayed by a year. The long cycle > also means that a lot more time will be spent backporting things to the > current release, since people won’t be able to wait a whole year for some > improvements. > > Maybe it’s just the dev in me, but I prefer shorter cycles (CD, anyone?).
You're missing the key point that coupled with the change in the overall development cycle schedule we would be encouraging projects to release more often. I'd personally rather do away with milestones altogether and just tag everything monthly, but some projects may not be ready to do that and some may want to go more often (libraries in particular). Doug __________________________________________________________________________ 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
