154
edits
Platform/Layout: Difference between revisions
→Backlog Tracking in Bugzilla: Tweak priority guidance
(→Backlog Tracking in Bugzilla: Add more backlog queries) |
(→Backlog Tracking in Bugzilla: Tweak priority guidance) |
||
| Line 34: | Line 34: | ||
We use bug priorities to indicate how soon we plan to work on a bug, task or enhancement according to the following classifications (assuming the bug also has the <code>[layout:backlog]</code> whiteboard tag): | We use bug priorities to indicate how soon we plan to work on a bug, task or enhancement according to the following classifications (assuming the bug also has the <code>[layout:backlog]</code> whiteboard tag): | ||
* '''P1''' — Under active development, or planned development for the current or next release cycle. | * '''P1''' — "Must have/fix." Under active development, or planned development for the current or next release cycle. | ||
* '''P2''' — Near-term backlog item, can/will be worked on soon (within the next 2-3 months). | * '''P2''' — "Should have/fix." Near-term backlog item, can/will be worked on soon (within the next 2-3 months). | ||
* '''P3''' — Longer-term backlog item, planned to work on within the next year. | * '''P3''' — "Would like to have/fix." Longer-term backlog item, planned to work on within the next year. | ||
* '''P4''' — N/A | * '''P4''' — N/A | ||
* '''P5''' — No plans to work on this item, but will accept contributor patches. | * '''P5''' — No plans to work on this item, but will accept contributor patches. | ||