openstack/neutron
Code Issues Proposed changes

Merge "Updates to Bug Deputy section of Bugs DevRef"

Browse Source
This commit is contained in:
Jenkins 2016-03-09 22:47:29 +00:00 committed by Gerrit Code Review
commit 9cdd1310fb
1 changed files with 11 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
doc/source/policies/bugs.rst
View File

@ -94,14 +94,14 @@ steps you will need to follow in order to be prepared.
around setting the importance and tags of bugs. around setting the importance and tags of bugs.
* Sign up for neutron bug emails from LaunchPad. * Sign up for neutron bug emails from LaunchPad.
* Navigate to the `LaunchPad Neutron bug list <https://bugs.launchpad.net/openstack/+bugs?field.tag=neutron>`_. * Navigate to the `LaunchPad Neutron bug list <https://bugs.launchpad.net/neutron>`_.
* On the right hand side, click on "Subscribe to bug mail". * On the right hand side, click on "Subscribe to bug mail".
* In the pop-up that is displayed, keep the recipient as "Yourself", and your * In the pop-up that is displayed, keep the recipient as "Yourself", and your
subscription something useful like "Neutron Bugs". You can choose either subscription something useful like "Neutron Bugs". You can choose either
option for how much mail you get, but keep in mind that getting mail for option for how much mail you get, but keep in mind that getting mail for
all changes - while informative - will result in several dozen emails per all changes - while informative - will result in several dozen emails per
day at least. day at least.
* Do the same for the `LaunchPad python-neutronclient bug list <https://bugs.launchpad.net/openstack/+bugs?field.tag=python-neutronclient>`_. * Do the same for the `LaunchPad python-neutronclient bug list <https://bugs.launchpad.net/python-neutronclient>`_.
* Configure the information you get from `LaunchPad <https://bugs.launchpad.net/neutron>`_ * Configure the information you get from `LaunchPad <https://bugs.launchpad.net/neutron>`_
to make visible additional information, especially the 'age' of the bugs. You to make visible additional information, especially the 'age' of the bugs. You
@ -247,6 +247,13 @@ The process of bug triaging consists of the following steps:
* Check if a bug was filed for a correct component (project). If not, either * Check if a bug was filed for a correct component (project). If not, either
change the project or mark it as "Invalid". change the project or mark it as "Invalid".
* For bugs that affect documenation (including autogenerated DocImpact bugs)
proceed like this. If documentation affects
* the ReST API, add "openstack-api-site" to the affected projects.
* the OpenStack manuals, like the Networking Guide or the Configuration
Reference, add "openstack-manuals" to the affected projects
* developer documentation (devref), set the bug to "Confirmed" for
the project Neutron, otherwise set it to "Invalid".
* Check if a similar bug was filed before. Rely on your memory if Launchpad * Check if a similar bug was filed before. Rely on your memory if Launchpad
is not clever enough to spot a duplicate upon submission. You may also is not clever enough to spot a duplicate upon submission. You may also
check already verified bugs for `Neutron <https://review.openstack.org/#/q/status:open+label:Verified-2+project:openstack/neutron>`_ check already verified bugs for `Neutron <https://review.openstack.org/#/q/status:open+label:Verified-2+project:openstack/neutron>`_
@ -270,7 +277,8 @@ If the bug report is sound, move next:
* Depending on ease of reproduction (or if the issue can be spotted in the * Depending on ease of reproduction (or if the issue can be spotted in the
code), mark it as 'Confirmed'. If you are unable to assess/triage the code), mark it as 'Confirmed'. If you are unable to assess/triage the
issue because you do not have access to a repro environment, consider issue because you do not have access to a repro environment, consider
reaching out the Lieutenant, go-to person for the affected component; reaching out the `Lieutenant <http://docs.openstack.org/developer/neutron/policies/core-reviewers.html#core-review-hierarchy>`_,
go-to person for the affected component;
he/she may be able to help: assign the bug to him/her for further he/she may be able to help: assign the bug to him/her for further
screening. If the bug already has an assignee, check that a patch is screening. If the bug already has an assignee, check that a patch is
in progress. Sometimes more than one patch is required to address an in progress. Sometimes more than one patch is required to address an