Re: [openstack-dev] [release] Proposal to change the timing of Feature Freeze

2017-05-20 Thread Chris Jones
Hey Well, it definitely seems like there's not much support for the idea ;) Thanks everyone who replied. I'll go away and think about ways we can improve things without moving FF :) Cheers, -- Chris Jones > On 18 May 2017, at 11:18, Thierry Carrez wrote: > > Chris

Re: [openstack-dev] [release] Proposal to change the timing of Feature Freeze

2017-05-18 Thread Thierry Carrez
Chris Jones wrote: > I have a fairly simple proposal to make - I'd like to suggest that > Feature Freeze move to being much earlier in the release cycle (no > earlier than M.1 and no later than M.2 would be my preference). > [...] Hey Chris, From my (admittedly too long) experience in release

Re: [openstack-dev] [release] Proposal to change the timing of Feature Freeze

2017-05-17 Thread Matt Riedemann
On 5/17/2017 11:20 AM, Dmitry Tantsur wrote: On 05/17/2017 05:34 PM, Chris Jones wrote: Hey folks I have a fairly simple proposal to make - I'd like to suggest that Feature Freeze move to being much earlier in the release cycle (no earlier than M.1 and no later than M.2 would be my

Re: [openstack-dev] [release] Proposal to change the timing of Feature Freeze

2017-05-17 Thread Dmitry Tantsur
On 05/17/2017 05:34 PM, Chris Jones wrote: Hey folks I have a fairly simple proposal to make - I'd like to suggest that Feature Freeze move to being much earlier in the release cycle (no earlier than M.1 and no later than M.2 would be my preference). I welcome projects to experiment with

[openstack-dev] [release] Proposal to change the timing of Feature Freeze

2017-05-17 Thread Chris Jones
Hey folks I have a fairly simple proposal to make - I'd like to suggest that Feature Freeze move to being much earlier in the release cycle (no earlier than M.1 and no later than M.2 would be my preference). In the current arrangement (looking specifically at Pike), FF is scheduled to happen 5