Difference between revisions of "BugDays/20120202BugSquashing"
(talk) |
(Page reorg in prep for Bugtriage day) |
||
| Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
| − | = | + | <!-- ## page was renamed from [[BugSquashingDay]]/20120202 --> |
| + | = Groundhog Bug Squashing Day = | ||
| − | * Date: ''' | + | * Date: '''February 2nd, 2012''' |
| − | * Topic: | + | * Topic: OpenStack project bugs. |
| − | * Key objective: | + | * Key objective: Close as many bugs as possible over a day ! |
| − | |||
| − | == What | + | == What? How? == |
| − | See [[BugSquashingDay]] for more details on Bug squashing days. | + | See [[BugSquashingDay]] for more details on Bug squashing days. See [[DevQuickstart]] for instructions on getting a development environment up. |
| − | == | + | == Where? == |
| + | |||
| + | * Online on IRC: Join '''#openstack-bugsquash''' on Freenode | ||
| + | * Austin event - Racker Rally Room starting at 9:00 am. See http://www.meetup.com/OpenStack-Austin/events/48406252/ to RSVP. Lunch around noon and beer-thirty at 4:30 pm in the lobby. | ||
| + | * SFO event - See http://www.meetup.com/openstack/events/48362422/ to RSVP. | ||
| + | * Blacksburg event - Contact Gabe Westmaas, gabe dot westmaas at rackspace dot com to join in. | ||
| + | |||
| + | == Metrics == | ||
| + | |||
| + | See how much of a difference you make: we will graph our progress during the whole day, using stats at: '''http://wiki.openstack.org/bugstats/''' | ||
| + | |||
| + | == Why? == | ||
The [http://webnumbr.com/open-nova-bugs number of open bugs] filed against Nova grew from 200 to 500 in the last 6 months. Some of them no longer apply, some of them are easy fixes. Getting rid of them will allow us to have a more usable bug list as we get closer to the Essex release. | The [http://webnumbr.com/open-nova-bugs number of open bugs] filed against Nova grew from 200 to 500 in the last 6 months. Some of them no longer apply, some of them are easy fixes. Getting rid of them will allow us to have a more usable bug list as we get closer to the Essex release. | ||
| + | |||
| + | Even if their numbers are smaller, all other OpenStack projects are welcome to squash their bugs on the same day! | ||
| + | |||
| + | == Getting Started Guide == | ||
| + | |||
| + | [[DevQuickstart]] | ||
== Tasks == | == Tasks == | ||
| Line 29: | Line 46: | ||
It's sometimes hard to distinguish fresh bugs from false alarms. You can help by using your expertise or reproduction skills on ''New'' bugs. If you can confirm the issue, set the bug to ''Confirmed''. If you can fix it, read the previous chapter. If you need more info from the reporter, set it to ''Incomplete''. And if it happens to not really be valid, set it to ''Invalid'' ! | It's sometimes hard to distinguish fresh bugs from false alarms. You can help by using your expertise or reproduction skills on ''New'' bugs. If you can confirm the issue, set the bug to ''Confirmed''. If you can fix it, read the previous chapter. If you need more info from the reporter, set it to ''Incomplete''. And if it happens to not really be valid, set it to ''Invalid'' ! | ||
| − | == | + | == Per-project objectives == |
| − | |||
| − | |||
| − | |||
| − | |||
| − | == | ||
| − | |||
| − | |||
| − | == | + | ==== Nova ==== |
| + | * Primary objective: '''Fall below 350 open bugs''' | ||
| + | * Secondary objectives | ||
| + | ** New/Incomplete (untriaged bugs): under 40 | ||
| + | ** Confirmed/triaged bugs: under 250 | ||
| + | ** In progress bugs: under 40 | ||
| − | + | ==== Quantum ==== | |
| + | * Focus on code quality metrics, including code coverage and pylint | ||
| + | * Improve system/integration testing with nova | ||
Revision as of 11:42, 25 May 2012
Groundhog Bug Squashing Day
- Date: February 2nd, 2012
- Topic: OpenStack project bugs.
- Key objective: Close as many bugs as possible over a day !
What? How?
See BugSquashingDay for more details on Bug squashing days. See DevQuickstart for instructions on getting a development environment up.
Where?
- Online on IRC: Join #openstack-bugsquash on Freenode
- Austin event - Racker Rally Room starting at 9:00 am. See http://www.meetup.com/OpenStack-Austin/events/48406252/ to RSVP. Lunch around noon and beer-thirty at 4:30 pm in the lobby.
- SFO event - See http://www.meetup.com/openstack/events/48362422/ to RSVP.
- Blacksburg event - Contact Gabe Westmaas, gabe dot westmaas at rackspace dot com to join in.
Metrics
See how much of a difference you make: we will graph our progress during the whole day, using stats at: http://wiki.openstack.org/bugstats/
Why?
The number of open bugs filed against Nova grew from 200 to 500 in the last 6 months. Some of them no longer apply, some of them are easy fixes. Getting rid of them will allow us to have a more usable bug list as we get closer to the Essex release.
Even if their numbers are smaller, all other OpenStack projects are welcome to squash their bugs on the same day!
Getting Started Guide
Tasks
Close old fixed bugs
Old bugs are nasty. Even when they are long dead, they clog bug views and render the lists unusable. Just look at old bugs and check if they still apply ! If they don't, close them as FixReleased (if you can pinpoint when they were fixed) or Invalid (if you can't).
Fix bugs
The best thing you can do on a bug squashing day is to kill a live one. Just look at the list of Confirmed or Triaged and pick your target. Submit a change that fixes it. Ask for review help on the channel.
Triage incoming bugs
It's sometimes hard to distinguish fresh bugs from false alarms. You can help by using your expertise or reproduction skills on New bugs. If you can confirm the issue, set the bug to Confirmed. If you can fix it, read the previous chapter. If you need more info from the reporter, set it to Incomplete. And if it happens to not really be valid, set it to Invalid !
Per-project objectives
Nova
- Primary objective: Fall below 350 open bugs
- Secondary objectives
- New/Incomplete (untriaged bugs): under 40
- Confirmed/triaged bugs: under 250
- In progress bugs: under 40
Quantum
- Focus on code quality metrics, including code coverage and pylint
- Improve system/integration testing with nova
