On 08/17/2013 12:26 AM, Clint Byrum wrote:
Excerpts from Maru Newby's message of 2013-08-16 16:42:23 -0700:
On Aug 16, 2013, at 11:44 AM, Clint Byrum wrote:
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 pa
On Sat, Aug 17, 2013 at 9:46 AM, Robert Collins
wrote:
> On 17 August 2013 23:49, Salvatore Orlando 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 jo
On 17 August 2013 23:49, Salvatore Orlando 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 through, and that mea
On Aug 17, 2013 7:52 AM, "Salvatore Orlando" 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 through, and that mea
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 headac
Excerpts from Maru Newby's message of 2013-08-16 16:42:23 -0700:
>
> On Aug 16, 2013, at 11:44 AM, Clint Byrum wrote:
>
> > 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 slo
On Aug 16, 2013, at 11:44 AM, Clint Byrum wrote:
> 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 worki
On Aug 16, 2013, at 11:44 AM, Monty Taylor wrote:
>
>
> 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 w
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
> w
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 t
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
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 w
12 matches
Mail list logo
