Confirmed users
1,094
edits
Firefox/searchandaddon: Difference between revisions
→Triage Guidelines: g
Sescalante (talk | contribs) (updated) |
Sescalante (talk | contribs) (→Triage Guidelines: g) |
||
| Line 117: | Line 117: | ||
==Triage Guidelines== | ==Triage Guidelines== | ||
The Product Backlog is continually maintained by the Hello Management team to ensure new priorities are available for each Sprint Planning meeting. | The Product Backlog is continually maintained by the Hello Management team to ensure new priorities are available for each Sprint Planning meeting. | ||
* Priorities follow this Standard: | * '''Priorities''' follow this Standard: | ||
** Priority 1 - Blocker, must-fix before shipping. | ** Priority 1 - Blocker, must-fix before shipping. | ||
** Priority 2 - Major impact, considering severity × probability. Not a blocker for shipping. | ** Priority 2 - Major impact, considering severity × probability. Not a blocker for shipping. | ||
| Line 124: | Line 124: | ||
** Priority 5 - Low-impact. something we'd fix, but mostly only bothers the discerning user. Little impact on usability. | ** Priority 5 - Low-impact. something we'd fix, but mostly only bothers the discerning user. Little impact on usability. | ||
<p> </p> | <p> </p> | ||
*RANK: As priority buckets start to have a large amount of bugs in them, the Rank field can be used to call attention to higher or lower rank and provide a way to sort easily in bugzilla. To have some rhyme/reason to the order - Rank should relate to Priority. The "Ranking" number does not need to be unique. Unless there is a reason to for a bug to be considered before (or after) others in the Priority bucket - default to mid-range value. | *'''RANK''': As priority buckets start to have a large amount of bugs in them, the Rank field can be used to call attention to higher or lower rank and provide a way to sort easily in bugzilla. To have some rhyme/reason to the order - Rank should relate to Priority. The "Ranking" number does not need to be unique. Unless there is a reason to for a bug to be considered before (or after) others in the Priority bucket - default to mid-range value. | ||
** P1 Rank options=1-19, default 15 | ** P1 Rank options=1-19, default 15 | ||
** P2 Rank options=20-29, default 25 | ** P2 Rank options=20-29, default 25 | ||
| Line 132: | Line 132: | ||
** any that we don't think we can get to in the next 6 months should go in "backlog-" area | ** any that we don't think we can get to in the next 6 months should go in "backlog-" area | ||
<p> </p> | <p> </p> | ||
*The Firefox-backlog flag is used to track bugs that are approved for the Backlog "+" (or Backlog - to not be looked at for a while) | *The '''Firefox-backlog''' flag is used to track bugs that are approved for the Backlog "+" (or Backlog - to not be looked at for a while) | ||
*Add whiteboard tag to bugs [fxsearch] as bugs for this team may span Product:: Component areas. | *Add '''whiteboard''' tag to bugs [fxsearch] as bugs for this team may span Product:: Component areas. | ||
*QE-Verify is a flag that developers should be setting on bugs they are working on. This is used for QE to filter which bugs they check | *'''QE-Verify''' is a flag that developers should be setting on bugs they are working on. This is used for QE to filter which bugs they check | ||
**"+" means that QE should look at the bug and it can be verified with human eyes | **"+" means that QE should look at the bug and it can be verified with human eyes | ||
**"-" means QE should not look at | **"-" means QE should not look at | ||
***Typically goes with in-testsuite set to "+", to show testing via another method. | ***Typically goes with in-testsuite set to "+", to show testing via another method. | ||
* | *'''Points''' should be set when known. | ||
* | *'''Iteration''' should be updated when a bug is being worked on during a particular Iteration. | ||
<p> </p> | <p> </p> | ||