NeutronBugs

Neutron maintains all of it's bugs in Launchpad. Please see that link for a list of all Neutron bugs.

Neutron Bug Czar
Neutron maintains the notion of a "bug czar." The bug czar plays an important role in the Neutron community. As a large project, Neutron is routinely fielding many bug reports. The bug czar is responsible as acting as a "first contact" for these bug reports and performing triaging. The bug czar is expected to communicate with the various NeutronSubTeams when a bug has been triaged down to the sub-team level. In addition, the bug czar should be reporting High and Critical priority bugs to both the PTL and the core team. These bugs should also be highlighted for discussion during the weekly meeting.

The current Neutron Bug Czar is Kyle Mestery (IRC: mestery).

Previous bug czars:
 * Eugene Nikanorov (IRC: enikanorov)

Bug Triage Process
The process of bug triaging consists of the following steps:
 * 1) Check if a bug was filed for a correct component (project), if not - either change the project or mark it as Invalid
 * 2) Add appropriate tags. Even if the bug is not valid or is duplicate of another one, it still may help bug submitters and corresponding subteam.
 * 3) Check if such bug was filed before. If so, mark it as duplicate of previous bug.
 * 4) Check if bug description is consistent, e.g. it has enough information for developers to reproduce it. If it's not consistent - ask submitter to provide more info and mark a bug as Incomplete.
 * 5) Depending on ease of reproduction (or if the issue can be spot in the code) - mark it as Confirmed
 * 6) Assign Importance. Bugs that obviously break core and widely used functionality should get High or Critical importance. The same applies to bugs that were filed for gate failures.
 * 7) (Optional) Add comments explaining the issue and possible strategy of fixing/working around