154
edits
(→Bug Triage Process Guidelines: Minor fix of subheading) |
(→Roadmap and Status: Update roadmap and status information) |
||
| Line 26: | Line 26: | ||
For more detailed information, [https://docs.google.com/document/d/1ySAAbTiLGonljjkM01ZIyz1P_W1A2dk5Cj_oi-550mo/edit notes from the team's weekly standup meetings] are available. | For more detailed information, [https://docs.google.com/document/d/1ySAAbTiLGonljjkM01ZIyz1P_W1A2dk5Cj_oi-550mo/edit notes from the team's weekly standup meetings] are available. | ||
=== Backlog Tracking in Bugzilla === | |||
We use the <code>[layout:backlog]</code> tag in the whiteboard field on bugs, tasks and enhancements to track work items that are either under active development, or being considered for development within the next year. | |||
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 release cycle. | |||
* '''P2''' — Near-term backlog item, planned to work on within the next 2-3 months. | |||
* '''P3''' — Longer-term backlog item, planned to work on within the next year. | |||
* '''P4''' — N/A | |||
* '''P5''' — No plans to work on this item, but will accept contributor patches. | |||
== Release Notes == | == Release Notes == | ||
edits