On 9/16/14, 11:12 AM, "Daniel P. Berrange" <berra...@redhat.com> wrote:

>On Tue, Sep 16, 2014 at 07:30:26AM +1000, Michael Still wrote:
>> On Tue, Sep 16, 2014 at 12:30 AM, Russell Bryant <rbry...@redhat.com>
>> > On 09/15/2014 05:42 AM, Daniel P. Berrange wrote:
>> >> On Sun, Sep 14, 2014 at 07:07:13AM +1000, Michael Still wrote:
>> >>> Just an observation from the last week or so...
>> >>>
>> >>> The biggest problem nova faces at the moment isn't code review
>>latency. Our
>> >>> biggest problem is failing to fix our bugs so that the gate is
>> >>> The number of rechecks we've done in the last week to try and land
>>code is
>> >>> truly startling.
>> >>
>> >> I consider both problems to be pretty much equally as important. I
>> >> think solving review latency or test reliabilty in isolation is
>>enough to
>> >> save Nova. We need to tackle both problems as a priority. I tried to
>> >> getting into my concerns about testing in my mail on review team
>> >> since I think we should address the problems independantly / in
>> >
>> > Agreed with this.  I don't think we can afford to ignore either one
>>of them.
>> Yes, that was my point. I don't mind us debating how to rearrange
>> hypervisor drivers. However, if we think that will solve all our
>> problems we are confused.
>> So, how do we get people to start taking bugs / gate failures more
>> seriously?
>I think we should have formal "Bug squash wednesdays"  (or pick another
>day). By this I mean that the core reviewers will focus their attention
>on just reviews that are related to bug fixing. They will also try to
>work on bugs if they have time and encourage everyone else involved in
>Nova todo the same. We'd have a team of people in the Nova IRC channel
>to publicise & co-ordinate bug squashing, perhaps  with a list of top
>20 bugs we want to attack this week. I wouldn't focus just on gate bugs
>here since many a pretty darn hard & so would put off many people. Have
>a mix of bugs of varying difficulties to point people to. Make this a
>regular fortnightly or even weekly event which we publicise in advance
>on mailing lists, etc.

I am in favor of that. This is similar to what I suggested in

>afdd513f39cce7f5f3ab73352c456981edc8f0aa6c4861d61f1ce0528c      -o-
>a31 :|
>e922c5cb03f8a55c11b821bf9f4c011b6a3403db100266dba66e2e5f0c69ff :|
>79ea977e54c5203c70c9a8043195c3addd86cb4f2d0aca9ee34deff3f9f       -o-
>%0A&s=a13745c2c9636ce6c906c4467ba453cd8a2011fde467959cde586abc69cc0717 :|
>&s=427473a2fc971ad2586cfc228d80b49c48a730603946888ed33085a30da98985 :|
>OpenStack-dev mailing list

OpenStack-dev mailing list

Reply via email to