Nova Bug Triage
The triage of Nova bugs follows the OpenStack-wide process documented on BugTriage. Since Nova is such an active project with a high number of incoming bug reports, we have a separate process for categorizing bugs and distributing the load of triage to a larger group of people.
There is also a weekly Nova bug meeting here: Meetings/NovaBugScrub
Step 0: Join nova-bugs team
There is an open group you need to join to get permissions to set bug priorities: https://launchpad.net/~nova-bugs
Step 1: Tagging
All new bugs should be tagged to reflect which part of Nova they are related to. The current list of tags can be found on BugTags. Note that it is fine for a bug to receive more than one tag if appropriate.
Launchpad Query: Untriaged Bugs Without Tags
Anyone is welcome to help with tagging bugs. However, the nova bug scrub team has committed to checking this on a regular basis to keep the untagged bug queue under control. See the meeting link for more information
Step 2: Triage Tagged Bugs
Once new bugs have been tagged, they should be triaged as described on BugTriage. To help make sure that the triage queue stays under control, the following table lists the people that have committed to regularly triaging bugs for a given tag. For a description of each tag, see BugTags.
|Bug tag||Owner(s)||Untriaged Query||All Query|
|ironic||John Villalovos / devananda||Untriaged||All|
|testing||wendar, jogo, and others||Untriaged||All|
1. novaclient bugs exist in their own project on launchpad, python-novaclient. They are not tagged bugs in the nova project. However, we still need one or more people signed up to make sure novaclient bugs get triaged and looked after.
Step 3: Spotting Bug "Themes"
While the above looks at the area of the code, lets also consider tags for key bug "themes":