DOM/Triage: Difference between revisions

DOM/Triage (view source)

Revision as of 11:39, 4 May 2020

1,569 bytes added , 4 May 2020

→‎New bugs of "defect" type - do this daily

Hsinyi

Confirmed users

978

edits

@@ Line 2: / Line 2: @@
 [https://mozilla.github.io/bug-handling/triage-bugzilla Here] gives an overview of how we do triage and what each priority means. We now have [https://mozilla.github.io/task-defect-enhancement/index.html three types of bugs]: defect, task and enhancement. Our engineering daily triage practice focuses on '''defect''' bugs. Bugs with type task or enhancement will generally be reviewed with PM/EPM. '''The goal is to set a priority in as little time as possible!'''
-==New bugs of "defect" type - do this daily==
+==New bugs of "defect" or "task" type - do this daily==
-New bugs of "defect" type that need actions
+New bugs of "defect" or"task" type that need actions
-*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20Core%20new%20Defect%20bugs&sharer_id=434964&list_id=15178369 DOM Core]
+*[https://bugzilla.mozilla.org/buglist.cgi?o1=notsubstring&f9=bug_type&o4=notregexp&resolution=---&columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate%2Cstatus_whiteboard&v9=defect&f3=status_whiteboard&emailreporter1=1&emailreporter2=1&list_id=15228355&chfieldfrom=2020-04-20&query_format=advanced&o2=notsubstring&v7=---&f6=cf_status_firefox_nightly&email2=wptsync%40mozilla.bugs&bug_severity=--&chfield=%5BBug%20creation%5D&v6=---&f7=cf_status_firefox_release&o8=equals&f5=OP&email1=intermittent-bug-filer%40mozilla.bugs&classification=Components&f8=cf_status_firefox_beta&o7=equals&v8=---&known_name=DOM%20Core%20new%20bugs%20%28w%2Fo%20severity%29&o6=equals&f2=short_desc&emailtype2=notequals&v1=needinfo&product=Core&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Editor&component=DOM%3A%20Events&component=DOM%3A%20Forms&component=DOM%3A%20Geolocation&component=DOM%3A%20HTML%20Parser&component=DOM%3A%20Selection&component=DOM%3A%20Serializers&component=DOM%3A%20UI%20Events%20%26%20Focus%20Handling&chfieldto=Now&o3=notsubstring&f10=CP&f4=short_desc&o9=equals&query_based_on=DOM%20Core%20new%20bugs%20%28w%2Fo%20severity%29&f1=flagtypes.name&emailtype1=notequals DOM Core (all types)]
-*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20Fission%20new%20Defect%20bugs&sharer_id=434964&list_id=14982371 DOM Fission]
+NOTE: DOM Core team had a retro in Brrrlin all-hands that we think visiting all types of bugs has benefits to our engineering work and overview. DOM Core team is trying our best to do daily triage for all types of bugs.
-*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20WorkerAndStorage%20-%20new%20Defect%20bugs&sharer_id=434964&list_id=14982384 DOM Worker&Storage]
-Each day, for each of the bugs in the lists above, set the priority field. We'd like to have the priority set within two weeks after bug filing, especially a bug with "defect" type. Here's a cheat sheet:
+*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20Fission%20new%20Defect%20bugs&sharer_id=434964&list_id=14982371 DOM Fission (needs update per the new "Severity triage" practice]
-* P1: this is a major issue and needs to be fixed ASAP. '''You should also ensure someone is assigned or at least needinfoed!'''
+*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20WorkerAndStorage%20-%20new%20Defect%20bugs&sharer_id=434964&list_id=14982384 (needs update per the new "Severity triage" practice]
-* P2: we should fix this soon (or someone's already working on it)
+Each day, for each of the bugs in the lists above, set the Severity field and ensure the one or more current (Nightly, Beta, Release, ESR) Status_FirefoxNN flags set to a non-default value for a "defect" bug:
-* P3: this should go into the ever-growing pile of "work we should do some day"
+*S1: (Catastrophic) Blocks development/testing, may impact more than 25% of users, causes data loss, potential chemspill, and no workaround available
-* P5: we likely won't spend time on this but if someone contributes a patch, we'd review it (aka "the polite WONTFIX")
+*S2: (Serious) Major Functionality/product severely impaired and a satisfactory workaround doesn't exist
+*S3: (Normal) Blocks non-critical functionality and a work around exists
+*S4: (Small/Trivial) minor significance, cosmetic issues, low or no impact to users
+Use these descriptions to guide your decision on a bug’s severity. We’ll be mapping existing bugs to the new definitions.
 Let's ensure newly-filed bugs in a variety of DOM-ish components are actionable as soon as possible after their filing. This ''doesn't'' mean we're going to fix them sooner but that they'll be fix''able'' when we get around to attempting to fix them. Inspiration taken from [[Platform/GFX/TriageSchedule]].