<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 3 December 2015 at 07:58, Ihar Hrachyshka <span dir="ltr"><<a href="mailto:ihrachys@redhat.com" target="_blank">ihrachys@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">Armando M. <<a href="mailto:armamig@gmail.com" target="_blank">armamig@gmail.com</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi neutrinos,<br>
<br>
It's been a couple of months that the Bug deputy process has been in place [1,2]. Since the beginning of Mitaka we have collected the following statistics (for neutron and neutronclient):<br>
<br>
Total bug reports: 373<br>
• Fix committed: 144<br>
• Unassigned: 73<br>
• New: 17<br>
• Incomplete: 20<br>
• Confirmed: 27<br>
• Triaged: 6<br>
<br>
At first, it is clear that we do not fix issues nearly as fast as they come in, but at least we managed to keep the number of unassigned/unvetted bugs relatively small, so kudos to you all who participated in this experiment. I don't have data based on older releases, so I can't see whether we've improved or worsened, and I'd like to ask for feedback from the people who played with this first hand, especially on the amount of time that has taken them to do deputy duty for their assigned week.<br>
• ihrachys<br>
• regXboi<br>
• markmcclain<br>
• mestery<br>
• mangelajo<br>
• garyk<br>
• rossella_s<br>
• dougwig<br>
</blockquote>
<br></span>
My perspective, it is a success. We are better at disseminating information about ongoing reported issues.<br>
<br>
Timewise, it did not waste more than an hour per day for me, usually less.</blockquote><div><br></div><div>Thanks not time wasted, is it? :)</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> The trick I use is subscribing to all comments in all neutron bugs in LP. That way I don’t need to rely on UI to get the list of bugs reported during me on duty.<br>
<br>
The thing I would like us to see enhanced is making sure that tags set to bugs are actively tracked by corresponding teams. Hint: in my case, I have some recurrent todo on each Fri to walk thru all ‘oslo’ bugs. I may do the same if/once we get ‘upgrade’ tag. It would be great to be able to subscribe to just specific tag for emails, but I don’t know whether it’s possible in LP.<br></blockquote><div><br></div><div>I think the trick is to provide a subscription name, and you can subscribe just to a single tag. That's how I have the RFE bugs stand out in my pile.</div><div><br></div><div>Cheers,</div><div>Armando</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
So kudos for setting the process and thanks everyone involved so far,<br>
<br>
Ihar<div class="HOEnZb"><div class="h5"><br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br></div></div>