Special issue titles

Generally, issue titles should be a concise description of the issue. Some issues have special prefixes with specific meanings:

• [already committed]: The issue has already been committed (merged) into all the intended branches, but remains open for followup tasks.
• [backport]: The issue is for porting a patch from another issue to a previous version of the project.
• [meta]: The issue is a "meta-issue", meaning that it is a page that is being used to gather together a list of other issues, and will be marked fixed when all of the issues in the list are fixed.
• [ignore]: The issue has been created in order to trigger an automated test or otherwise test issue queue functionality, but it should be ignored by project maintainers and reviewers.
• [Plan]: The issues is being used to make a plan (also set the issue Category field to Plan) and is not expected to result in a software patch directly.
• [policy, no patch]: The issue is discussing a policy rather than making a software fix (also set the issue Category field to Plan)
• PP-1, PP-2, etc.: The issue is currently postponed on 1, 2, ... other issues, meaning that it cannot be fixed until other issues have been fixed. In addition, the issue Status field should be set to Postponed. Also, the remaining tasks should include links to the issue this this is postponed on..
• [random test failure]: The issue is about a random failure of automated tests.
• [regression]: The issue is about behavior that was previously working, but has been broken by another issue's fix.