Re: [openstack-dev] Continuous deployment - significant process change

2013-08-18 Thread Robert Collins
On 1 May 2013 08:12, Sean Dague s...@dague.net wrote: I think the reality is that openstack tree and process is very close to what the CD folks want. The only thing that's causing some allergy among the core teams is the idea of features coming in in an off state, versus coming in default on

Re: [openstack-dev] Continuous deployment - significant process change

2013-08-18 Thread Robert Collins
Just when you thought this had been forgotten On 1 May 2013 21:46, Thierry Carrez thie...@openstack.org wrote: Clint Byrum wrote: On 2013-04-30 14:52, Russell Bryant wrote: My biggest concern with this is applying it to an open source project with an unmanaged workforce. Thierry captured

Re: [openstack-dev] Continuous deployment - significant process change

2013-08-18 Thread Christopher Yeoh
On Mon, Aug 19, 2013 at 5:51 AM, Robert Collins robe...@robertcollins.netwrote: - Stable branch maintenance becoming harder. The set of proposals being made to tackle this are: - Set a much harder upper bound on commit size - we were saying 500 lines, but the recent research paper suggests

Re: [openstack-dev] Continuous deployment - significant process change

2013-08-18 Thread John Griffith
On Sun, Aug 18, 2013 at 9:10 PM, Christopher Yeoh cbky...@gmail.com wrote: On Mon, Aug 19, 2013 at 5:51 AM, Robert Collins robe...@robertcollins.net wrote: - Stable branch maintenance becoming harder. The set of proposals being made to tackle this are: - Set a much harder upper bound on

Re: [openstack-dev] Continuous deployment - significant process change

2013-08-18 Thread Robert Collins
On 19 August 2013 16:15, John Griffith john.griff...@solidfire.com wrote: This was pretty well discussed back in April and May IMO. It petered out with no firm consensus AFAICT. Those of us with CD experience are trying to debug the concerns those of us here without CD experience have, so that