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> >>wrote: >> > 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 >>reliable. >> >>> 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 >>don't >> >> 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 >>avoid >> >> getting into my concerns about testing in my mail on review team >>bottlenecks >> >> since I think we should address the problems independantly / in >>parallel. >> > >> > 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 http://lists.openstack.org/pipermail/openstack-dev/2014-September/045440.ht ml Thanks Gary > >Regards, >Daniel >-- >|: >https://urldefense.proofpoint.com/v1/url?u=http://berrange.com/&k=oIvRg1%2 >BdGAgOoM1BIlLLqw%3D%3D%0A&r=eH0pxTUZo8NPZyF6hgoMQu%2BfDtysg45MkPhCZFxPEq8% >3D%0A&m=%2BBB%2BI2z%2F47JBRJ4B1mOkFOq0SW%2F4bOrVdaRdWsCsYn0%3D%0A&s=23d33d >afdd513f39cce7f5f3ab73352c456981edc8f0aa6c4861d61f1ce0528c -o- >https://urldefense.proofpoint.com/v1/url?u=http://www.flickr.com/photos/db >errange/&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=eH0pxTUZo8NPZyF6hgoMQu%2BfD >tysg45MkPhCZFxPEq8%3D%0A&m=%2BBB%2BI2z%2F47JBRJ4B1mOkFOq0SW%2F4bOrVdaRdWsC >sYn0%3D%0A&s=2d1a888a2988ac4dd3736b5e3cbd83af371bb5155b92ed769a7dd5516d7ed >a31 :| >|: >https://urldefense.proofpoint.com/v1/url?u=http://libvirt.org/&k=oIvRg1%2B >dGAgOoM1BIlLLqw%3D%3D%0A&r=eH0pxTUZo8NPZyF6hgoMQu%2BfDtysg45MkPhCZFxPEq8%3 >D%0A&m=%2BBB%2BI2z%2F47JBRJ4B1mOkFOq0SW%2F4bOrVdaRdWsCsYn0%3D%0A&s=c2a7391 >a88982f704eb0c1d17acfcb531f6388d637bc72d0fa6dbd5f2ee5077e >-o- >https://urldefense.proofpoint.com/v1/url?u=http://virt-manager.org/&k=oIvR >g1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=eH0pxTUZo8NPZyF6hgoMQu%2BfDtysg45MkPhCZFxP >Eq8%3D%0A&m=%2BBB%2BI2z%2F47JBRJ4B1mOkFOq0SW%2F4bOrVdaRdWsCsYn0%3D%0A&s=8f >e922c5cb03f8a55c11b821bf9f4c011b6a3403db100266dba66e2e5f0c69ff :| >|: >https://urldefense.proofpoint.com/v1/url?u=http://autobuild.org/&k=oIvRg1% >2BdGAgOoM1BIlLLqw%3D%3D%0A&r=eH0pxTUZo8NPZyF6hgoMQu%2BfDtysg45MkPhCZFxPEq8 >%3D%0A&m=%2BBB%2BI2z%2F47JBRJ4B1mOkFOq0SW%2F4bOrVdaRdWsCsYn0%3D%0A&s=3eb04 >79ea977e54c5203c70c9a8043195c3addd86cb4f2d0aca9ee34deff3f9f -o- > >https://urldefense.proofpoint.com/v1/url?u=http://search.cpan.org/~danberr >/&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=eH0pxTUZo8NPZyF6hgoMQu%2BfDtysg45M >kPhCZFxPEq8%3D%0A&m=%2BBB%2BI2z%2F47JBRJ4B1mOkFOq0SW%2F4bOrVdaRdWsCsYn0%3D >%0A&s=a13745c2c9636ce6c906c4467ba453cd8a2011fde467959cde586abc69cc0717 :| >|: >https://urldefense.proofpoint.com/v1/url?u=http://entangle-photo.org/&k=oI >vRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=eH0pxTUZo8NPZyF6hgoMQu%2BfDtysg45MkPhCZF >xPEq8%3D%0A&m=%2BBB%2BI2z%2F47JBRJ4B1mOkFOq0SW%2F4bOrVdaRdWsCsYn0%3D%0A&s= >53d5c4828d9a4c7529bb8bb589b686af7eb1026f0bb7355655b32b06350c85f2 >-o- >https://urldefense.proofpoint.com/v1/url?u=http://live.gnome.org/gtk-vnc&k >=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=eH0pxTUZo8NPZyF6hgoMQu%2BfDtysg45MkPh >CZFxPEq8%3D%0A&m=%2BBB%2BI2z%2F47JBRJ4B1mOkFOq0SW%2F4bOrVdaRdWsCsYn0%3D%0A >&s=427473a2fc971ad2586cfc228d80b49c48a730603946888ed33085a30da98985 :| > >_______________________________________________ >OpenStack-dev mailing list >OpenStack-dev@lists.openstack.org >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
