DOM/Triage: Difference between revisions

From MozillaWiki
< DOM
Jump to navigation Jump to search
 
(46 intermediate revisions by 3 users not shown)
Line 1: Line 1:
= Overview =
= Overview =
[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!'''  
[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://firefox-source-docs.mozilla.org/bug-mgmt/guides/bug-types.html three types of bugs]: defect, task and enhancement. Our engineering daily triage practice focuses on '''defect''' and '''task''' bugs. Bugs with type task or enhancement will generally be reviewed with PM/EPM. '''The goal is to set a Severity in as little time as possible''' and to drive timely actions for important bugs.
 
As of the [https://groups.google.com/d/msg/mozilla.dev.platform/bqiYgKyTOzk/TpETNzAKBwAJ new Mozilla triage practice] starting in May 04, 2020,  we set the '''Severity''' field to a non-default value when triaging Firefox
related bugs.


==New bugs of "defect" type - do this daily==
==New bugs of "defect" type - do this daily==
New bugs of "defect" type that need actions
'''New bugs of "defect" 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?keywords_type=nowords&o3=notsubstring&emailtype2=notequals&v5=-1y&f3=status_whiteboard&emailreporter1=1&f4=keywords&f2=bug_severity&keywords=intermittent-failure&v1=needinfo%3F&o4=nowords&o2=anyexact&query_format=advanced&query_based_on=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&known_name=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&resolution=---&product=Core&product=Toolkit&o5=greaterthan&emailtype1=notequals&f5=creation_ts&v3=%5Bno-nag%5D&o1=notsubstring&emailreporter2=1&v4=meta&component=about%3Amemory&component=DOM%3A%20Bindings%20%28WebIDL%29&component=DOM%3A%20Copy%20%26%20Paste%20and%20Drag%20%26%20Drop&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%20Navigation&component=DOM%3A%20Selection&component=DOM%3A%20Serializers&component=DOM%3A%20UI%20Events%20%26%20Focus%20Handling&component=DOM%3A%20Window%20and%20Location&component=XML&component=XPConnect&component=XSLT&v2=--%2Cn%2Fa&f1=flagtypes.name&email2=wptsync%40mozilla.bugs&email1=intermittent-bug-filer%40mozilla.bugs&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&bug_type=defect&columnlist=opendate%2Cshort_desc%2Cpriority%2Cbug_severity%2Cbug_type%2Ctriage_owner%2Ccf_status_firefox_nightly%2Ccf_status_firefox_beta%2Ccf_status_firefox_release%2Ccf_status_firefox_esr%2Cproduct%2Ccomponent%2Cbug_status%2Cresolution%2Creporter%2Creporter_realname%2Cassigned_to%2Cchangeddate&list_id=15926871 DOM Core (defects)]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20Fission%20new%20Defect%20bugs&sharer_id=434964&list_id=14982371 DOM Fission]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20UnTriaged&sharer_id=646284 DOM LWS (defects)]
*[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:
 
* P1: this is a major issue and needs to be fixed ASAP. '''You should also ensure someone is assigned or at least needinfoed!'''
'''New S2 crashes that need actions'''
* P2: we should fix this soon (or someone's already working on it)
 
* P3: this should go into the ever-growing pile of "work we should do some day"
According to the current triage policy, new bugs that have "crash" keyword will get S2 automatically. We want to ensure that we look into these new bugs in our team triage practice, too.
* P5: we likely won't spend time on this but if someone contributes a patch, we'd review it (aka "the polite WONTFIX")
*[https://bugzilla.mozilla.org/buglist.cgi?o3=greaterthan&f6=OP&f1=status_whiteboard&component=about%3Amemory&component=DOM%3A%20Bindings%20%28WebIDL%29&component=DOM%3A%20Copy%20%26%20Paste%20and%20Drag%20%26%20Drop&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%20Navigation&component=DOM%3A%20Selection&component=DOM%3A%20Serializers&component=DOM%3A%20UI%20Events%20%26%20Focus%20Handling&component=DOM%3A%20Window%20and%20Location&component=XML&component=XPConnect&component=XSLT&j_top=OR&o5=greaterthan&email2=wptsync%40mozilla.bugs&query_format=advanced&keywords_type=anywords&email1=intermittent-bug-filer%40mozilla.bugs&f4=bug_severity&emailtype1=notequals&list_id=16022603&emailreporter1=1&v4=-1w&f2=keywords&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&query_based_on=DOM%20Core%20S2%20%28new%20crash%20-1w%29&o4=changedafter&f7=CP&o2=nowords&known_name=DOM%20Core%20S2%20%28new%20crash%20-1w%29&resolution=---&emailreporter2=1&product=Core&product=Toolkit&f5=creation_ts&o1=notsubstring&v5=-1w&emailtype2=notequals&f3=creation_ts&bug_type=--&bug_type=defect&bug_type=enhancement&bug_type=task&keywords=crash%2C%20&bug_severity=S2&columnlist=opendate%2Cshort_desc%2Cpriority%2Cbug_severity%2Cbug_type%2Cchangeddate%2Cproduct%2Ccomponent%2Cstatus_whiteboard%2Ccf_status_firefox_nightly%2Ccf_status_firefox_beta%2Ccf_status_firefox_release%2Ccf_status_firefox_esr%2Ctriage_owner%2Cbug_status%2Cresolution%2Creporter%2Creporter_realname%2Cassigned_to DOM Core new S2 crashes, opened in the past week]
 
 
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:
*S1: (Catastrophic) Blocks development/testing, may impact more than 25% of users, causes data loss, potential chemspill, and no workaround available
 
*S2: (Serious) Major Functionality/product severely impaired and a satisfactory workaround doesn't exist


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]].
*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.


* is this bug with the '''right type'''?
* is this bug with the '''right type'''?
* is this bug in the '''correct component'''?
* is this bug in the '''correct component'''?
* do we need a '''regression range'''?
* do we need a '''regression range'''?
* '''needinfo''' for more information, e.g. URL, STR, or module owners' comment, if you can't decide the priority right at the moment
* '''needinfo''' for more information, e.g. URL, STR, or module owners' comment, if you can't decide the severity (and priority) right at the moment
* note: an assumption here is that bugs with non-nobody assignees are progressing towards a fix in some way


==Unanswered-needinfo new defect bugs - do this daily if possible==
==Unanswered-needinfo new defect bugs - do this weekly==
We'd like to see needinfo answered in 10 days.
We'd like to see '''needinfo''' answered in '''10 days'''.
* is there an outstanding needinfo request for any missing information?
* is there an outstanding needinfo request for any missing information?
** is there someone else who could answer?
** is there someone else who could answer?
Line 28: Line 42:
** see above for other tips for dealing with new bugs
** see above for other tips for dealing with new bugs
* do these people or their managers need to be emailed?
* do these people or their managers need to be emailed?
* Set '''priority''' if you've done above and there's no pending needinfo so it doesn't show up in tomorrow's list
* Set '''severity''' if you've done above and there's no pending needinfo so it doesn't show up in tomorrow's list


Bugs with outstanding needinfo?
Bugs with outstanding needinfo?
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20Core%20defect%20pendingNIs&sharer_id=434964&list_id=15178479 DOM Core needinfo?]
*[https://bugzilla.mozilla.org/buglist.cgi?v1=needinfo%3F&o2=anyexact&emailreporter1=1&emailtype1=notequals&resolution=---&v3=%5Bno-nag%5D&known_name=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&f3=status_whiteboard&bug_type=defect&o5=greaterthan&query_format=advanced&email1=intermittent-bug-filer%40mozilla.bugs&f1=flagtypes.name&o4=nowords&columnlist=opendate%2Cshort_desc%2Cpriority%2Cbug_severity%2Cbug_type%2Ctriage_owner%2Ccf_status_firefox_nightly%2Ccf_status_firefox_beta%2Ccf_status_firefox_release%2Ccf_status_firefox_esr%2Cproduct%2Ccomponent%2Cbug_status%2Cresolution%2Creporter%2Creporter_realname%2Cassigned_to%2Cchangeddate&component=about%3Amemory&component=DOM%3A%20Bindings%20%28WebIDL%29&component=DOM%3A%20Copy%20%26%20Paste%20and%20Drag%20%26%20Drop&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%20Navigation&component=DOM%3A%20Selection&component=DOM%3A%20Serializers&component=DOM%3A%20UI%20Events%20%26%20Focus%20Handling&component=DOM%3A%20Window%20and%20Location&component=XML&component=XPConnect&component=XSLT&emailreporter2=1&product=Core&product=Toolkit&v4=meta&keywords_type=nowords&f2=bug_severity&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&v5=-1y&list_id=15926885&email2=wptsync%40mozilla.bugs&emailtype2=notequals&f5=creation_ts&o3=notsubstring&f4=keywords&o1=substring&v2=--%2Cn%2Fa&query_based_on=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&keywords=intermittent-failureDOM DOM Core needinfo?]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20Fission%20defect%20pendingNIs&sharer_id=434964&list_id=14982428 DOM Fission needinfo?]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20UnTriaged%20w%2Fneedinfo&sharer_id=646284&list_id=15925257 DOM LWS needinfo?]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20WorkerAndStorage%20defect%20pendingNIs&sharer_id=434964&list_id=14982435 DOM Worker&Storage needinfo?]


==P1 bugs (including defect, task, enhancement) - do this weekly==
==S1 bugs (including defect, task, enhancement) - do this weekly==
* is there is an assignee?
* is there is an assignee?
* is there anything needed to make this bug move forward?
* is there anything needed to make this bug move forward?
* is this still a valid P1?
* is this still a valid S1?


P1 bugs:
S1 bugs:
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20Core-P1&sharer_id=434964&list_id=14982466 DOM Core P1s]
*[https://bugzilla.mozilla.org/buglist.cgi?known_name=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&v3=-1y&resolution=---&emailtype1=notequals&emailreporter1=1&o2=nowords&v1=%5Bno-nag%5D&bug_severity=S1&component=about%3Amemory&component=DOM%3A%20Bindings%20%28WebIDL%29&component=DOM%3A%20Copy%20%26%20Paste%20and%20Drag%20%26%20Drop&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%20Navigation&component=DOM%3A%20Selection&component=DOM%3A%20Serializers&component=DOM%3A%20UI%20Events%20%26%20Focus%20Handling&component=DOM%3A%20Window%20and%20Location&component=XML&component=XPConnect&component=XSLT&columnlist=opendate%2Cshort_desc%2Cpriority%2Cbug_severity%2Cbug_type%2Ctriage_owner%2Ccf_status_firefox_nightly%2Ccf_status_firefox_beta%2Ccf_status_firefox_release%2Ccf_status_firefox_esr%2Cproduct%2Ccomponent%2Cbug_status%2Cresolution%2Creporter%2Creporter_realname%2Cassigned_to%2Cchangeddate&f1=status_whiteboard&email1=intermittent-bug-filer%40mozilla.bugs&bug_type=--&bug_type=defect&bug_type=enhancement&bug_type=task&f3=creation_ts&query_format=advanced&list_id=15926892&email2=wptsync%40mozilla.bugs&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&f2=keywords&emailreporter2=1&keywords_type=nowords&product=Core&product=Toolkit&v2=meta&o1=notsubstring&keywords=intermittent-failureDOM&query_based_on=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&emailtype2=notequals&o3=greaterthan DOM Core S1s]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20Fission-P1&sharer_id=434964&list_id=14982471 DOM Fission P1s]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20S1&sharer_id=646284 DOM LWS S1s]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20WorkerAndStorage-P1&sharer_id=434964&list_id=14982479 DOM Worker&Storage P1s]


==Severity/Priority nomination==
Make severity changes after review. (De-)Nomination happens at least once a release.


* are any of these super sever and thus really S1?
* if we marked something as S2 and it's been that way for a while, do we really need to keep it as such or could it become a S3?
* is a bug even valid anymore?


==Priority nomination==
== Bugzilla Query List ==
Make P2s to P1s, and P3s to P2s/P1s after review. (De-)Nomination happens at least once a release.
S1 bugs:
*[https://bugzilla.mozilla.org/buglist.cgi?known_name=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&v3=-1y&resolution=---&emailtype1=notequals&emailreporter1=1&o2=nowords&v1=%5Bno-nag%5D&bug_severity=S1&component=about%3Amemory&component=DOM%3A%20Bindings%20%28WebIDL%29&component=DOM%3A%20Copy%20%26%20Paste%20and%20Drag%20%26%20Drop&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%20Navigation&component=DOM%3A%20Selection&component=DOM%3A%20Serializers&component=DOM%3A%20UI%20Events%20%26%20Focus%20Handling&component=DOM%3A%20Window%20and%20Location&component=XML&component=XPConnect&component=XSLT&columnlist=opendate%2Cshort_desc%2Cpriority%2Cbug_severity%2Cbug_type%2Ctriage_owner%2Ccf_status_firefox_nightly%2Ccf_status_firefox_beta%2Ccf_status_firefox_release%2Ccf_status_firefox_esr%2Cproduct%2Ccomponent%2Cbug_status%2Cresolution%2Creporter%2Creporter_realname%2Cassigned_to%2Cchangeddate&f1=status_whiteboard&email1=intermittent-bug-filer%40mozilla.bugs&bug_type=--&bug_type=defect&bug_type=enhancement&bug_type=task&f3=creation_ts&query_format=advanced&list_id=15926892&email2=wptsync%40mozilla.bugs&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&f2=keywords&emailreporter2=1&keywords_type=nowords&product=Core&product=Toolkit&v2=meta&o1=notsubstring&keywords=intermittent-failureDOM&query_based_on=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&emailtype2=notequals&o3=greaterthan DOM Core S1s]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20S1&sharer_id=646284 DOM LWS S1s]


* are any of these super-urgent and thus really P1?
S2 bugs:
* if we marked something as P2 and it's been that way for a while, do we really need to keep it as such or could it become a P3?
*[https://bugzilla.mozilla.org/buglist.cgi?product=Core&product=Toolkit&v2=meta&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&v1=%5Bno-nag%5D&keywords=intermittent-failureDOM&f3=creation_ts&keywords_type=nowords&list_id=16102078&emailreporter2=1&email1=intermittent-bug-filer%40mozilla.bugs&query_based_on=DOM%20Core%20S2&resolution=---&emailtype2=notequals&email2=wptsync%40mozilla.bugs&component=about%3Amemory&component=DOM%3A%20Bindings%20%28WebIDL%29&component=DOM%3A%20Copy%20%26%20Paste%20and%20Drag%20%26%20Drop&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%20Navigation&component=DOM%3A%20Selection&component=DOM%3A%20Serializers&component=DOM%3A%20UI%20Events%20%26%20Focus%20Handling&component=DOM%3A%20Window%20and%20Location&component=XML&component=XPConnect&component=XSLT&o3=greaterthan&known_name=DOM%20Core%20S2&bug_type=--&bug_type=defect&bug_type=enhancement&bug_type=task&columnlist=opendate%2Cshort_desc%2Cpriority%2Cbug_severity%2Cbug_type%2Ctriage_owner%2Ccf_status_firefox_nightly%2Ccf_status_firefox_beta%2Ccf_status_firefox_release%2Ccf_status_firefox_esr%2Cproduct%2Ccomponent%2Cbug_status%2Cresolution%2Creporter%2Creporter_realname%2Cassigned_to%2Cchangeddate&bug_severity=S2&emailtype1=notequals&v3=-&f2=keywords&f1=status_whiteboard&query_format=advanced&o2=nowords&o1=notsubstring&emailreporter1=1 DOM Core S2s]
* is a bug even valid anymore?
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20S2&sharer_id=646284 DOM LWS S2s]


== Bugzilla Query List ==
S3 bugs:
P1 bugs:
*[https://bugzilla.mozilla.org/buglist.cgi?product=Core&product=Toolkit&v2=meta&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&v1=%5Bno-nag%5D&keywords=intermittent-failureDOM&f3=creation_ts&keywords_type=nowords&list_id=16102078&emailreporter2=1&email1=intermittent-bug-filer%40mozilla.bugs&query_based_on=DOM%20Core%20S3&resolution=---&emailtype2=notequals&email2=wptsync%40mozilla.bugs&component=about%3Amemory&component=DOM%3A%20Bindings%20%28WebIDL%29&component=DOM%3A%20Copy%20%26%20Paste%20and%20Drag%20%26%20Drop&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%20Navigation&component=DOM%3A%20Selection&component=DOM%3A%20Serializers&component=DOM%3A%20UI%20Events%20%26%20Focus%20Handling&component=DOM%3A%20Window%20and%20Location&component=XML&component=XPConnect&component=XSLT&o3=greaterthan&known_name=DOM%20Core%20S3&bug_type=--&bug_type=defect&bug_type=enhancement&bug_type=task&columnlist=opendate%2Cshort_desc%2Cpriority%2Cbug_severity%2Cbug_type%2Ctriage_owner%2Ccf_status_firefox_nightly%2Ccf_status_firefox_beta%2Ccf_status_firefox_release%2Ccf_status_firefox_esr%2Cproduct%2Ccomponent%2Cbug_status%2Cresolution%2Creporter%2Creporter_realname%2Cassigned_to%2Cchangeddate&bug_severity=S3&emailtype1=notequals&v3=-&f2=keywords&f1=status_whiteboard&query_format=advanced&o2=nowords&o1=notsubstring&emailreporter1=1 DOM Core S3s]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20Core-P1&sharer_id=434964&list_id=14982466 DOM Core P1s]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20S3&sharer_id=646284 DOM LWS S3s]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20Fission-P1&sharer_id=434964&list_id=14982471 DOM Fission P1s]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20WorkerAndStorage-P1&sharer_id=434964&list_id=14982479 DOM Worker&Storage P1s]


P2 bugs:
S4 bugs:
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20Core-P2&sharer_id=434964&list_id=14982485 DOM Core P2s]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20S4&sharer_id=646284 DOM LWS S4s]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20Fission-P2&sharer_id=434964&list_id=14982490 DOM Fission P2s]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20WorkerAndStorage-P2&sharer_id=434964&list_id=14982497 DOM Worker&Storage P2s]


P3 bugs:
Other useful ones:
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20Core-P3&sharer_id=434964&list_id=14982503 DOM Core P3s]
*'''[https://bugzilla.mozilla.org/buglist.cgi?bug_severity=--&email1=wptsync%40mozilla.bugs&query_format=advanced&chfieldto=Now&short_desc_type=allwordssubstr&list_id=15361191&classification=Components&short_desc=New%20wpt%20failures%20in&chfield=%5BBug%20creation%5D&emailreporter1=1&f5=OP&f6=CP&f7=OP&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&known_name=DOM%20Core%20new%20wpt%20failures&o1=notsubstring&v9=defect&f3=status_whiteboard&f1=flagtypes.name&o3=notsubstring&f2=short_desc&o2=notsubstring&o4=notregexp&columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate%2Cstatus_whiteboard&f4=short_desc&emailtype1=exact&product=Core&resolution=---&f8=CP&query_based_on=DOM%20Core%20new%20wpt%20failures&f9=bug_type&chfieldfrom=2020-04-20&v1=needinfo&o9=equals DOM Core New WPT failures]''', including which passed before but fails recently, or which passes on other browsers but fails only on Firefox. These bugs are excluded from the daily triage practice. It's good to review it regularly (e.g. monthly) as it can be a useful input to understand our interoperability situation and to prioritize the future work.
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20Fission-P3&sharer_id=434964&list_id=14982555 DOM Fission P3s]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20WorkerAndStorage-P3&sharer_id=434964&list_id=14982513 DOM Worker&Storage P3s]


==Chipping away at bugs that may have been forgotten - doesn't have to be done daily==
==Chipping away at bugs that may have been forgotten - doesn't have to be done daily==
Line 75: Line 88:
* is this bug even valid anymore?
* is this bug even valid anymore?


Old bugs that need re-prioritization or re-validation
Bugs with old (pre S1-S4) severity values:
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20Core-old%20no%20priority&sharer_id=434964&list_id=14982537 DOM Core]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20OldSeverity&sharer_id=646284&list_id=15925317 DOM LWS defects with old severity]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20Fission-old%20no%20priority&sharer_id=434964&list_id=14982556 DOM Fission]
 
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20WorkerAndStorage-old%20no%20priority&sharer_id=434964&list_id=14982557 DOM Worker&Storage]
Bugs that have not been touched for more than a year:
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20Core-old%20no%20priority&sharer_id=434964&list_id=14982537 DOM Core (query needs update)]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20unchanged%20for%20a%20year&sharer_id=646284 DOM LWS unchanged for a year]


== References ==
== References ==
Blink's [http://www.chromium.org/for-testers/bug-reporting-guidelines/triage-best-practices Triage Best Practices] document is a nice read
Blink's [https://www.chromium.org/for-testers/bug-reporting-guidelines/triage-best-practices Triage Best Practices] document is a nice read

Latest revision as of 14:29, 9 June 2022

Overview

Here gives an overview of how we do triage and what each priority means. We now have three types of bugs: defect, task and enhancement. Our engineering daily triage practice focuses on defect and task bugs. Bugs with type task or enhancement will generally be reviewed with PM/EPM. The goal is to set a Severity in as little time as possible and to drive timely actions for important bugs.

As of the new Mozilla triage practice starting in May 04, 2020, we set the Severity field to a non-default value when triaging Firefox related bugs.

New bugs of "defect" type - do this daily

New bugs of "defect" type that need actions


New S2 crashes that need actions

According to the current triage policy, new bugs that have "crash" keyword will get S2 automatically. We want to ensure that we look into these new bugs in our team triage practice, too.


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:

  • S1: (Catastrophic) Blocks development/testing, may impact more than 25% of users, causes data loss, potential chemspill, and no workaround available
  • 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 fixable when we get around to attempting to fix them.

  • is this bug with the right type?
  • is this bug in the correct component?
  • do we need a regression range?
  • needinfo for more information, e.g. URL, STR, or module owners' comment, if you can't decide the severity (and priority) right at the moment

Unanswered-needinfo new defect bugs - do this weekly

We'd like to see needinfo answered in 10 days.

  • is there an outstanding needinfo request for any missing information?
    • is there someone else who could answer?
    • is there a more appropriate person to needinfo?
    • see above for other tips for dealing with new bugs
  • do these people or their managers need to be emailed?
  • Set severity if you've done above and there's no pending needinfo so it doesn't show up in tomorrow's list

Bugs with outstanding needinfo?

S1 bugs (including defect, task, enhancement) - do this weekly

  • is there is an assignee?
  • is there anything needed to make this bug move forward?
  • is this still a valid S1?

S1 bugs:

Severity/Priority nomination

Make severity changes after review. (De-)Nomination happens at least once a release.

  • are any of these super sever and thus really S1?
  • if we marked something as S2 and it's been that way for a while, do we really need to keep it as such or could it become a S3?
  • is a bug even valid anymore?

Bugzilla Query List

S1 bugs:

S2 bugs:

S3 bugs:

S4 bugs:

Other useful ones:

  • DOM Core New WPT failures, including which passed before but fails recently, or which passes on other browsers but fails only on Firefox. These bugs are excluded from the daily triage practice. It's good to review it regularly (e.g. monthly) as it can be a useful input to understand our interoperability situation and to prioritize the future work.

Chipping away at bugs that may have been forgotten - doesn't have to be done daily

  • is there anything needed to make this bug actionable?
  • is this bug being prioritized appropriately?
  • is this bug even valid anymore?

Bugs with old (pre S1-S4) severity values:

Bugs that have not been touched for more than a year:

References

Blink's Triage Best Practices document is a nice read

Retrieved from "https://wiki.mozilla.org/index.php?title=DOM/Triage&oldid=1242872"