Contents |
Introduction
These tags are specialized conventions that the Mozilla Team uses for tracking bugs. Please use only these tags and do not add to the tag list without a vote in a Mozilla Team meeting. The tags are organized by bug status.
General
These tags apply to general Ubuntu packages that we are paying special attention to.
Tag |
Description |
Quicksearch |
accessibility |
Bugs that are related to accessibility issues, please see MozillaTeam/Accessibility. |
Needs Info
likely-dup |
bugs that are duplicates, but triager does not have bug number of MASTER bug at hand, can be tagged 'likely-dup'. Other triagers can then pick them, find MASTER bug and mark them appropriately. |
|
mt-needreport |
Crashes that are missing a crash report. |
|
mt-needretrace |
Crash reports that need to have apport-retrace run. |
|
mt-needtestcase |
Bugs that need a reproducible test case. |
|
mt-needtester |
Bugs that need a tester who can reproduce and help to evaluate test-fixes in a responsive manner. |
|
mt-needsummary |
Bugs that need their summary and description cleaned up. |
|
mt-confirm |
Bugs that appears to have all information necessary to go to state "Confirmed" |
|
mt-reject-candidate |
Bugs older than two months, already tagged as "mt-confirm", w/o a valid test case ("mt-needtestcase"), w/o dups, that should be reviewed for rejecting as they are unlikely to ever pass to "Confirmed" state. This tag is set automatically. |
Confirmed
mt-upstream |
Bugs that need to be triaged upstream. |
|
mt-postupstream |
Bugs that are ready for upstream submission. |
|
mt-eval |
Bug needs evaluation. |
|
mt-confirm |
Bugs that have a good solution evaluation attached. |
If you want to tag something specific to a product, be it Firefox, Thunderbird or even Flashplugin-nonfree then please start up a new category to hold it.
Feedback
fixme I think we will need to add status to distinguish between needsinfo confim and confirmed confirm. -- done: asac