154
edits
Platform/Layout: Difference between revisions
Jump to navigation
Jump to search
→Whiteboard Tags: Add icebox, links to printing and fragmentation
(Add a variety of information on bugzilla whiteboard tags and contributor resources) |
(→Whiteboard Tags: Add icebox, links to printing and fragmentation) |
||
| Line 84: | Line 84: | ||
We use the following strings (tags) in the whiteboard field on bugs in Bugzilla to track important metadata: | We use the following strings (tags) in the whiteboard field on bugs in Bugzilla to track important metadata: | ||
* <code>[layout:backlog]</code>: Indicates the bug is in our backlog, and is either under active development, or planned development for the | * <code>[layout:backlog]</code>: Indicates the bug is in our backlog, and is either under active development, or planned development for the current year (see bug priority for approximate timeline). | ||
* <code>[layout:icebox]</code>: Indicates a bug we are considering including in our backlog in the future, but are unlikely to work on in the current year. | |||
* <code>[layout:triage-discuss]</code>: Indicates that we plan to discuss this bug in more detail at one of our internal, bi-weekly triage meetings. Usually this is set if the severity level is disputed, or in question, or other triage details of the bug are unclear. | * <code>[layout:triage-discuss]</code>: Indicates that we plan to discuss this bug in more detail at one of our internal, bi-weekly triage meetings. Usually this is set if the severity level is disputed, or in question, or other triage details of the bug are unclear. | ||
We also use whiteboard tags to track bugs for longer-running projects. For more information on these projects and their associated tags, see the pages below: | |||
* [[Platform/Layout/Printing and fragmentation|Printing and Fragmentation Improvements]] | |||
= Contributing = | = Contributing = | ||