canmove, Confirmed users
1,126
edits
EngineeringProductivity/Projects/Treeherder: Difference between revisions
Jump to navigation
Jump to search
EngineeringProductivity/Projects/Treeherder (view source)
Revision as of 12:47, 24 October 2014
, 24 October 2014→Bug Tables: Add explanation of priority levels
m (→Bug Tables: Add additional sort criteria for bug tables) |
(→Bug Tables: Add explanation of priority levels) |
||
| Line 53: | Line 53: | ||
== Bug Tables == | == Bug Tables == | ||
We're still refining our use of the priority flag, but this is the rough rule of thumb used when triaging: | |||
* '''P1:''' Bugs that should take absolute priority and mean other work is put on hold. Ideal timeframe for work beginning: This week. | |||
* '''P2:''' Important "next" bugs. Timeframe: This month. | |||
* '''P3:''' Timeframe: Ideally in the next few months. | |||
* '''P4:''' Timeframe: Next quarter or two. | |||
* '''P5''' Timeframe: Unknown / future. | |||
Once one queue (eg P1) is nearing depletion, a selection of the bugs from the group below will be promoted to that priority level. Once the substantial lists of [[#TBPL_regressions]] and [[#Operational_and_scaling_bugs]] have been reduced, the guide above may change. | |||
=== [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=blocked%3A1059400 TBPL regressions] === | === [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=blocked%3A1059400 TBPL regressions] === | ||