BMO/UserGuide/Whiteboard: Difference between revisions
Jump to navigation
Jump to search
(→Contributor mentoring: [mentor=] is deprecated in favour of the new mentor field) |
(Explain a number of whiteboard values) |
||
| Line 22: | Line 22: | ||
== 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. | |||
== Firefox OS == | == Firefox OS == | ||
| Line 51: | Line 52: | ||
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>[MemShrink]</code> | * <code>[MemShrink]</code> | ||
* <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) | ||
| Line 58: | Line 57: | ||
* <code>[games]</code> (example: https://bugzilla.mozilla.org/show_bug.cgi?id=1017892) | * <code>[games]</code> (example: https://bugzilla.mozilla.org/show_bug.cgi?id=1017892) | ||
* <code>[2.0-FL-bug-bash]</code> (example: https://bugzilla.mozilla.org/show_bug.cgi?id=1021384) | * <code>[2.0-FL-bug-bash]</code> (example: https://bugzilla.mozilla.org/show_bug.cgi?id=1021384) | ||
Revision as of 21:26, 13 January 2015
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.
Contributor mentoring
For more information, see Mentors.
[good first bug]: Indicate this is a good first bug for new contributors.[lang=]: The programming language involved for this bug.[mentor-lang=]: (human/natural) language other than English the mentor will be able to communicate to the contributor with.
Automated Testing
[test disabled]: 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.
Release Engineering
[capacity]: This bug will help increase (or free up) capacity for our automated build & test machines.
Sheriffing
[leave open]: This has 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.
Firefox
dupeme,dupme, orDUPEME: we're pretty sure this bug report is a duplicate of another bug, but cannot recall which one or cannot find it.[qa-]: QE (Quality Engineering) verification not required - superseded by the qe-verify flag.[adv-mainNN+](whereNNis some number): a security advisory about this bug for the releaseNNwill be (has been) written.
Firefox OS
[POVB]: Part of vendor build; the fix of this bug is not in the Mozilla codebase, but it's in our interest to track it.[priority]: Indicates we are asked by a partner to address this issue with priority.[tarako_only]: Special pref or feature that only lands on branch for Tarako (low memory phone), i.e. 1.3T branch of Gaia and Gecko. To be picked up on future releases.[p=]/[u=]/[c=]/[s=]: See Scrum Development. Firefox OS uses the u= tag as the milestone instead, see Firefox OS Performance Triage[ft:<name of the team>],[systemsfe], 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.
Web Compatibility
Our whiteboard keywords are already described.
Scrum Development
The following flags are used by tools like scrumbu.gs for managing sprints using the scrum development framework:
[p=]: A rough estimate from engineer on how long the bug is going to take.[u=]: The user (in the scrum sense) that this story affects[c=]: The component (in the scrum sense) that this story affects[s=]: An explicit sprint slug this bug should belong to.
If you are not managing a product, you probably don't have to set these.
What does this whiteboard keyword mean?
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):
[MemShrink][TCP](example: https://bugzilla.mozilla.org/show_bug.cgi?id=920036)- my guess: Tablet Contribution Program?
[games](example: https://bugzilla.mozilla.org/show_bug.cgi?id=1017892)[2.0-FL-bug-bash](example: https://bugzilla.mozilla.org/show_bug.cgi?id=1021384)