On Sun, Nov 24, 2013 at 10:48 PM, Robert Collins <robe...@robertcollins.net>wrote:
> On 25 November 2013 19:25, Joe Gordon <joe.gord...@gmail.com> wrote: > > > > > > > > On Sun, Nov 24, 2013 at 9:58 PM, Robert Collins < > robe...@robertcollins.net> > > wrote: > >> > >> I have a proposal - I think we should mark all recheck bugs critical, > >> and the respective project PTLs should actively shop around amongst > >> their contributors to get them fixed before other work: we should > >> drive the known set of nondeterministic issues down to 0 and keep it > >> there. > > > > > > > > Yes! In fact we are already working towards that. See > > > http://lists.openstack.org/pipermail/openstack-dev/2013-November/020048.html > > Indeed I saw that thread - I think I'm proposing something slightly > different, or perhaps 'gate blocking' needs clearing up. Which is - > that once we have sufficient evidence to believe there is a > nondeterministic bug in trunk, whether or not the gate is obviously > suffering, we should consider it critical immediately. I don't think > we need 24h action on such bugs at that stage - gate blocking zomg > issues obviously do though! > I see what your saying. That sounds like a good idea, all gate bugs are critical, but only zomg gate is bad gets 24h action. > > The goal here would be to drive the steady state of 'recheck needed' > so low that most people never encounter it. And break the social > pattern that has been building up. > Yes, agreed. > > -Rob > > -- > Robert Collins <rbtcoll...@hp.com> > Distinguished Technologist > HP Converged Cloud > > _______________________________________________ > 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
