Re: [openstack-dev] Gate breakage process - Let's fix! (related but not specific to neutron)

2013-08-18 Thread Joe Gordon
On Sat, Aug 17, 2013 at 9:46 AM, Robert Collins robe...@robertcollins.netwrote: On 17 August 2013 23:49, Salvatore Orlando sorla...@nicira.com wrote: I tend to agree that when the gate for a project is broken, nothing should be merged for that project until the gate jobs are green again.

Re: [openstack-dev] Gate breakage process - Let's fix! (related but not specific to neutron)

2013-08-17 Thread Salvatore Orlando
I tend to agree that when the gate for a project is broken, nothing should be merged for that project until the gate jobs are green again. In the case of Neutron, making the job non voting only caused more bugs to slip through, and that meant more works for the developer themselves, and more

Re: [openstack-dev] Gate breakage process - Let's fix! (related but not specific to neutron)

2013-08-17 Thread Joe Gordon
On Aug 17, 2013 7:52 AM, Salvatore Orlando sorla...@nicira.com wrote: I tend to agree that when the gate for a project is broken, nothing should be merged for that project until the gate jobs are green again. In the case of Neutron, making the job non voting only caused more bugs to slip

Re: [openstack-dev] Gate breakage process - Let's fix! (related but not specific to neutron)

2013-08-17 Thread Robert Collins
On 17 August 2013 23:49, Salvatore Orlando sorla...@nicira.com wrote: I tend to agree that when the gate for a project is broken, nothing should be merged for that project until the gate jobs are green again. In the case of Neutron, making the job non voting only caused more bugs to slip

[openstack-dev] Gate breakage process - Let's fix! (related but not specific to neutron)

2013-08-16 Thread Maru Newby
Neutron has been in and out of the gate for the better part of the past month, and it didn't slow the pace of development one bit. Most Neutron developers kept on working as if nothing was wrong, blithely merging changes with no guarantees that they weren't introducing new breakage. New bugs

Re: [openstack-dev] Gate breakage process - Let's fix! (related but not specific to neutron)

2013-08-16 Thread Alex Gaynor
I'd strongly agree with that, a project must always be gated by any tests for it, even if they don't gate for other projects. I'd also argue that any time there's a non-gating test (for any project) it needs a formal explanation of why it's not gating yet, what the plan to get it to gating is, and

Re: [openstack-dev] Gate breakage process - Let's fix! (related but not specific to neutron)

2013-08-16 Thread Monty Taylor
On 08/16/2013 02:25 PM, Maru Newby wrote: Neutron has been in and out of the gate for the better part of the past month, and it didn't slow the pace of development one bit. Most Neutron developers kept on working as if nothing was wrong, blithely merging changes with no guarantees that they

Re: [openstack-dev] Gate breakage process - Let's fix! (related but not specific to neutron)

2013-08-16 Thread Clint Byrum
Excerpts from Maru Newby's message of 2013-08-16 11:25:07 -0700: Neutron has been in and out of the gate for the better part of the past month, and it didn't slow the pace of development one bit. Most Neutron developers kept on working as if nothing was wrong, blithely merging changes with