Open Stack

Great progress! Thanks for this huge effort.

Edgar

From: Eugene Nikanorov <enikanorov at mirantis.com<mailto:enikanorov at mirantis.com>>
Reply-To: OpenStack Development Mailing List <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Monday, November 24, 2014 at 1:52 AM
To: OpenStack Development Mailing List <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: Re: [openstack-dev] [Neutron] Bug day

Hi again,

I'd like to share some results of the bug day we've conducted on 2014-11-21.
Stats:

  *   73 New bugs<https://bugs.launchpad.net/neutron/+bugs?search=Search&field.status=New>
  *   795 Open bugs<https://bugs.launchpad.net/neutron/+bugs>
  *   285 In-progress bugs<https://bugs.launchpad.net/neutron/+bugs?search=Search&field.status=In+Progress>

I personally went over some opened/new bugs with High/Medium importance, trying to detect duplicates, get rid of some bugs that were not active for too long (like ones that have been filed back in 2013), pinging submitters to provide more info and such.

I've also moved some bugs from 'In progress' to 'New' or 'Confirmed' and removed assignees if their submitted patches were either abandoned or have not been updated for months.
So don't be surprised if I've removed someone. As Russel Bryant has mentioned, assignment might potentially discourage people from looking into the bug.

Thanks everyone for helping with this!

Eugene.

On Fri, Nov 21, 2014 at 11:03 AM, Eugene Nikanorov <enikanorov at mirantis.com<mailto:enikanorov at mirantis.com>> wrote:
Hi neutron folks!

Today we've decided to conduct bug triaging day.
We have more than one thousand bugs needing their state to be checked.
So everyone is welcome to participate!

The goals of bug triaging day are:
1) Decrease the number of New bugs.
Possible 'resolution' would be:
 - confirm bug. If you see the issue in the code, or you can reproduce it
 - mark as Incomplete. Bug description doesn't contain sufficient information to triage the bug.
 - mark as Invalid. Not a bug, or we're not going to fix it.
 - mark as duplicate. If you know that other bug filed earlier is describing the same issue.
 - mark as Fix committed if you know that the issue was fixed. It's good if you could provide a link to corresponding review.

2) Check the Open and In progress bugs.
If the last activity on the bug happened more than a month ago - it makes sense sometimes to bring it back to 'New'.
By activity I mean comments in the bug, actively maintained patch on review, and such.

Of course feel free to assign a bug to yourself if you know how and going to fix it.

Some statistics:

  *   85 New bugs<https://bugs.launchpad.net/neutron/+bugs?search=Search&field.status=New>
  *   811 Open bugs<https://bugs.launchpad.net/neutron/+bugs>
  *   331 In-progress bugs<https://bugs.launchpad.net/neutron/+bugs?search=Search&field.status=In+Progress>

Thanks,
Eugene.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20141124/b5933e9a/attachment.html>