Confirmed users
1,201
edits
BMO/UserGuide/Whiteboard: Difference between revisions
→Whiteboard considered harmful
Grahamperrin (talk | contribs) (Performance/MemShrink) |
|||
| (3 intermediate revisions by 3 users not shown) | |||
| Line 7: | Line 7: | ||
* Updating whiteboards tags through the API is non-trivial | * Updating whiteboards tags through the API is non-trivial | ||
* There is no global auto-suggest for whiteboard tags | * There is no global auto-suggest for whiteboard tags | ||
* There is no | * 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]. | 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]. | ||
| Line 21: | 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 29: | 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 == | ||