Issue Management

Goals

Every issue in the repository should:

• A clear title.
• Have labels explaining why the issue is still open.
• Have labels explaining what the issue applies to (e.g. debugging).
• Have labels explaining what sort of issue something is (e.g. a bug).

Workflow

New issues

... receive the classify label so they can be triaged.

Triaging

1. Issues get assigned to someone and receive the triage label, replacing the classify label.
2. If more information is needed from the original poster (OP), the info needed label is added, being removed once the OP responds with the requested information.
3. The investigating label is applied when the person assigned to triage the issue has started looking into the cause of the issue (this may come after a couple of messages between the OP and the assigned person to clearly understand what needs investigation).
4. If the issue is found to be legitimate, the appropriate needs label replaces the investigating label.

Closing

Issues can be closed if:

1. The issue was opened in error by the OP.
2. The issue cannot be reproduced.
3. The OP did not respond to a request for more information.
4. We have chosen not to pursue a feature request.
5. A feature has been implemented for the next release and has been added to the appropriate milestone (the issue is expected to also have either the on-testplan or verification-needed label applied as appropriate before we reach endgame week; see release testing for details)
6. A bug has been fixed in the next release and has been added to the appropriate milestone.