Bug Triage/Process/Triage: Difference between revisions

Bug Triage/Process/Triage (view source)

1,187 bytes removed , 6 May 2020

bug-handling docs moved in-tree to bug-mgmt

14

edits

@@ Line 1: / Line 1: @@
-= Who Triages =
+This is now being maintained in mozilla-central at https://firefox-source-docs.mozilla.org/bug-mgmt/policies/triage-bugzilla.html.
-See list of [[Bugmasters/Project/Bug_Handling/Triage_Leads|triage leads]].
-= What Do You Triage =
-All open, confirmed bugs in a component without a priority set or pending needinfo flage since 1 July 2016.
-Softvision and volunteers will work on unconfirmed bugs, and set priority to '--' when they land in NEW.
-= 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:
-;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 framework ===
-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