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

2017-12-16 Thread Clint Byrum
Excerpts from Thomas Goirand's message of 2017-12-15 16:15:04 +0100: > On 12/14/2017 12:44 AM, Clint Byrum wrote: > > We can take stock of the intermediate releases over the last year, and make > > sure they all work together once a year. Chris Jones mentioned that we > > should > > give users

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

2017-12-16 Thread Matt Riedemann
On 12/16/2017 5:51 AM, Kashyap Chamarthy wrote: 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

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

2017-12-16 Thread Kashyap Chamarthy
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

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

2017-12-16 Thread Kashyap Chamarthy
On Fri, Dec 15, 2017 at 10:11:24AM +0800, Zhenyu Zheng wrote: > On Thu, Dec 14, 2017 at 7:02 PM, Kashyap Chamarthy > wrote: [...] > > For a relatively mature (~7 years; and ~5 years if we count from the > > time governance changed to OpenStack Foudation) project, one