Bug Triage/Process/Triage: Difference between revisions
Jump to navigation
Jump to search
| Line 26: | Line 26: | ||
Needinfo someone who can answer your question and finish triaging when they reply. | Needinfo someone who can answer your question and finish triaging when they reply. | ||
=== This doesn't fit into a P1, P2, P3 | === This doesn't fit into a P1, P2, P3, or P5framework === | ||
Mark it as a P3. If it's a tracking bug, make sure it's marked as [meta]. | Mark it as a P3. If it's a tracking bug, make sure it's marked as [meta]. | ||
Revision as of 16:04, 14 June 2016
Who Triages
See list of triage leads.
What Do You Triage
All open, confirmed bugs in a component without a pending needinfo flag since 1 July 2016.
How Do You Triage
Find bugs un-triaged bugs in your component.
We're building a web tool to help you do this.
For each bug decide priority (you can ignore what's already been set, as a triage lead, you are the decider.)
- P1
- Fix in the current release or iteration
- P2
- Fix in the next release or iteration
- P3
- Backlog
- P5
- Will not fix, but will accept a patch
How Do I Handle Edge Cases
I Don't Have Enough Information
Needinfo someone who can answer your question and finish triaging when they reply.
This doesn't fit into a P1, P2, P3, or P5framework
Mark it as a P3. If it's a tracking bug, make sure it's marked as [meta].
I don't think we should work on it at any time
If you'll accept a patch, mark it as P5, otherwise, close it as WONTFIX
Follow Ups
Watch open needinfos
Don't let open needinfos linger for more than two weeks. Close minor bugs with unresponded needinfos. Chase down other needinfo requestees.
End of Iteration
- P2s become P1s after review
- Hoist any P3s to P2's or P1