Confirmed users
1,201
edits
(functional teams) |
|||
| (14 intermediate revisions by 10 users not shown) | |||
| Line 1: | Line 1: | ||
Each bug has a free-form single line text entry box for adding tags and status information. This wiki page is dedicated to collect a comprehensive list of whiteboard tags used in the Mozilla project. | Each bug has a free-form single line text entry box for adding tags and status information. This wiki page is dedicated to collect a comprehensive list of whiteboard tags used in the Mozilla project. | ||
== Whiteboard considered harmful == | |||
It is recommended that you request alternative metadata instead of using whiteboard tagging. | |||
* Updating whiteboards tags through the API is non-trivial | |||
* There is no global auto-suggest for whiteboard tags | |||
* There is no verification of whiteboard tags; typos will not be caught and prevented | |||
* Renaming a whiteboard tag requires writing a script to update every bug with that tag, changing its last modified timestamp and generating bugmail; other solutions involve a simple change by administrators | |||
* Whiteboard tags cannot be disabled; people might continue to provide them after they are no longer relevant thinking they still apply | |||
* If desired it's possible to restrict who can set flags to particular values; it will never be possible to prevent accidental or other changes to the whiteboard from any user with editbugs or the bug's reporter | |||
Consider using a keyword, a flag, or a status flag. You can request this on [https://bugzilla.mozilla.org/enter_bug.cgi?product=bugzilla.mozilla.org&component=Administration Bugzilla]. | |||
== Contributor mentoring == | == Contributor mentoring == | ||
| Line 5: | Line 18: | ||
For more information, see [[Mentors]]. | For more information, see [[Mentors]]. | ||
* <code>[lang=]</code>: The programming language involved for this bug. | * <code>[lang=]</code>: The programming language involved for this bug. | ||
* <code>[mentor-lang=]</code>: (human/natural) language other than English the mentor will be able to communicate to the contributor with. | * <code>[mentor-lang=]</code>: (human/natural) language other than English the mentor will be able to communicate to the contributor with. | ||
| Line 13: | Line 24: | ||
* <code>[test disabled]</code>: Indicates an automated test has been disabled. Typically used in bugs filed for intermittent test failures, to indicate that the absence of new failures in the bug is due to the test being disabled - as well as remind module owners that the test needs fixing and re-enabling. | * <code>[test disabled]</code>: Indicates an automated test has been disabled. Typically used in bugs filed for intermittent test failures, to indicate that the absence of new failures in the bug is due to the test being disabled - as well as remind module owners that the test needs fixing and re-enabling. | ||
== Autonag == | |||
<code>[no-nag]</code>: Indicates that a bug should not be modified or commented in by our [[Release_Management/autonag|Autonag]] scripts. | |||
== Release Engineering == | == Release Engineering == | ||
| Line 21: | Line 35: | ||
* <code>[leave open]</code>: This has [https://groups.google.com/forum/#!topic/mozilla.dev.platform/Ie9OXcWbTSs been deprecated] in favour of the 'leave-open' keyword. Used to ensure that the bug updating tool mcMerge does not close the bug when commits referencing it are merged into mozilla-central. | * <code>[leave open]</code>: This has [https://groups.google.com/forum/#!topic/mozilla.dev.platform/Ie9OXcWbTSs been deprecated] in favour of the 'leave-open' keyword. Used to ensure that the bug updating tool mcMerge does not close the bug when commits referencing it are merged into mozilla-central. | ||
* <code>[retriggered]</code>: Used by sheriffs when investigating Fresh Oranges [https://charts.mozilla.org/FreshOranges/index.html] to find where a failure started from, using backfills and retriggers | |||
== Firefox == | == Firefox == | ||
* <code>dupeme</code>, <code>dupme</code>, or <code>DUPEME</code>: we're pretty sure this bug report is a duplicate of another bug, but cannot recall which one or cannot find it. | |||
* <code>[qa-]</code>: QE (Quality Engineering) verification not required - superseded by the qe-verify flag. | |||
* <code>[adv-mainNN+]</code> (where <code>NN</code> is some number): a security advisory about this bug for the release <code>NN</code> will be (has been) written. | |||
* <code>[MemShrink]</code>: [[Performance/MemShrink|a project]] to reduce memory consumption. | |||
== Community reported bugs == | |||
* <code>[nightly-community]</code>: This bug was reported by a member of the Firefox Nightly community. Used to triage community-reported bugs and measure the impact of our core community on product quality. | |||
* <code>[mozfr-community]</code>: This bug was reported by a member of the MozFR French-speaking community. Used to evaluate the impact of the mozfr.org community on product quality. | |||
== Firefox OS == | == Firefox OS == | ||
{{ note: This project is no longer active, but we leave these definitions for bug tracker historian purposes }} | |||
* <code>[POVB]</code>: Part of vendor build; the fix of this bug is not in the Mozilla codebase, but it's in our interest to track it. | * <code>[POVB]</code>: Part of vendor build; the fix of this bug is not in the Mozilla codebase, but it's in our interest to track it. | ||
| Line 33: | Line 56: | ||
* <code>[p=]/[u=]/[c=]/[s=]</code>: See [[BMO/Whiteboard#Scrum Development|Scrum Development]]. Firefox OS uses the u= tag as the milestone instead, see [[FirefoxOS/Performance/Triage#Scrumbugs_Tags|Firefox OS Performance Triage]] | * <code>[p=]/[u=]/[c=]/[s=]</code>: See [[BMO/Whiteboard#Scrum Development|Scrum Development]]. Firefox OS uses the u= tag as the milestone instead, see [[FirefoxOS/Performance/Triage#Scrumbugs_Tags|Firefox OS Performance Triage]] | ||
* <code>[ft:<name of the team>]</code>, <code>[systemsfe]</code>, etc: Bugs identified to be owned by a "functional team" within B2G engineering. Each team owns a specific set of Bugzilla components, and tags are used to denote owned bugs outside of these components. | * <code>[ft:<name of the team>]</code>, <code>[systemsfe]</code>, etc: Bugs identified to be owned by a "functional team" within B2G engineering. Each team owns a specific set of Bugzilla components, and tags are used to denote owned bugs outside of these components. | ||
== Tor == | |||
* <code>[tor ###]</code> Part of the [[Security/Tor_Uplift/Tracking|Tor uplift project]]. For example, <code>[tor 16620]</code> indicates a corresponding ticket at https://trac.torproject.org/16620. See also https://torpat.ch/uplift | |||
== Web Compatibility == | == Web Compatibility == | ||
| Line 52: | Line 78: | ||
If you know what one of the following whiteboard keywords means, please describe it and put it into one of the above categories above (or create a new one): | If you know what one of the following whiteboard keywords means, please describe it and put it into one of the above categories above (or create a new one): | ||
* <code>[ | * <code>[2.0-FL-bug-bash]</code> (example: https://bugzilla.mozilla.org/show_bug.cgi?id=1021384) | ||
* <code>[ | * <code>[games]</code> (example: https://bugzilla.mozilla.org/show_bug.cgi?id=1017892) | ||
* <code>[ | * <code>[reserve-photon-structure]</code> ([https://bugzilla.mozilla.org/buglist.cgi?list_id=14108939&status_whiteboard_type=substring&status_whiteboard=%5Breserve-photon-structure%5D&order=Bug%20Number&query_format=advanced examples]) | ||
* <code>[TCP]</code> (example: https://bugzilla.mozilla.org/show_bug.cgi?id=920036) | * <code>[TCP]</code> (example: https://bugzilla.mozilla.org/show_bug.cgi?id=920036) | ||
** my guess: Tablet Contribution Program? | ** my guess: Tablet Contribution Program? | ||