MozillaWiki - User contributions [en]

DOM/Core

2023-12-14T13:29:04Z

Hsinyi: group member change

== DOM: Core ==

=== Who are we? ===
* Adam Vandolder
* Andreas Farre
* Andrew McCreight
* Edgar Chen
* Henri Sivonen
* Hsin-Yi Tsai
* Jan-Niklas Jäschke
* Masayuki Nakano
* Oliver Medhurst
* Peter Van der Beken
* Sean Feng
* Simon Pieters
* Vincent Hilla

=== What do we do? ===
We care about Web compatibility and interoperability. We advance the Web by contributing to evolving and implementing W3C and WHATWG Standards, including
* DOM
* HTML
* Events
* Editor
* Clipboard
* Selection
* WebIDL

Our bugzilla components:
* Toolkit::about:memory
* Core::DOM: Bindings (WebIDL)
* Core::DOM: Copy & Paste and Drag & Drop
* Core::DOM: Core & HTML
* Core::DOM: Editor
* Core::DOM: Events
* Core::DOM: Forms
* Core::DOM: Geolocation
* Core::DOM: HTML Parser
* Core::DOM: Navigation
* Core::DOM: Selection
* Core::DOM: Serializers
* Core::DOM: UI Events & Focus Handling
* Core::DOM: Window and Location
* Core::XML
* Core::XPConnect
* Core::XSLT

=== Where to find us? ===
We are at Matrix [https://chat.mozilla.org/#/room/#domcore:mozilla.org #DOM Core] channel

=== Help us with Good First Bugs ===
Working in open is the norm to us. Talk with and join us if you want to help. [https://firefox-source-docs.mozilla.org/contributing/contribution_quickref.html Here] is the Firefox Contributors’ Quick Reference. We've selected [https://bugzilla.mozilla.org/buglist.cgi?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&emailtype2=notequals&f3=creation_ts&email1=intermittent-bug-filer%40mozilla.bugs&emailtype1=notequals&bug_type=--&bug_type=defect&bug_type=enhancement&bug_type=task&resolution=---&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&f1=status_whiteboard&o2=nowords&known_name=DOM%20Core%20S2&f2=keywords&o1=notsubstring&product=Core&product=Toolkit&v1=%5Bno-nag%5D&keywords_type=anywords&v3=-&component=about%3Amemory&component=Cycle%20Collector&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&list_id=16582932&o3=greaterthan&email2=wptsync%40mozilla.bugs&query_format=advanced&keywords=good-first-bug%2C%20 Good First Bugs] to help you take your first steps into the DOM Core code!

<bugzilla>
{
"f1":"keywords",
"o1":"anywordssubstr",
"v1":"good-first-bug",
"component": ["Cycle Collector", "DOM: Bindings (WebIDL)", "DOM: Copy & Paste and Drag & Drop", "DOM: Core & HTML", "DOM: Editor", "DOM: Events", "DOM: Forms", "DOM: Geolocation", "DOM: HTML Parser", "DOM: Navigation", "DOM: Selection", "DOM: Serializers", "DOM: UI Events & Focus Handling", "DOM: Window and Location", "XML", "XPConnect", "XSLT"],
"include_fields":"id,summary,status,severity, priority, updated",
"resolution":["---"]
}
</bugzilla>

DOM/Core

2023-06-05T13:52:59Z

Hsinyi: /* Help us with Good First Bugs */ minor table changes

== DOM: Core ==

=== Who are we? ===
* Adam Vandolder
* Andreas Farre
* Andrew McCreight
* Edgar Chen
* Henri Sivonen
* Hsin-Yi Tsai
* Jan-Niklas Jäschke
* Kris Maglione
* Masayuki Nakano
* Peter Van der Beken
* Sean Feng
* Simon Pieters
* Vincent Hilla

=== What do we do? ===
We care about Web compatibility and interoperability. We advance the Web by contributing to evolving and implementing W3C and WHATWG Standards, including
* DOM
* HTML
* Events
* Editor
* Clipboard
* Selection
* WebIDL

Our bugzilla components:
* Toolkit::about:memory
* Core::DOM: Bindings (WebIDL)
* Core::DOM: Copy & Paste and Drag & Drop
* Core::DOM: Core & HTML
* Core::DOM: Editor
* Core::DOM: Events
* Core::DOM: Forms
* Core::DOM: Geolocation
* Core::DOM: HTML Parser
* Core::DOM: Navigation
* Core::DOM: Selection
* Core::DOM: Serializers
* Core::DOM: UI Events & Focus Handling
* Core::DOM: Window and Location
* Core::XML
* Core::XPConnect
* Core::XSLT

=== Where to find us? ===
We are at Matrix [https://chat.mozilla.org/#/room/#domcore:mozilla.org #DOM Core] channel

=== Help us with Good First Bugs ===
Working in open is the norm to us. Talk with and join us if you want to help. [https://firefox-source-docs.mozilla.org/contributing/contribution_quickref.html Here] is the Firefox Contributors’ Quick Reference. We've selected [https://bugzilla.mozilla.org/buglist.cgi?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&emailtype2=notequals&f3=creation_ts&email1=intermittent-bug-filer%40mozilla.bugs&emailtype1=notequals&bug_type=--&bug_type=defect&bug_type=enhancement&bug_type=task&resolution=---&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&f1=status_whiteboard&o2=nowords&known_name=DOM%20Core%20S2&f2=keywords&o1=notsubstring&product=Core&product=Toolkit&v1=%5Bno-nag%5D&keywords_type=anywords&v3=-&component=about%3Amemory&component=Cycle%20Collector&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&list_id=16582932&o3=greaterthan&email2=wptsync%40mozilla.bugs&query_format=advanced&keywords=good-first-bug%2C%20 Good First Bugs] to help you take your first steps into the DOM Core code!

<bugzilla>
{
"f1":"keywords",
"o1":"anywordssubstr",
"v1":"good-first-bug",
"component": ["Cycle Collector", "DOM: Bindings (WebIDL)", "DOM: Copy & Paste and Drag & Drop", "DOM: Core & HTML", "DOM: Editor", "DOM: Events", "DOM: Forms", "DOM: Geolocation", "DOM: HTML Parser", "DOM: Navigation", "DOM: Selection", "DOM: Serializers", "DOM: UI Events & Focus Handling", "DOM: Window and Location", "XML", "XPConnect", "XSLT"],
"include_fields":"id,summary,status,severity, priority, updated",
"resolution":["---"]
}
</bugzilla>

DOM/Core

2023-06-05T13:49:48Z

Hsinyi: add good first bugs

== DOM: Core ==

=== Who are we? ===
* Adam Vandolder
* Andreas Farre
* Andrew McCreight
* Edgar Chen
* Henri Sivonen
* Hsin-Yi Tsai
* Jan-Niklas Jäschke
* Kris Maglione
* Masayuki Nakano
* Peter Van der Beken
* Sean Feng
* Simon Pieters
* Vincent Hilla

=== What do we do? ===
We care about Web compatibility and interoperability. We advance the Web by contributing to evolving and implementing W3C and WHATWG Standards, including
* DOM
* HTML
* Events
* Editor
* Clipboard
* Selection
* WebIDL

Our bugzilla components:
* Toolkit::about:memory
* Core::DOM: Bindings (WebIDL)
* Core::DOM: Copy & Paste and Drag & Drop
* Core::DOM: Core & HTML
* Core::DOM: Editor
* Core::DOM: Events
* Core::DOM: Forms
* Core::DOM: Geolocation
* Core::DOM: HTML Parser
* Core::DOM: Navigation
* Core::DOM: Selection
* Core::DOM: Serializers
* Core::DOM: UI Events & Focus Handling
* Core::DOM: Window and Location
* Core::XML
* Core::XPConnect
* Core::XSLT

=== Where to find us? ===
We are at Matrix [https://chat.mozilla.org/#/room/#domcore:mozilla.org #DOM Core] channel

=== Help us with Good First Bugs ===
Working in open is the norm to us. Talk with and join us if you want to help. [https://firefox-source-docs.mozilla.org/contributing/contribution_quickref.html Here] is the Firefox Contributors’ Quick Reference. We've selected [https://bugzilla.mozilla.org/buglist.cgi?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&emailtype2=notequals&f3=creation_ts&email1=intermittent-bug-filer%40mozilla.bugs&emailtype1=notequals&bug_type=--&bug_type=defect&bug_type=enhancement&bug_type=task&resolution=---&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&f1=status_whiteboard&o2=nowords&known_name=DOM%20Core%20S2&f2=keywords&o1=notsubstring&product=Core&product=Toolkit&v1=%5Bno-nag%5D&keywords_type=anywords&v3=-&component=about%3Amemory&component=Cycle%20Collector&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&list_id=16582932&o3=greaterthan&email2=wptsync%40mozilla.bugs&query_format=advanced&keywords=good-first-bug%2C%20 Good First Bugs] to help you take your first steps into the DOM Core code!

<bugzilla>
{
"f1":"keywords",
"o1":"anywordssubstr",
"v1":"good-first-bug",
"component": ["Cycle Collector", "DOM: Bindings (WebIDL)", "DOM: Copy & Paste and Drag & Drop", "DOM: Core & HTML", "DOM: Editor", "DOM: Events", "DOM: Forms", "DOM: Geolocation", "DOM: HTML Parser", "DOM: Navigation", "DOM: Selection", "DOM: Serializers", "DOM: UI Events & Focus Handling", "DOM: Window and Location", "XML", "XPConnect", "XSLT"],
"include_fields":"id,summary,status,resolution, priority",
"resolution":["---"]
}
</bugzilla>

DOM/Core

2023-05-30T10:13:12Z

Hsinyi: create DOM: Core subpage

DOM/Triage

2022-06-09T14:29:14Z

Hsinyi: /* Bugzilla Query List */ DOM Core S3

= 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://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 that need actions'''
*[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=DOMLWS%20UnTriaged&sharer_id=646284 DOM LWS (defects)]

'''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.
*[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

*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 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?
*[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=DOMLWS%20UnTriaged%20w%2Fneedinfo&sharer_id=646284&list_id=15925257 DOM LWS 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:
*[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]

==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:
*[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]

S2 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%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]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20S2&sharer_id=646284 DOM LWS S2s]

S3 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=DOMLWS%20S3&sharer_id=646284 DOM LWS S3s]

S4 bugs:
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20S4&sharer_id=646284 DOM LWS S4s]

Other useful ones:
*'''[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.

==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:
*[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]

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 ==
Blink's [https://www.chromium.org/for-testers/bug-reporting-guidelines/triage-best-practices Triage Best Practices] document is a nice read

DOM/Triage

2022-06-01T08:02:09Z

Hsinyi: /* Bugzilla Query List */ update DOM Core S2

= 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://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 that need actions'''
*[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=DOMLWS%20UnTriaged&sharer_id=646284 DOM LWS (defects)]

'''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.
*[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

*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 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?
*[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=DOMLWS%20UnTriaged%20w%2Fneedinfo&sharer_id=646284&list_id=15925257 DOM LWS 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:
*[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]

==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:
*[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]

S2 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%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]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20S2&sharer_id=646284 DOM LWS S2s]

S3 bugs:
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20S3&sharer_id=646284 DOM LWS S3s]

S4 bugs:
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20S4&sharer_id=646284 DOM LWS S4s]

Other useful ones:
*'''[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.

==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:
*[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]

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 ==
Blink's [https://www.chromium.org/for-testers/bug-reporting-guidelines/triage-best-practices Triage Best Practices] document is a nice read

DOM/Triage

2022-03-15T13:11:44Z

Hsinyi: /* New bugs of "defect" type - do this daily */ minor changes

= 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://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 that need actions'''
*[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=DOMLWS%20UnTriaged&sharer_id=646284 DOM LWS (defects)]

'''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.
*[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

*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 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?
*[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=DOMLWS%20UnTriaged%20w%2Fneedinfo&sharer_id=646284&list_id=15925257 DOM LWS 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:
*[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]

==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:
*[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]

S2 bugs:
*[https://bugzilla.mozilla.org/buglist.cgi?product=Core&product=Toolkit&keywords_type=nowords&bug_type=--&bug_type=defect&bug_type=enhancement&bug_type=task&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&bug_severity=S2&emailreporter2=1&query_based_on=DOM%20Core%20S2&o3=greaterthan&o1=notsubstring&o2=nowords&keywords=intermittent-failureDOM&known_name=DOM%20Core%20S2&f3=creation_ts&f2=keywords&f1=status_whiteboard&v3=-1y&v2=meta&v1=%5Bno-nag%5D&email2=wptsync%40mozilla.bugs&list_id=15966377&resolution=---&emailtype1=notequals&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&emailtype2=notequals&query_format=advanced&emailreporter1=1&email1=intermittent-bug-filer%40mozilla.bugs&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 DOM Core S2s]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20S2&sharer_id=646284 DOM LWS S2s]

S3 bugs:
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20S3&sharer_id=646284 DOM LWS S3s]

S4 bugs:
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20S4&sharer_id=646284 DOM LWS S4s]

Other useful ones:
*'''[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.

==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:
*[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]

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 ==
Blink's [https://www.chromium.org/for-testers/bug-reporting-guidelines/triage-best-practices Triage Best Practices] document is a nice read

DOM/Triage

2022-03-15T13:10:32Z

Hsinyi: /* New bugs of "defect" type - do this daily */ DOM Core new S2 crashes

= 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://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 that need actions
*[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=DOMLWS%20UnTriaged&sharer_id=646284 DOM LWS (defects)]

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

*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 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?
*[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=DOMLWS%20UnTriaged%20w%2Fneedinfo&sharer_id=646284&list_id=15925257 DOM LWS 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:
*[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]

==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:
*[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]

S2 bugs:
*[https://bugzilla.mozilla.org/buglist.cgi?product=Core&product=Toolkit&keywords_type=nowords&bug_type=--&bug_type=defect&bug_type=enhancement&bug_type=task&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&bug_severity=S2&emailreporter2=1&query_based_on=DOM%20Core%20S2&o3=greaterthan&o1=notsubstring&o2=nowords&keywords=intermittent-failureDOM&known_name=DOM%20Core%20S2&f3=creation_ts&f2=keywords&f1=status_whiteboard&v3=-1y&v2=meta&v1=%5Bno-nag%5D&email2=wptsync%40mozilla.bugs&list_id=15966377&resolution=---&emailtype1=notequals&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&emailtype2=notequals&query_format=advanced&emailreporter1=1&email1=intermittent-bug-filer%40mozilla.bugs&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 DOM Core S2s]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20S2&sharer_id=646284 DOM LWS S2s]

S3 bugs:
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20S3&sharer_id=646284 DOM LWS S3s]

S4 bugs:
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20S4&sharer_id=646284 DOM LWS S4s]

Other useful ones:
*'''[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.

==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:
*[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]

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 ==
Blink's [https://www.chromium.org/for-testers/bug-reporting-guidelines/triage-best-practices Triage Best Practices] document is a nice read

DOM/Triage

2022-01-19T10:26:36Z

Hsinyi: /* Bugzilla Query List */ update DOM Core S2

= 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://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 that need actions
*[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=DOMLWS%20UnTriaged&sharer_id=646284 DOM LWS (defects)]
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 fix''able'' 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?
*[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=DOMLWS%20UnTriaged%20w%2Fneedinfo&sharer_id=646284&list_id=15925257 DOM LWS 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:
*[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]

==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:
*[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]

S2 bugs:
*[https://bugzilla.mozilla.org/buglist.cgi?product=Core&product=Toolkit&keywords_type=nowords&bug_type=--&bug_type=defect&bug_type=enhancement&bug_type=task&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&bug_severity=S2&emailreporter2=1&query_based_on=DOM%20Core%20S2&o3=greaterthan&o1=notsubstring&o2=nowords&keywords=intermittent-failureDOM&known_name=DOM%20Core%20S2&f3=creation_ts&f2=keywords&f1=status_whiteboard&v3=-1y&v2=meta&v1=%5Bno-nag%5D&email2=wptsync%40mozilla.bugs&list_id=15966377&resolution=---&emailtype1=notequals&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&emailtype2=notequals&query_format=advanced&emailreporter1=1&email1=intermittent-bug-filer%40mozilla.bugs&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 DOM Core S2s]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20S2&sharer_id=646284 DOM LWS S2s]

S3 bugs:
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20S3&sharer_id=646284 DOM LWS S3s]

S4 bugs:
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20S4&sharer_id=646284 DOM LWS S4s]

Other useful ones:
*'''[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.

==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:
*[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]

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 ==
Blink's [https://www.chromium.org/for-testers/bug-reporting-guidelines/triage-best-practices Triage Best Practices] document is a nice read

DOM/Triage

2021-12-07T13:56:35Z

Hsinyi: /* Bugzilla Query List */ DOM Core S1 & S2

= 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://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 that need actions
*[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=DOMLWS%20UnTriaged&sharer_id=646284 DOM LWS (defects)]
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 fix''able'' 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?
*[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=DOMLWS%20UnTriaged%20w%2Fneedinfo&sharer_id=646284&list_id=15925257 DOM LWS 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:
*[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]

==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:
*[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]

S2 bugs:
*[https://bugzilla.mozilla.org/buglist.cgi?f2=keywords&email1=intermittent-bug-filer%40mozilla.bugs&v3=-1y&query_based_on=DOM%20Core%20S1&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&emailreporter1=1&f1=status_whiteboard&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&emailtype2=notequals&emailtype1=notequals&keywords_type=nowords&f3=creation_ts&v2=meta&bug_severity=S2&v1=%5Bno-nag%5D&email2=wptsync%40mozilla.bugs&emailreporter2=1&bug_type=--&bug_type=defect&bug_type=enhancement&bug_type=task&query_format=advanced&o3=greaterthan&keywords=intermittent-failureDOM&product=Core&product=Toolkit&list_id=15926897&resolution=---&o1=notsubstring&known_name=DOM%20Core%20S1&o2=nowords&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 DOM Core S2s]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20S2&sharer_id=646284 DOM LWS S2s]

S3 bugs:
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20S3&sharer_id=646284 DOM LWS S3s]

S4 bugs:
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20S4&sharer_id=646284 DOM LWS S4s]

Other useful ones:
*'''[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.

==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:
*[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]

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 ==
Blink's [https://www.chromium.org/for-testers/bug-reporting-guidelines/triage-best-practices Triage Best Practices] document is a nice read

DOM/Triage

2021-12-07T13:54:25Z

Hsinyi: /* S1 bugs (including defect, task, enhancement) - do this weekly */ DOM Core

= 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://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 that need actions
*[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=DOMLWS%20UnTriaged&sharer_id=646284 DOM LWS (defects)]
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 fix''able'' 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?
*[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=DOMLWS%20UnTriaged%20w%2Fneedinfo&sharer_id=646284&list_id=15925257 DOM LWS 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:
*[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]

==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:
*[https://bugzilla.mozilla.org/buglist.cgi?o1=notsubstring&f3=bug_severity&f1=flagtypes.name&o3=equals&emailreporter1=1&chfield=%5BBug%20creation%5D&f5=CP&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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%20S1&list_id=15361214&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&email1=intermittent-bug-filer%40mozilla.bugs&query_format=advanced&j2=OR&chfieldfrom=2020-04-20&v3=S1&emailtype2=notequals&emailtype1=notequals&resolution=---&product=Core&query_based_on=DOM%20Core%20S1&emailreporter2=1&email2=wptsync%40mozilla.bugs&o4=equals&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&f4=component&f2=OP DOM Core S1s]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20S1&sharer_id=646284 DOM LWS S1s]

S2 bugs:
*[https://bugzilla.mozilla.org/buglist.cgi?f4=component&chfieldfrom=2020-04-20&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&email1=intermittent-bug-filer%40mozilla.bugs&emailtype2=notequals&o4=equals&chfield=%5BBug%20creation%5D&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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&j2=OR&emailtype1=notequals&f5=CP&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&o1=notsubstring&o3=equals&emailreporter2=1&email2=wptsync%40mozilla.bugs&product=Core&f3=bug_severity&f1=flagtypes.name&f2=OP&list_id=15361211&query_format=advanced&v3=S2&query_based_on=DOM%20Core%20S1&known_name=DOM%20Core%20S1&emailreporter1=1&resolution=--- DOM Core S2s]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20S2&sharer_id=646284 DOM LWS S2s]

S3 bugs:
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20S3&sharer_id=646284 DOM LWS S3s]

S4 bugs:
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20S4&sharer_id=646284 DOM LWS S4s]

Other useful ones:
*'''[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.

==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:
*[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]

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 ==
Blink's [https://www.chromium.org/for-testers/bug-reporting-guidelines/triage-best-practices Triage Best Practices] document is a nice read

DOM/Triage

2021-12-07T13:52:33Z

Hsinyi: /* Unanswered-needinfo new defect bugs - do this weekly */ typo

= 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://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 that need actions
*[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=DOMLWS%20UnTriaged&sharer_id=646284 DOM LWS (defects)]
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 fix''able'' 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?
*[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=DOMLWS%20UnTriaged%20w%2Fneedinfo&sharer_id=646284&list_id=15925257 DOM LWS 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:
*[https://bugzilla.mozilla.org/buglist.cgi?f5=CP&emailtype1=notequals&j2=OR&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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&chfield=%5BBug%20creation%5D&o4=equals&emailtype2=notequals&email1=intermittent-bug-filer%40mozilla.bugs&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&chfieldfrom=2020-04-20&f4=component&resolution=---&emailreporter1=1&known_name=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&query_based_on=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&v3=S1&query_format=advanced&list_id=15354367&f1=flagtypes.name&f2=OP&f3=bug_severity&product=Core&email2=wptsync%40mozilla.bugs&emailreporter2=1&o3=equals&o1=notsubstring&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 DOM Core S1s]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20S1&sharer_id=646284 DOM LWS S1s]

==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:
*[https://bugzilla.mozilla.org/buglist.cgi?o1=notsubstring&f3=bug_severity&f1=flagtypes.name&o3=equals&emailreporter1=1&chfield=%5BBug%20creation%5D&f5=CP&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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%20S1&list_id=15361214&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&email1=intermittent-bug-filer%40mozilla.bugs&query_format=advanced&j2=OR&chfieldfrom=2020-04-20&v3=S1&emailtype2=notequals&emailtype1=notequals&resolution=---&product=Core&query_based_on=DOM%20Core%20S1&emailreporter2=1&email2=wptsync%40mozilla.bugs&o4=equals&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&f4=component&f2=OP DOM Core S1s]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20S1&sharer_id=646284 DOM LWS S1s]

S2 bugs:
*[https://bugzilla.mozilla.org/buglist.cgi?f4=component&chfieldfrom=2020-04-20&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&email1=intermittent-bug-filer%40mozilla.bugs&emailtype2=notequals&o4=equals&chfield=%5BBug%20creation%5D&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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&j2=OR&emailtype1=notequals&f5=CP&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&o1=notsubstring&o3=equals&emailreporter2=1&email2=wptsync%40mozilla.bugs&product=Core&f3=bug_severity&f1=flagtypes.name&f2=OP&list_id=15361211&query_format=advanced&v3=S2&query_based_on=DOM%20Core%20S1&known_name=DOM%20Core%20S1&emailreporter1=1&resolution=--- DOM Core S2s]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20S2&sharer_id=646284 DOM LWS S2s]

S3 bugs:
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20S3&sharer_id=646284 DOM LWS S3s]

S4 bugs:
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20S4&sharer_id=646284 DOM LWS S4s]

Other useful ones:
*'''[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.

==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:
*[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]

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 ==
Blink's [https://www.chromium.org/for-testers/bug-reporting-guidelines/triage-best-practices Triage Best Practices] document is a nice read

DOM/Triage

2021-12-07T13:51:57Z

Hsinyi: /* Unanswered-needinfo new defect bugs - do this weekly */ DOM Core updates

= 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://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 that need actions
*[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=DOMLWS%20UnTriaged&sharer_id=646284 DOM LWS (defects)]
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 fix''able'' 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?
*[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 Core 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?]

==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:
*[https://bugzilla.mozilla.org/buglist.cgi?f5=CP&emailtype1=notequals&j2=OR&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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&chfield=%5BBug%20creation%5D&o4=equals&emailtype2=notequals&email1=intermittent-bug-filer%40mozilla.bugs&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&chfieldfrom=2020-04-20&f4=component&resolution=---&emailreporter1=1&known_name=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&query_based_on=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&v3=S1&query_format=advanced&list_id=15354367&f1=flagtypes.name&f2=OP&f3=bug_severity&product=Core&email2=wptsync%40mozilla.bugs&emailreporter2=1&o3=equals&o1=notsubstring&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 DOM Core S1s]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20S1&sharer_id=646284 DOM LWS S1s]

==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:
*[https://bugzilla.mozilla.org/buglist.cgi?o1=notsubstring&f3=bug_severity&f1=flagtypes.name&o3=equals&emailreporter1=1&chfield=%5BBug%20creation%5D&f5=CP&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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%20S1&list_id=15361214&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&email1=intermittent-bug-filer%40mozilla.bugs&query_format=advanced&j2=OR&chfieldfrom=2020-04-20&v3=S1&emailtype2=notequals&emailtype1=notequals&resolution=---&product=Core&query_based_on=DOM%20Core%20S1&emailreporter2=1&email2=wptsync%40mozilla.bugs&o4=equals&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&f4=component&f2=OP DOM Core S1s]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20S1&sharer_id=646284 DOM LWS S1s]

S2 bugs:
*[https://bugzilla.mozilla.org/buglist.cgi?f4=component&chfieldfrom=2020-04-20&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&email1=intermittent-bug-filer%40mozilla.bugs&emailtype2=notequals&o4=equals&chfield=%5BBug%20creation%5D&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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&j2=OR&emailtype1=notequals&f5=CP&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&o1=notsubstring&o3=equals&emailreporter2=1&email2=wptsync%40mozilla.bugs&product=Core&f3=bug_severity&f1=flagtypes.name&f2=OP&list_id=15361211&query_format=advanced&v3=S2&query_based_on=DOM%20Core%20S1&known_name=DOM%20Core%20S1&emailreporter1=1&resolution=--- DOM Core S2s]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20S2&sharer_id=646284 DOM LWS S2s]

S3 bugs:
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20S3&sharer_id=646284 DOM LWS S3s]

S4 bugs:
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20S4&sharer_id=646284 DOM LWS S4s]

Other useful ones:
*'''[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.

==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:
*[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]

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 ==
Blink's [https://www.chromium.org/for-testers/bug-reporting-guidelines/triage-best-practices Triage Best Practices] document is a nice read

DOM/Triage

2021-12-07T13:47:52Z

Hsinyi: /* New bugs of "defect" type - do this daily */ DOM Core updates

= 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://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 that need actions
*[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=DOMLWS%20UnTriaged&sharer_id=646284 DOM LWS (defects)]
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 fix''able'' 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?
*[https://bugzilla.mozilla.org/buglist.cgi?product=Core&f4=cf_tracking_e10s&query_format=advanced&f1=flagtypes.name&v4=%20&v1=needinfo&o4=notequals&emailreporter2=1&o1=substring&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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&emailreporter1=1&o9=notsubstring&o8=notregexp&f7=status_whiteboard&f9=keywords&emailtype2=notequals&o7=notsubstring&f8=short_desc&f11=CP&query_based_on=DOM%20Core%20defect%20pendingNIs%20%28w%2Fo%20severity%29&f5=short_desc&known_name=DOM%20Core%20defect%20pendingNIs%20%28w%2Fo%20severity%29&email2=intermittent-bug-filer%40mozilla.bugs&chfieldfrom=2016-06-01&bug_severity=--&f2=bug_type&f6=assigned_to&o6=equals&o2=equals&chfield=%5BBug%20creation%5D&o5=notsubstring&f10=OP&v6=nobody%40mozilla.org&list_id=15354385&o3=notregexp&columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cshort_desc%2Cchangeddate%2Cstatus_whiteboard%2Cbug_severity%2Cpriority%2Cflagtypes.name&chfieldto=Now&email1=wptsync%40mozilla.bugs&classification=Components&resolution=---&f3=keywords&emailtype1=notequals DOM Core needinfo? (all types)]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20UnTriaged%20w%2Fneedinfo&sharer_id=646284&list_id=15925257 DOM LWS 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:
*[https://bugzilla.mozilla.org/buglist.cgi?f5=CP&emailtype1=notequals&j2=OR&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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&chfield=%5BBug%20creation%5D&o4=equals&emailtype2=notequals&email1=intermittent-bug-filer%40mozilla.bugs&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&chfieldfrom=2020-04-20&f4=component&resolution=---&emailreporter1=1&known_name=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&query_based_on=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&v3=S1&query_format=advanced&list_id=15354367&f1=flagtypes.name&f2=OP&f3=bug_severity&product=Core&email2=wptsync%40mozilla.bugs&emailreporter2=1&o3=equals&o1=notsubstring&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 DOM Core S1s]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20S1&sharer_id=646284 DOM LWS S1s]

==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:
*[https://bugzilla.mozilla.org/buglist.cgi?o1=notsubstring&f3=bug_severity&f1=flagtypes.name&o3=equals&emailreporter1=1&chfield=%5BBug%20creation%5D&f5=CP&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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%20S1&list_id=15361214&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&email1=intermittent-bug-filer%40mozilla.bugs&query_format=advanced&j2=OR&chfieldfrom=2020-04-20&v3=S1&emailtype2=notequals&emailtype1=notequals&resolution=---&product=Core&query_based_on=DOM%20Core%20S1&emailreporter2=1&email2=wptsync%40mozilla.bugs&o4=equals&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&f4=component&f2=OP DOM Core S1s]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20S1&sharer_id=646284 DOM LWS S1s]

S2 bugs:
*[https://bugzilla.mozilla.org/buglist.cgi?f4=component&chfieldfrom=2020-04-20&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&email1=intermittent-bug-filer%40mozilla.bugs&emailtype2=notequals&o4=equals&chfield=%5BBug%20creation%5D&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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&j2=OR&emailtype1=notequals&f5=CP&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&o1=notsubstring&o3=equals&emailreporter2=1&email2=wptsync%40mozilla.bugs&product=Core&f3=bug_severity&f1=flagtypes.name&f2=OP&list_id=15361211&query_format=advanced&v3=S2&query_based_on=DOM%20Core%20S1&known_name=DOM%20Core%20S1&emailreporter1=1&resolution=--- DOM Core S2s]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20S2&sharer_id=646284 DOM LWS S2s]

S3 bugs:
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20S3&sharer_id=646284 DOM LWS S3s]

S4 bugs:
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOMLWS%20S4&sharer_id=646284 DOM LWS S4s]

Other useful ones:
*'''[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.

==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:
*[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]

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 ==
Blink's [https://www.chromium.org/for-testers/bug-reporting-guidelines/triage-best-practices Triage Best Practices] document is a nice read

DOM/Triage

2021-10-05T13:08:43Z

Hsinyi: /* New bugs of "defect" type - do this daily */ DOM Core updates - be the same with autonag inquiry

= 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://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 that need actions
*[https://bugzilla.mozilla.org/buglist.cgi?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=XML&component=XPConnect&component=XSLT&o4=nowords&v2=--%2Cn%2Fa&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&f2=bug_severity&emailreporter2=1&email1=intermittent-bug-filer%40mozilla.bugs&v5=-1y&keywords_type=nowords&email2=wptsync%40mozilla.bugs&product=Core&product=Toolkit&query_based_on=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&bug_type=defect&f5=creation_ts&v1=needinfo%3F&known_name=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&emailreporter1=1&o3=notsubstring&f1=flagtypes.name&emailtype2=notequals&o5=greaterthan&keywords=intermittent-failure&resolution=---&v3=%5Bno-nag%5D&o1=notsubstring&f3=status_whiteboard&emailtype1=notequals&query_format=advanced&f4=keywords&v4=meta&o2=anyexact&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software 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 (needs update per the new "Severity triage" practice)]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20WorkerAndStorage%20-%20new%20Defect%20bugs&sharer_id=434964&list_id=14982384 DOM Workers & Storage(needs update per the new "Severity triage" practice)]
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 fix''able'' 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?
*[https://bugzilla.mozilla.org/buglist.cgi?product=Core&f4=cf_tracking_e10s&query_format=advanced&f1=flagtypes.name&v4=%20&v1=needinfo&o4=notequals&emailreporter2=1&o1=substring&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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&emailreporter1=1&o9=notsubstring&o8=notregexp&f7=status_whiteboard&f9=keywords&emailtype2=notequals&o7=notsubstring&f8=short_desc&f11=CP&query_based_on=DOM%20Core%20defect%20pendingNIs%20%28w%2Fo%20severity%29&f5=short_desc&known_name=DOM%20Core%20defect%20pendingNIs%20%28w%2Fo%20severity%29&email2=intermittent-bug-filer%40mozilla.bugs&chfieldfrom=2016-06-01&bug_severity=--&f2=bug_type&f6=assigned_to&o6=equals&o2=equals&chfield=%5BBug%20creation%5D&o5=notsubstring&f10=OP&v6=nobody%40mozilla.org&list_id=15354385&o3=notregexp&columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cshort_desc%2Cchangeddate%2Cstatus_whiteboard%2Cbug_severity%2Cpriority%2Cflagtypes.name&chfieldto=Now&email1=wptsync%40mozilla.bugs&classification=Components&resolution=---&f3=keywords&emailtype1=notequals DOM Core needinfo? (all types)]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20Fission%20defect%20pendingNIs&sharer_id=434964&list_id=14982428 DOM Fission needinfo? (needs update per the new triage practice)]
*[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? (needs update per the new triage practice) ]

==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:
*[https://bugzilla.mozilla.org/buglist.cgi?f5=CP&emailtype1=notequals&j2=OR&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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&chfield=%5BBug%20creation%5D&o4=equals&emailtype2=notequals&email1=intermittent-bug-filer%40mozilla.bugs&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&chfieldfrom=2020-04-20&f4=component&resolution=---&emailreporter1=1&known_name=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&query_based_on=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&v3=S1&query_format=advanced&list_id=15354367&f1=flagtypes.name&f2=OP&f3=bug_severity&product=Core&email2=wptsync%40mozilla.bugs&emailreporter2=1&o3=equals&o1=notsubstring&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 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 (needs update per the new triage practice)]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20WorkerAndStorage-P1&sharer_id=434964&list_id=14982479 DOM Worker&Storage P1s (needs update per the new triage practice)]

==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:
*[https://bugzilla.mozilla.org/buglist.cgi?o1=notsubstring&f3=bug_severity&f1=flagtypes.name&o3=equals&emailreporter1=1&chfield=%5BBug%20creation%5D&f5=CP&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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%20S1&list_id=15361214&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&email1=intermittent-bug-filer%40mozilla.bugs&query_format=advanced&j2=OR&chfieldfrom=2020-04-20&v3=S1&emailtype2=notequals&emailtype1=notequals&resolution=---&product=Core&query_based_on=DOM%20Core%20S1&emailreporter2=1&email2=wptsync%40mozilla.bugs&o4=equals&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&f4=component&f2=OP DOM Core S1s]

S2 bugs:
*[https://bugzilla.mozilla.org/buglist.cgi?f4=component&chfieldfrom=2020-04-20&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&email1=intermittent-bug-filer%40mozilla.bugs&emailtype2=notequals&o4=equals&chfield=%5BBug%20creation%5D&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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&j2=OR&emailtype1=notequals&f5=CP&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&o1=notsubstring&o3=equals&emailreporter2=1&email2=wptsync%40mozilla.bugs&product=Core&f3=bug_severity&f1=flagtypes.name&f2=OP&list_id=15361211&query_format=advanced&v3=S2&query_based_on=DOM%20Core%20S1&known_name=DOM%20Core%20S1&emailreporter1=1&resolution=--- DOM Core S2s]

P1 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?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:
*[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=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:
*[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?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]

Other useful ones:
*'''[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.

==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?

Old bugs that need re-prioritization or re-validation
*[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=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]

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

DOM/Triage

2021-10-05T13:06:02Z

Hsinyi: /* New bugs of "defect" type - do this daily */ DOM Core updates

= 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://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 that need actions
*[https://bugzilla.mozilla.org/buglist.cgi?emailtype2=notequals&v3=[no-nag]&resolution=---&o1=notsubstring&f3=status_whiteboard&query_format=advanced&chfield=[Bug%20creation]&chfieldfrom=2020-04-20&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&emailreporter2=1&keywords_type=nowords&known_name=DOM%20Core%20new%20bugs%20no%20pending%20NI%20(w%2Fo%20severity)&v1=needinfo%3F&o3=notsubstring&f1=flagtypes.name&o5=greaterthan&keywords=intermittent-failure&emailtype1=notequals&f4=keywords&v4=meta&o2=anyexact&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&component=about%3Amemory&component=DOM%3A%20Bindings%20(WebIDL)&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=XML&component=XPConnect&component=XSLT&o4=nowords&v2=--%2Cn%2Fa&f2=bug_severity&email1=intermittent-bug-filer%40mozilla.bugs&v5=-1y&product=Core&product=Toolkit&email2=wptsync%40mozilla.bugs&query_based_on=DOM%20Core%20new%20bugs%20no%20pending%20NI%20(w%2Fo%20severity)&bug_type=defect&f5=creation_ts&emailreporter1=1&list_id=15858328 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 (needs update per the new "Severity triage" practice)]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20WorkerAndStorage%20-%20new%20Defect%20bugs&sharer_id=434964&list_id=14982384 DOM Workers & Storage(needs update per the new "Severity triage" practice)]
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 fix''able'' 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?
*[https://bugzilla.mozilla.org/buglist.cgi?product=Core&f4=cf_tracking_e10s&query_format=advanced&f1=flagtypes.name&v4=%20&v1=needinfo&o4=notequals&emailreporter2=1&o1=substring&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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&emailreporter1=1&o9=notsubstring&o8=notregexp&f7=status_whiteboard&f9=keywords&emailtype2=notequals&o7=notsubstring&f8=short_desc&f11=CP&query_based_on=DOM%20Core%20defect%20pendingNIs%20%28w%2Fo%20severity%29&f5=short_desc&known_name=DOM%20Core%20defect%20pendingNIs%20%28w%2Fo%20severity%29&email2=intermittent-bug-filer%40mozilla.bugs&chfieldfrom=2016-06-01&bug_severity=--&f2=bug_type&f6=assigned_to&o6=equals&o2=equals&chfield=%5BBug%20creation%5D&o5=notsubstring&f10=OP&v6=nobody%40mozilla.org&list_id=15354385&o3=notregexp&columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cshort_desc%2Cchangeddate%2Cstatus_whiteboard%2Cbug_severity%2Cpriority%2Cflagtypes.name&chfieldto=Now&email1=wptsync%40mozilla.bugs&classification=Components&resolution=---&f3=keywords&emailtype1=notequals DOM Core needinfo? (all types)]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20Fission%20defect%20pendingNIs&sharer_id=434964&list_id=14982428 DOM Fission needinfo? (needs update per the new triage practice)]
*[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? (needs update per the new triage practice) ]

==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:
*[https://bugzilla.mozilla.org/buglist.cgi?f5=CP&emailtype1=notequals&j2=OR&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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&chfield=%5BBug%20creation%5D&o4=equals&emailtype2=notequals&email1=intermittent-bug-filer%40mozilla.bugs&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&chfieldfrom=2020-04-20&f4=component&resolution=---&emailreporter1=1&known_name=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&query_based_on=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&v3=S1&query_format=advanced&list_id=15354367&f1=flagtypes.name&f2=OP&f3=bug_severity&product=Core&email2=wptsync%40mozilla.bugs&emailreporter2=1&o3=equals&o1=notsubstring&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 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 (needs update per the new triage practice)]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20WorkerAndStorage-P1&sharer_id=434964&list_id=14982479 DOM Worker&Storage P1s (needs update per the new triage practice)]

==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:
*[https://bugzilla.mozilla.org/buglist.cgi?o1=notsubstring&f3=bug_severity&f1=flagtypes.name&o3=equals&emailreporter1=1&chfield=%5BBug%20creation%5D&f5=CP&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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%20S1&list_id=15361214&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&email1=intermittent-bug-filer%40mozilla.bugs&query_format=advanced&j2=OR&chfieldfrom=2020-04-20&v3=S1&emailtype2=notequals&emailtype1=notequals&resolution=---&product=Core&query_based_on=DOM%20Core%20S1&emailreporter2=1&email2=wptsync%40mozilla.bugs&o4=equals&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&f4=component&f2=OP DOM Core S1s]

S2 bugs:
*[https://bugzilla.mozilla.org/buglist.cgi?f4=component&chfieldfrom=2020-04-20&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&email1=intermittent-bug-filer%40mozilla.bugs&emailtype2=notequals&o4=equals&chfield=%5BBug%20creation%5D&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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&j2=OR&emailtype1=notequals&f5=CP&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&o1=notsubstring&o3=equals&emailreporter2=1&email2=wptsync%40mozilla.bugs&product=Core&f3=bug_severity&f1=flagtypes.name&f2=OP&list_id=15361211&query_format=advanced&v3=S2&query_based_on=DOM%20Core%20S1&known_name=DOM%20Core%20S1&emailreporter1=1&resolution=--- DOM Core S2s]

P1 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?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:
*[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=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:
*[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?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]

Other useful ones:
*'''[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.

==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?

Old bugs that need re-prioritization or re-validation
*[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=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]

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

DOM/Triage

2021-10-04T03:53:07Z

Hsinyi: /* New bugs of "defect" or "task" type - do this daily */ missing [

= 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://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" or "task" type - do this daily==
New bugs of "defect" or"task" type that need actions
*[https://bugzilla.mozilla.org/buglist.cgi?v4=untriaged&chfieldfrom=2020-04-20&o3=equals&o1=notsubstring&email1=intermittent-bug-filer%40mozilla.bugs&product=Core&product=Toolkit&f4=component&list_id=15856358&j2=OR&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&resolution=---&v3=--&v1=needinfo&emailtype2=notequals&emailreporter1=1&email2=wptsync%40mozilla.bugs&query_based_on=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&f2=OP&o4=equals&emailreporter2=1&known_name=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&bug_type=defect&emailtype1=notequals&f3=bug_severity&f5=CP&query_format=advanced&chfield=%5BBug%20creation%5D&f1=flagtypes.name&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=XML&component=XPConnect&component=XSLT&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software 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 (needs update per the new "Severity triage" practice)]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20WorkerAndStorage%20-%20new%20Defect%20bugs&sharer_id=434964&list_id=14982384 DOM Workers & Storage(needs update per the new "Severity triage" practice)]
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 fix''able'' 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?
*[https://bugzilla.mozilla.org/buglist.cgi?product=Core&f4=cf_tracking_e10s&query_format=advanced&f1=flagtypes.name&v4=%20&v1=needinfo&o4=notequals&emailreporter2=1&o1=substring&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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&emailreporter1=1&o9=notsubstring&o8=notregexp&f7=status_whiteboard&f9=keywords&emailtype2=notequals&o7=notsubstring&f8=short_desc&f11=CP&query_based_on=DOM%20Core%20defect%20pendingNIs%20%28w%2Fo%20severity%29&f5=short_desc&known_name=DOM%20Core%20defect%20pendingNIs%20%28w%2Fo%20severity%29&email2=intermittent-bug-filer%40mozilla.bugs&chfieldfrom=2016-06-01&bug_severity=--&f2=bug_type&f6=assigned_to&o6=equals&o2=equals&chfield=%5BBug%20creation%5D&o5=notsubstring&f10=OP&v6=nobody%40mozilla.org&list_id=15354385&o3=notregexp&columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cshort_desc%2Cchangeddate%2Cstatus_whiteboard%2Cbug_severity%2Cpriority%2Cflagtypes.name&chfieldto=Now&email1=wptsync%40mozilla.bugs&classification=Components&resolution=---&f3=keywords&emailtype1=notequals DOM Core needinfo? (all types)]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20Fission%20defect%20pendingNIs&sharer_id=434964&list_id=14982428 DOM Fission needinfo? (needs update per the new triage practice)]
*[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? (needs update per the new triage practice) ]

==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:
*[https://bugzilla.mozilla.org/buglist.cgi?f5=CP&emailtype1=notequals&j2=OR&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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&chfield=%5BBug%20creation%5D&o4=equals&emailtype2=notequals&email1=intermittent-bug-filer%40mozilla.bugs&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&chfieldfrom=2020-04-20&f4=component&resolution=---&emailreporter1=1&known_name=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&query_based_on=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&v3=S1&query_format=advanced&list_id=15354367&f1=flagtypes.name&f2=OP&f3=bug_severity&product=Core&email2=wptsync%40mozilla.bugs&emailreporter2=1&o3=equals&o1=notsubstring&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 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 (needs update per the new triage practice)]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20WorkerAndStorage-P1&sharer_id=434964&list_id=14982479 DOM Worker&Storage P1s (needs update per the new triage practice)]

==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:
*[https://bugzilla.mozilla.org/buglist.cgi?o1=notsubstring&f3=bug_severity&f1=flagtypes.name&o3=equals&emailreporter1=1&chfield=%5BBug%20creation%5D&f5=CP&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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%20S1&list_id=15361214&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&email1=intermittent-bug-filer%40mozilla.bugs&query_format=advanced&j2=OR&chfieldfrom=2020-04-20&v3=S1&emailtype2=notequals&emailtype1=notequals&resolution=---&product=Core&query_based_on=DOM%20Core%20S1&emailreporter2=1&email2=wptsync%40mozilla.bugs&o4=equals&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&f4=component&f2=OP DOM Core S1s]

S2 bugs:
*[https://bugzilla.mozilla.org/buglist.cgi?f4=component&chfieldfrom=2020-04-20&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&email1=intermittent-bug-filer%40mozilla.bugs&emailtype2=notequals&o4=equals&chfield=%5BBug%20creation%5D&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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&j2=OR&emailtype1=notequals&f5=CP&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&o1=notsubstring&o3=equals&emailreporter2=1&email2=wptsync%40mozilla.bugs&product=Core&f3=bug_severity&f1=flagtypes.name&f2=OP&list_id=15361211&query_format=advanced&v3=S2&query_based_on=DOM%20Core%20S1&known_name=DOM%20Core%20S1&emailreporter1=1&resolution=--- DOM Core S2s]

P1 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?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:
*[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=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:
*[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?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]

Other useful ones:
*'''[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.

==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?

Old bugs that need re-prioritization or re-validation
*[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=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]

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

DOM/Triage

2021-10-04T03:52:26Z

Hsinyi: /* New bugs of "defect" or "task" type - do this daily */ DOM Core updates

= 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://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" or "task" type - do this daily==
New bugs of "defect" or"task" type that need actions
*https://bugzilla.mozilla.org/buglist.cgi?v4=untriaged&chfieldfrom=2020-04-20&o3=equals&o1=notsubstring&email1=intermittent-bug-filer%40mozilla.bugs&product=Core&product=Toolkit&f4=component&list_id=15856358&j2=OR&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&resolution=---&v3=--&v1=needinfo&emailtype2=notequals&emailreporter1=1&email2=wptsync%40mozilla.bugs&query_based_on=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&f2=OP&o4=equals&emailreporter2=1&known_name=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&bug_type=defect&emailtype1=notequals&f3=bug_severity&f5=CP&query_format=advanced&chfield=%5BBug%20creation%5D&f1=flagtypes.name&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=XML&component=XPConnect&component=XSLT&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software 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 (needs update per the new "Severity triage" practice)]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20WorkerAndStorage%20-%20new%20Defect%20bugs&sharer_id=434964&list_id=14982384 DOM Workers & Storage(needs update per the new "Severity triage" practice)]
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 fix''able'' 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?
*[https://bugzilla.mozilla.org/buglist.cgi?product=Core&f4=cf_tracking_e10s&query_format=advanced&f1=flagtypes.name&v4=%20&v1=needinfo&o4=notequals&emailreporter2=1&o1=substring&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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&emailreporter1=1&o9=notsubstring&o8=notregexp&f7=status_whiteboard&f9=keywords&emailtype2=notequals&o7=notsubstring&f8=short_desc&f11=CP&query_based_on=DOM%20Core%20defect%20pendingNIs%20%28w%2Fo%20severity%29&f5=short_desc&known_name=DOM%20Core%20defect%20pendingNIs%20%28w%2Fo%20severity%29&email2=intermittent-bug-filer%40mozilla.bugs&chfieldfrom=2016-06-01&bug_severity=--&f2=bug_type&f6=assigned_to&o6=equals&o2=equals&chfield=%5BBug%20creation%5D&o5=notsubstring&f10=OP&v6=nobody%40mozilla.org&list_id=15354385&o3=notregexp&columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cshort_desc%2Cchangeddate%2Cstatus_whiteboard%2Cbug_severity%2Cpriority%2Cflagtypes.name&chfieldto=Now&email1=wptsync%40mozilla.bugs&classification=Components&resolution=---&f3=keywords&emailtype1=notequals DOM Core needinfo? (all types)]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20Fission%20defect%20pendingNIs&sharer_id=434964&list_id=14982428 DOM Fission needinfo? (needs update per the new triage practice)]
*[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? (needs update per the new triage practice) ]

==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:
*[https://bugzilla.mozilla.org/buglist.cgi?f5=CP&emailtype1=notequals&j2=OR&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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&chfield=%5BBug%20creation%5D&o4=equals&emailtype2=notequals&email1=intermittent-bug-filer%40mozilla.bugs&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&chfieldfrom=2020-04-20&f4=component&resolution=---&emailreporter1=1&known_name=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&query_based_on=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&v3=S1&query_format=advanced&list_id=15354367&f1=flagtypes.name&f2=OP&f3=bug_severity&product=Core&email2=wptsync%40mozilla.bugs&emailreporter2=1&o3=equals&o1=notsubstring&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 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 (needs update per the new triage practice)]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20WorkerAndStorage-P1&sharer_id=434964&list_id=14982479 DOM Worker&Storage P1s (needs update per the new triage practice)]

==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:
*[https://bugzilla.mozilla.org/buglist.cgi?o1=notsubstring&f3=bug_severity&f1=flagtypes.name&o3=equals&emailreporter1=1&chfield=%5BBug%20creation%5D&f5=CP&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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%20S1&list_id=15361214&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&email1=intermittent-bug-filer%40mozilla.bugs&query_format=advanced&j2=OR&chfieldfrom=2020-04-20&v3=S1&emailtype2=notequals&emailtype1=notequals&resolution=---&product=Core&query_based_on=DOM%20Core%20S1&emailreporter2=1&email2=wptsync%40mozilla.bugs&o4=equals&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&f4=component&f2=OP DOM Core S1s]

S2 bugs:
*[https://bugzilla.mozilla.org/buglist.cgi?f4=component&chfieldfrom=2020-04-20&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&email1=intermittent-bug-filer%40mozilla.bugs&emailtype2=notequals&o4=equals&chfield=%5BBug%20creation%5D&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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&j2=OR&emailtype1=notequals&f5=CP&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&o1=notsubstring&o3=equals&emailreporter2=1&email2=wptsync%40mozilla.bugs&product=Core&f3=bug_severity&f1=flagtypes.name&f2=OP&list_id=15361211&query_format=advanced&v3=S2&query_based_on=DOM%20Core%20S1&known_name=DOM%20Core%20S1&emailreporter1=1&resolution=--- DOM Core S2s]

P1 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?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:
*[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=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:
*[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?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]

Other useful ones:
*'''[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.

==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?

Old bugs that need re-prioritization or re-validation
*[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=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]

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

DOM/Triage

2021-09-13T09:05:58Z

Hsinyi: /* New bugs of "defect" or "task" type - do this daily */ DOM Core defect inquiry update

= 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://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" or "task" type - do this daily==
New bugs of "defect" or"task" type that need actions
*[https://bugzilla.mozilla.org/buglist.cgi?emailreporter2=1&bug_type=defect&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&resolution=---&product=Core&emailreporter1=1&list_id=15834882&email2=wptsync%40mozilla.bugs&f4=component&v4=untriaged&query_based_on=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&f2=OP&emailtype2=notequals&emailtype1=notequals&o3=equals&o1=notsubstring&query_format=advanced&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&f3=bug_severity&j2=OR&v3=--&f5=CP&chfield=%5BBug%20creation%5D&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%20Selection&component=DOM%3A%20Serializers&component=DOM%3A%20UI%20Events%20%26%20Focus%20Handling&f1=flagtypes.name&v1=needinfo&chfieldfrom=2020-04-20&o4=equals&email1=intermittent-bug-filer%40mozilla.bugs&known_name=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29 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 (needs update per the new "Severity triage" practice)]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20WorkerAndStorage%20-%20new%20Defect%20bugs&sharer_id=434964&list_id=14982384 DOM Workers & Storage(needs update per the new "Severity triage" practice)]
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 fix''able'' 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?
*[https://bugzilla.mozilla.org/buglist.cgi?product=Core&f4=cf_tracking_e10s&query_format=advanced&f1=flagtypes.name&v4=%20&v1=needinfo&o4=notequals&emailreporter2=1&o1=substring&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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&emailreporter1=1&o9=notsubstring&o8=notregexp&f7=status_whiteboard&f9=keywords&emailtype2=notequals&o7=notsubstring&f8=short_desc&f11=CP&query_based_on=DOM%20Core%20defect%20pendingNIs%20%28w%2Fo%20severity%29&f5=short_desc&known_name=DOM%20Core%20defect%20pendingNIs%20%28w%2Fo%20severity%29&email2=intermittent-bug-filer%40mozilla.bugs&chfieldfrom=2016-06-01&bug_severity=--&f2=bug_type&f6=assigned_to&o6=equals&o2=equals&chfield=%5BBug%20creation%5D&o5=notsubstring&f10=OP&v6=nobody%40mozilla.org&list_id=15354385&o3=notregexp&columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cshort_desc%2Cchangeddate%2Cstatus_whiteboard%2Cbug_severity%2Cpriority%2Cflagtypes.name&chfieldto=Now&email1=wptsync%40mozilla.bugs&classification=Components&resolution=---&f3=keywords&emailtype1=notequals DOM Core needinfo? (all types)]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20Fission%20defect%20pendingNIs&sharer_id=434964&list_id=14982428 DOM Fission needinfo? (needs update per the new triage practice)]
*[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? (needs update per the new triage practice) ]

==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:
*[https://bugzilla.mozilla.org/buglist.cgi?f5=CP&emailtype1=notequals&j2=OR&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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&chfield=%5BBug%20creation%5D&o4=equals&emailtype2=notequals&email1=intermittent-bug-filer%40mozilla.bugs&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&chfieldfrom=2020-04-20&f4=component&resolution=---&emailreporter1=1&known_name=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&query_based_on=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&v3=S1&query_format=advanced&list_id=15354367&f1=flagtypes.name&f2=OP&f3=bug_severity&product=Core&email2=wptsync%40mozilla.bugs&emailreporter2=1&o3=equals&o1=notsubstring&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 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 (needs update per the new triage practice)]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20WorkerAndStorage-P1&sharer_id=434964&list_id=14982479 DOM Worker&Storage P1s (needs update per the new triage practice)]

==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:
*[https://bugzilla.mozilla.org/buglist.cgi?o1=notsubstring&f3=bug_severity&f1=flagtypes.name&o3=equals&emailreporter1=1&chfield=%5BBug%20creation%5D&f5=CP&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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%20S1&list_id=15361214&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&email1=intermittent-bug-filer%40mozilla.bugs&query_format=advanced&j2=OR&chfieldfrom=2020-04-20&v3=S1&emailtype2=notequals&emailtype1=notequals&resolution=---&product=Core&query_based_on=DOM%20Core%20S1&emailreporter2=1&email2=wptsync%40mozilla.bugs&o4=equals&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&f4=component&f2=OP DOM Core S1s]

S2 bugs:
*[https://bugzilla.mozilla.org/buglist.cgi?f4=component&chfieldfrom=2020-04-20&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&email1=intermittent-bug-filer%40mozilla.bugs&emailtype2=notequals&o4=equals&chfield=%5BBug%20creation%5D&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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&j2=OR&emailtype1=notequals&f5=CP&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&o1=notsubstring&o3=equals&emailreporter2=1&email2=wptsync%40mozilla.bugs&product=Core&f3=bug_severity&f1=flagtypes.name&f2=OP&list_id=15361211&query_format=advanced&v3=S2&query_based_on=DOM%20Core%20S1&known_name=DOM%20Core%20S1&emailreporter1=1&resolution=--- DOM Core S2s]

P1 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?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:
*[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=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:
*[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?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]

Other useful ones:
*'''[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.

==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?

Old bugs that need re-prioritization or re-validation
*[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=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]

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

DOM/Triage

2021-09-08T09:04:31Z

Hsinyi: /* Overview */ new bugs: add "DOM: Copy & Paste and Drag & Drop" into the triage list

= 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://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" or "task" type - do this daily==
New bugs of "defect" or"task" type that need actions
*[https://bugzilla.mozilla.org/buglist.cgi?f1=flagtypes.name&email1=intermittent-bug-filer%40mozilla.bugs&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&f5=CP&known_name=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&chfield=%5BBug%20creation%5D&o1=notsubstring&v1=needinfo&emailtype1=notequals&product=Core&query_based_on=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&emailreporter1=1&list_id=15829822&query_format=advanced&f3=bug_severity&f4=component&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&f2=OP&emailtype2=notequals&j2=OR&emailreporter2=1&v4=untriaged&o3=equals&chfieldfrom=2020-04-20&o4=equals&v3=--&resolution=---&email2=wptsync%40mozilla.bugs&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%20Selection&component=DOM%3A%20Serializers&component=DOM%3A%20UI%20Events%20%26%20Focus%20Handling DOM Core (all types)]
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 (i.e. defects, tasks and enhancements).

*[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)]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20WorkerAndStorage%20-%20new%20Defect%20bugs&sharer_id=434964&list_id=14982384 DOM Workers & Storage(needs update per the new "Severity triage" practice)]
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 fix''able'' 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?
*[https://bugzilla.mozilla.org/buglist.cgi?product=Core&f4=cf_tracking_e10s&query_format=advanced&f1=flagtypes.name&v4=%20&v1=needinfo&o4=notequals&emailreporter2=1&o1=substring&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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&emailreporter1=1&o9=notsubstring&o8=notregexp&f7=status_whiteboard&f9=keywords&emailtype2=notequals&o7=notsubstring&f8=short_desc&f11=CP&query_based_on=DOM%20Core%20defect%20pendingNIs%20%28w%2Fo%20severity%29&f5=short_desc&known_name=DOM%20Core%20defect%20pendingNIs%20%28w%2Fo%20severity%29&email2=intermittent-bug-filer%40mozilla.bugs&chfieldfrom=2016-06-01&bug_severity=--&f2=bug_type&f6=assigned_to&o6=equals&o2=equals&chfield=%5BBug%20creation%5D&o5=notsubstring&f10=OP&v6=nobody%40mozilla.org&list_id=15354385&o3=notregexp&columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cshort_desc%2Cchangeddate%2Cstatus_whiteboard%2Cbug_severity%2Cpriority%2Cflagtypes.name&chfieldto=Now&email1=wptsync%40mozilla.bugs&classification=Components&resolution=---&f3=keywords&emailtype1=notequals DOM Core needinfo? (all types)]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20Fission%20defect%20pendingNIs&sharer_id=434964&list_id=14982428 DOM Fission needinfo? (needs update per the new triage practice)]
*[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? (needs update per the new triage practice) ]

==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:
*[https://bugzilla.mozilla.org/buglist.cgi?f5=CP&emailtype1=notequals&j2=OR&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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&chfield=%5BBug%20creation%5D&o4=equals&emailtype2=notequals&email1=intermittent-bug-filer%40mozilla.bugs&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&chfieldfrom=2020-04-20&f4=component&resolution=---&emailreporter1=1&known_name=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&query_based_on=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&v3=S1&query_format=advanced&list_id=15354367&f1=flagtypes.name&f2=OP&f3=bug_severity&product=Core&email2=wptsync%40mozilla.bugs&emailreporter2=1&o3=equals&o1=notsubstring&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 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 (needs update per the new triage practice)]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20WorkerAndStorage-P1&sharer_id=434964&list_id=14982479 DOM Worker&Storage P1s (needs update per the new triage practice)]

==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:
*[https://bugzilla.mozilla.org/buglist.cgi?o1=notsubstring&f3=bug_severity&f1=flagtypes.name&o3=equals&emailreporter1=1&chfield=%5BBug%20creation%5D&f5=CP&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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%20S1&list_id=15361214&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&email1=intermittent-bug-filer%40mozilla.bugs&query_format=advanced&j2=OR&chfieldfrom=2020-04-20&v3=S1&emailtype2=notequals&emailtype1=notequals&resolution=---&product=Core&query_based_on=DOM%20Core%20S1&emailreporter2=1&email2=wptsync%40mozilla.bugs&o4=equals&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&f4=component&f2=OP DOM Core S1s]

S2 bugs:
*[https://bugzilla.mozilla.org/buglist.cgi?f4=component&chfieldfrom=2020-04-20&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&email1=intermittent-bug-filer%40mozilla.bugs&emailtype2=notequals&o4=equals&chfield=%5BBug%20creation%5D&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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&j2=OR&emailtype1=notequals&f5=CP&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&o1=notsubstring&o3=equals&emailreporter2=1&email2=wptsync%40mozilla.bugs&product=Core&f3=bug_severity&f1=flagtypes.name&f2=OP&list_id=15361211&query_format=advanced&v3=S2&query_based_on=DOM%20Core%20S1&known_name=DOM%20Core%20S1&emailreporter1=1&resolution=--- DOM Core S2s]

P1 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?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:
*[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=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:
*[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?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]

Other useful ones:
*'''[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.

==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?

Old bugs that need re-prioritization or re-validation
*[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=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]

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

User:Hsinyi/Gecko engineering

2020-08-04T10:02:13Z

Hsinyi: disclaimer

<big><Disclaimer: This document is a draft and a collection of my personal thoughts of gecko engineering practices. Discussion and comments welcome!></big>

== What should I work on? ==
We want to deliver a product with high qualities to our users, we want to bring new values to our users. This won't happen without collaboration with various teams and our community. Therefore, when we are thinking about what we should work on with which priority, we consider to unblock others and help others as well. Here is a list (in descending order of priority) to show others how our work is being prioritized, not necessarily a how to strictly prioritize the work.

*Catastrophic bugs
*: Bugs that block development/testing, may impact more than 25% of users, causes data loss, potential chemspill, and no workaround available. Examples include but not limit to:
*#[[Security_Severity_Ratings/Client|sec-critical security bugs]]
*#Sev-blocker or release-tracking+ bugs
*#Permanent test failures that block branch merging
*#New regressions: Not every regression is a catastrophic issue, but we should look into quickly to investigate the impact and solutions timely.

*Review and needinfo requests to unblock others
*: Browser is such a complex system. No one knows every single piece or no one can figure out every single piece shortly. Only when we have collaborative team work, are we able to deliver a satisfying product or bring new values to our users timely. (Yes, '''TIMELY''' again!) It takes time and effort to build a product with high qualities, no doubt. I am not saying we should sacrifice the quality. What I am trying to say here is we have to admit the time-to-market impact or how the life cycle of a bug impacts our user, keep that in mind and guide our work. So with that in mind, unblocking others is a key for us to succeed.
*: To do a proper and thorough and high-quality review may take time. And we should take what it needs to ensure our quality. Communication is nevertheless a key here. If it takes longer to review/respond, communicate. If you are not sure about the priority, communicate. Oh, and, if it's a simple enough review or question (even the priority isn't high), just do it and help things done.

*Serious bugs
*: Bugs that cause major Functionality/product severely impaired. If there's a satisfactory workaround, for example, flipping a preference and explaining to our users about this so they can live with it, we should do it. sec-high security bugs are one example for this category, as well as top crashes. Again, keep an eye on regressions.

*Special programs e.g. WFH bugs, q-flow bugs
*: To react upon the real world situation, priorities change for a given period of time. COVID-19 is an example of how people's working, social and daily lives are largely impacted and changed in a certain period. Some old issues may become much more sever due to this.

*Important partner and webcompat bug fixes
*:

*Bug fixes
*:

*New features
*:Again, though new features are listed at the bottom of the list, it doesn’t mean that new features are always strictly with the lowest priority compared with other engineering tasks. Nevertheless, there are more important things than new feature implementations we need to work on as well.

Add some notes for tests and documents.

== Bug triage ==
Why are we doing triage?
:Ensuring we don’t miss important bugs and timely actions are taken

What counts as being triaged?
:According to [https://firefox-source-docs.mozilla.org/bug-mgmt/policies/triage-bugzilla.html?highlight=triage%20severity|Mozilla's latest triage practice], '''severity''' field is set.

What are the actions to take?
:Paying particular attention to regressions
:Paying particular attention for bugs impacting top websites
:When needinfo someone, be clear that help is needed to try to advance it
:Responding to needinfo requests and not collecting ASSIGNED bugs
:Also, rotation duty of Core: General triage

References:

[https://wiki.mozilla.org/Platform/Layout/Triage| Layout team triage]

[https://wiki.mozilla.org/Platform/DOM_Bug_Triage| DOM team triage]

[https://apenwarr.ca/log/20171213| Backlog management presentation]

== Code review ==
=== What is the purpose of code review ===
''“Code review is our basic mechanism for validating the design and implementation of patches. It also helps us maintain a level of consistency in design and implementation practices across the many hackers and among the various modules of Mozilla.”'' [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Code_Review_FAQ| 1]

Additionally, knowledge sharing is another major advantage.

===What does the code review process look like===
A critical thing to remember is that coding to some extent is a social process. The code review process may start '''before''' an actual patch and actual review request are submitted. '''Communication''' is key. It is very important and helpful that before you start implementing you discuss your implementation plan with the module peers, especially when you are working on something new to you or you are working on a new feature. Because documentation can be lacking or out of date, talking to the other members may save you literally weeks of needless time. It’s also because walking reviewers through your thoughts can help save their time and allow them to provide early feedback, too.

With this thought in mind, the code review process actually contains the [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/How_to_Submit_a_Patch steps] in the red rectangular.

[[File:(Draft) Gecko Platform Code Review Best Practice.png|thumb]]

====Initial communication between requesters & reviewers ====
*Mutual understanding of the priority and the expected timeline
*:As a requester, set a clear expectation. For a new feature or big patch, it’s especially important to plan in advance.
*:As a reviewer, set a clear expectation about your availability, too.

*Check reviewer’s availability before/when submitting a patch to avoid needless waiting time
*:Reviewers should ensure that their phabricator calendars are up-to-date so that requesters will receive warnings when requests are submitted to a reviewer who is not available.
*:Reviewers should ensure their bugzilla user name displays the Out-of-office information, if they are away for more than 2 days.
*:Reviewers should consider to block accepting bugzilla needinfo/review requests, if they are away for more than 2 days.

*Architecture design documents help! Examples:
*:[https://docs.google.com/document/d/1Tk-DY1aLTNtfRqrngAmLo8Eivqo9zohsCgAyNUBfVFQ/edit Lazy image loading architecture review]
*:[https://docs.google.com/document/d/1fOlyHR2R3qFi390fj_j33-LaPd36jzdbKHOF6w7SdNk/edit OOP-iframe event delivery in Fission]

====Creating a patch & testing====
===== Commit messages =====
''“Changesets should have commit messages. The commit message should describe not just the "what" of the change but also the "why". This is especially true in cases when the "what" is obvious from the diff anyway; for larger changes it makes sense to have a summary of the "what" in the commit message.''

''As a specific example, if your diff is a one-line change that changes a method call argument from "true" to "false", having a commit message that says "change argument to mymethod from true to false" is not very helpful at all. A good commit message in this situation will at least mention the meaning for the argument. If that does not make it clear why the change is being made, the commit message should explain the "why".''[https://groups.google.com/g/mozilla.dev.platform/c/qERnoJniCds/m/YWmmKqe4EAAJ 2]

*Describe WHY in addition to WHAT
*Describe the change but not the symptom. Bad example: [Bug XYZ: Crash at Foo::Bar" ]
*For WPTs which will be upstreamed, consider how the commit message will read outside the m-c repository, and at least mention which features the tests are intending to cover.
**For example, a commit message like "Bug 1234 - Part 2: Tests" is not totally terrible in the context of Mozilla Central (though can be better) but "Part 2: Tests" is utterly meaningless upstream.
*Reviewers should feel comfortable to reject a review request if the commit message isn’t well-written or doesn’t provide useful information.
*[[https://groups.google.com/g/mozilla.dev.platform/c/qERnoJniCds/m/6DLNfrGhBQAJ Open question]] People have various preferences on the length of commit messages … We need more discussions and a much better style guide, explaining what makes a good commit message and what makes a good and descriptive bug, with a number of (good and bad) examples.

===== Patch scope & size =====
It’s arguable if the size of a patch matters much and optimizing for “small changes v.s. big diffs” is hard. But a good principle to keep is: '''seek to understand''' (understand the code, implement the change), and '''seek to be understood''' (present the change in an understandable form). Normally, smaller is better.

An example for arranging patches in sequence to [https://phabricator.services.mozilla.com/D63324#1956232 help reviewers]: https://bugzilla.mozilla.org/show_bug.cgi?id=1615581

Ensure to always stick with *the* real problem you want to fix. Be conscious about '''not''' adding unrelated fixes into that patch, even if they are super tiny.

=====Tests=====
*'''ALWAYS''' pursue this target - land code changes along with automated tests. There are exceptions or cases where testing isn’t possible using current testing frameworks. However, always ensure that you’ve thought about automated tests and you have a strong reason why no automated tests are needed or why landing without automated tests is acceptable.
**There are cases when testing isn't possible using current testing frameworks: some parts of DnD, clipboard, printing etc.
**Improving performance can often rely on existing performance tests. Or the patch might improve some very micro level issue, so adding a performance test for that might not be worth.
**Scheduling changes should get tested by overall "do tests still pass" and performance tests (but we do need better tests for responsiveness etc.)
**Scheduling changes for things like CC and GC are tested basically by looking at telemetry data.
*'''Web platform tests (WPT)''' have helped a lot for us and for cross-browser behaviors. WPT should always be the default testing framework, where possible.
*'''Write comments'''! Comments in the tests are particularly useful. It forces the patch author to think which all cases are tested and reviewers can also easily see that.
*Always, ensure that a patch is '''well-tested''' and '''self-reviewed''' before it’s submitted for review.

====Getting reviews and during reviews====
Remember, communication is key! Code reviews are more '''a discussion, not a dictation'''. Patch authors are encouraged to have different opinions than reviewers that not every review comment is being taken, as long as there's sensible discussion and reasoning about the opinions that it's better for the code quality and the users.

Respect each other’s time as yours. While we expect reviewers to get back to the patch authors within 2 days, it's also important that patch authors allocate time to address review comments in the same time frame. This helps the discussion momentum while the memory is still fresh. It may not be a good practice that an author submits a patch to review right before they take vacations without proper communication in advance, because reviewers may need explanation or elaboration from the author when they are conducting a proper review. It won’t be effective if the author is away.

====Checklist====
=====When requesting a code review=====
First thing to remember - You are responsible for the code you write. You are responsible for the issue fixing. You are responsible for the code base quality after your code is landed.

=====When doing a code review=====
*Check mozilla-standard-positions for new WebAPIs; if in doubt, file an issue to request Mozilla’s official position on that.
*Refer to [https://wiki.mozilla.org/ExposureGuidelines ExposureGuidelines] for web observable changes, including sending intent-to-* emails or creating new preferences.
*Be cautious about the follow-up suggestion. Whenever there is a "follow-up", it should be thought of work which is not going to happen ever - except perhaps in one case, when the follow-up blocks some meta bug, where fixing all the blockers are required. For example Fission meta bug has such blockers.
*Functionality
*Life cycle management
*Performance

== Release health and product quality ==
* Communication with release management (e.g. channel meeting)
**Release metrics tracking
*Regression Engineering Owner (REO)
*Security bulletin report
*Test coverage - are we doing good enough to ensure a test is added along with a fix?
**72% of the bugs with updated RCA had no tests added along with the fix according to the RCA phase I results
*Paying attentions to these slack channels as many Mozillians often report Firefox problems there
#firefox
#web-platform
#webcompat
#moco
#planning
#triage-and-tracking

== Roadmap and status communication ==

User:Hsinyi/Gecko engineering

2020-08-03T14:42:59Z

Hsinyi: /* Release health and product quality */ adding contents

<big><Disclaimer: This document is a draft and a collection of my personal thoughts of gecko engineering practices.></big>

== What should I work on? ==
We want to deliver a product with high qualities to our users, we want to bring new values to our users. This won't happen without collaboration with various teams and our community. Therefore, when we are thinking about what we should work on with which priority, we consider to unblock others and help others as well. Here is a list (in descending order of priority) to show others how our work is being prioritized, not necessarily a how to strictly prioritize the work.

*Catastrophic bugs
*: Bugs that block development/testing, may impact more than 25% of users, causes data loss, potential chemspill, and no workaround available. Examples include but not limit to:
*#[[Security_Severity_Ratings/Client|sec-critical security bugs]]
*#Sev-blocker or release-tracking+ bugs
*#Permanent test failures that block branch merging
*#New regressions: Not every regression is a catastrophic issue, but we should look into quickly to investigate the impact and solutions timely.

*Review and needinfo requests to unblock others
*: Browser is such a complex system. No one knows every single piece or no one can figure out every single piece shortly. Only when we have collaborative team work, are we able to deliver a satisfying product or bring new values to our users timely. (Yes, '''TIMELY''' again!) It takes time and effort to build a product with high qualities, no doubt. I am not saying we should sacrifice the quality. What I am trying to say here is we have to admit the time-to-market impact or how the life cycle of a bug impacts our user, keep that in mind and guide our work. So with that in mind, unblocking others is a key for us to succeed.
*: To do a proper and thorough and high-quality review may take time. And we should take what it needs to ensure our quality. Communication is nevertheless a key here. If it takes longer to review/respond, communicate. If you are not sure about the priority, communicate. Oh, and, if it's a simple enough review or question (even the priority isn't high), just do it and help things done.

*Serious bugs
*: Bugs that cause major Functionality/product severely impaired. If there's a satisfactory workaround, for example, flipping a preference and explaining to our users about this so they can live with it, we should do it. sec-high security bugs are one example for this category, as well as top crashes. Again, keep an eye on regressions.

*Special programs e.g. WFH bugs, q-flow bugs
*: To react upon the real world situation, priorities change for a given period of time. COVID-19 is an example of how people's working, social and daily lives are largely impacted and changed in a certain period. Some old issues may become much more sever due to this.

*Important partner and webcompat bug fixes
*:

*Bug fixes
*:

*New features
*:Again, though new features are listed at the bottom of the list, it doesn’t mean that new features are always strictly with the lowest priority compared with other engineering tasks. Nevertheless, there are more important things than new feature implementations we need to work on as well.

Add some notes for tests and documents.

== Bug triage ==
Why are we doing triage?
:Ensuring we don’t miss important bugs and timely actions are taken

What counts as being triaged?
:According to [https://firefox-source-docs.mozilla.org/bug-mgmt/policies/triage-bugzilla.html?highlight=triage%20severity|Mozilla's latest triage practice], '''severity''' field is set.

What are the actions to take?
:Paying particular attention to regressions
:Paying particular attention for bugs impacting top websites
:When needinfo someone, be clear that help is needed to try to advance it
:Responding to needinfo requests and not collecting ASSIGNED bugs
:Also, rotation duty of Core: General triage

References:

[https://wiki.mozilla.org/Platform/Layout/Triage| Layout team triage]

[https://wiki.mozilla.org/Platform/DOM_Bug_Triage| DOM team triage]

[https://apenwarr.ca/log/20171213| Backlog management presentation]

== Code review ==
=== What is the purpose of code review ===
''“Code review is our basic mechanism for validating the design and implementation of patches. It also helps us maintain a level of consistency in design and implementation practices across the many hackers and among the various modules of Mozilla.”'' [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Code_Review_FAQ| 1]

Additionally, knowledge sharing is another major advantage.

===What does the code review process look like===
A critical thing to remember is that coding to some extent is a social process. The code review process may start '''before''' an actual patch and actual review request are submitted. '''Communication''' is key. It is very important and helpful that before you start implementing you discuss your implementation plan with the module peers, especially when you are working on something new to you or you are working on a new feature. Because documentation can be lacking or out of date, talking to the other members may save you literally weeks of needless time. It’s also because walking reviewers through your thoughts can help save their time and allow them to provide early feedback, too.

With this thought in mind, the code review process actually contains the [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/How_to_Submit_a_Patch steps] in the red rectangular.

[[File:(Draft) Gecko Platform Code Review Best Practice.png|thumb]]

====Initial communication between requesters & reviewers ====
*Mutual understanding of the priority and the expected timeline
*:As a requester, set a clear expectation. For a new feature or big patch, it’s especially important to plan in advance.
*:As a reviewer, set a clear expectation about your availability, too.

*Check reviewer’s availability before/when submitting a patch to avoid needless waiting time
*:Reviewers should ensure that their phabricator calendars are up-to-date so that requesters will receive warnings when requests are submitted to a reviewer who is not available.
*:Reviewers should ensure their bugzilla user name displays the Out-of-office information, if they are away for more than 2 days.
*:Reviewers should consider to block accepting bugzilla needinfo/review requests, if they are away for more than 2 days.

*Architecture design documents help! Examples:
*:[https://docs.google.com/document/d/1Tk-DY1aLTNtfRqrngAmLo8Eivqo9zohsCgAyNUBfVFQ/edit Lazy image loading architecture review]
*:[https://docs.google.com/document/d/1fOlyHR2R3qFi390fj_j33-LaPd36jzdbKHOF6w7SdNk/edit OOP-iframe event delivery in Fission]

====Creating a patch & testing====
===== Commit messages =====
''“Changesets should have commit messages. The commit message should describe not just the "what" of the change but also the "why". This is especially true in cases when the "what" is obvious from the diff anyway; for larger changes it makes sense to have a summary of the "what" in the commit message.''

''As a specific example, if your diff is a one-line change that changes a method call argument from "true" to "false", having a commit message that says "change argument to mymethod from true to false" is not very helpful at all. A good commit message in this situation will at least mention the meaning for the argument. If that does not make it clear why the change is being made, the commit message should explain the "why".''[https://groups.google.com/g/mozilla.dev.platform/c/qERnoJniCds/m/YWmmKqe4EAAJ 2]

*Describe WHY in addition to WHAT
*Describe the change but not the symptom. Bad example: [Bug XYZ: Crash at Foo::Bar" ]
*For WPTs which will be upstreamed, consider how the commit message will read outside the m-c repository, and at least mention which features the tests are intending to cover.
**For example, a commit message like "Bug 1234 - Part 2: Tests" is not totally terrible in the context of Mozilla Central (though can be better) but "Part 2: Tests" is utterly meaningless upstream.
*Reviewers should feel comfortable to reject a review request if the commit message isn’t well-written or doesn’t provide useful information.
*[[https://groups.google.com/g/mozilla.dev.platform/c/qERnoJniCds/m/6DLNfrGhBQAJ Open question]] People have various preferences on the length of commit messages … We need more discussions and a much better style guide, explaining what makes a good commit message and what makes a good and descriptive bug, with a number of (good and bad) examples.

===== Patch scope & size =====
It’s arguable if the size of a patch matters much and optimizing for “small changes v.s. big diffs” is hard. But a good principle to keep is: '''seek to understand''' (understand the code, implement the change), and '''seek to be understood''' (present the change in an understandable form). Normally, smaller is better.

An example for arranging patches in sequence to [https://phabricator.services.mozilla.com/D63324#1956232 help reviewers]: https://bugzilla.mozilla.org/show_bug.cgi?id=1615581

Ensure to always stick with *the* real problem you want to fix. Be conscious about '''not''' adding unrelated fixes into that patch, even if they are super tiny.

=====Tests=====
*'''ALWAYS''' pursue this target - land code changes along with automated tests. There are exceptions or cases where testing isn’t possible using current testing frameworks. However, always ensure that you’ve thought about automated tests and you have a strong reason why no automated tests are needed or why landing without automated tests is acceptable.
**There are cases when testing isn't possible using current testing frameworks: some parts of DnD, clipboard, printing etc.
**Improving performance can often rely on existing performance tests. Or the patch might improve some very micro level issue, so adding a performance test for that might not be worth.
**Scheduling changes should get tested by overall "do tests still pass" and performance tests (but we do need better tests for responsiveness etc.)
**Scheduling changes for things like CC and GC are tested basically by looking at telemetry data.
*'''Web platform tests (WPT)''' have helped a lot for us and for cross-browser behaviors. WPT should always be the default testing framework, where possible.
*'''Write comments'''! Comments in the tests are particularly useful. It forces the patch author to think which all cases are tested and reviewers can also easily see that.
*Always, ensure that a patch is '''well-tested''' and '''self-reviewed''' before it’s submitted for review.

====Getting reviews and during reviews====
Remember, communication is key! Code reviews are more '''a discussion, not a dictation'''. Patch authors are encouraged to have different opinions than reviewers that not every review comment is being taken, as long as there's sensible discussion and reasoning about the opinions that it's better for the code quality and the users.

Respect each other’s time as yours. While we expect reviewers to get back to the patch authors within 2 days, it's also important that patch authors allocate time to address review comments in the same time frame. This helps the discussion momentum while the memory is still fresh. It may not be a good practice that an author submits a patch to review right before they take vacations without proper communication in advance, because reviewers may need explanation or elaboration from the author when they are conducting a proper review. It won’t be effective if the author is away.

====Checklist====
=====When requesting a code review=====
First thing to remember - You are responsible for the code you write. You are responsible for the issue fixing. You are responsible for the code base quality after your code is landed.

=====When doing a code review=====
*Check mozilla-standard-positions for new WebAPIs; if in doubt, file an issue to request Mozilla’s official position on that.
*Refer to [https://wiki.mozilla.org/ExposureGuidelines ExposureGuidelines] for web observable changes, including sending intent-to-* emails or creating new preferences.
*Be cautious about the follow-up suggestion. Whenever there is a "follow-up", it should be thought of work which is not going to happen ever - except perhaps in one case, when the follow-up blocks some meta bug, where fixing all the blockers are required. For example Fission meta bug has such blockers.
*Functionality
*Life cycle management
*Performance

== Release health and product quality ==
* Communication with release management (e.g. channel meeting)
**Release metrics tracking
*Regression Engineering Owner (REO)
*Security bulletin report
*Test coverage - are we doing good enough to ensure a test is added along with a fix?
**72% of the bugs with updated RCA had no tests added along with the fix according to the RCA phase I results
*Paying attentions to these slack channels as many Mozillians often report Firefox problems there
#firefox
#web-platform
#webcompat
#moco
#planning
#triage-and-tracking

== Roadmap and status communication ==

User:Hsinyi/Gecko engineering

2020-08-03T13:57:33Z

Hsinyi: /* What is the purpose of code review */ editing change

User:Hsinyi/Gecko engineering

2020-08-03T13:56:34Z

Hsinyi: /* Getting reviews and during reviews */ check list

<big><Disclaimer: This document is a draft and a collection of my personal thoughts of gecko engineering practices.></big>

== What should I work on? ==
We want to deliver a product with high qualities to our users, we want to bring new values to our users. This won't happen without collaboration with various teams and our community. Therefore, when we are thinking about what we should work on with which priority, we consider to unblock others and help others as well. Here is a list (in descending order of priority) to show others how our work is being prioritized, not necessarily a how to strictly prioritize the work.

*Catastrophic bugs
*: Bugs that block development/testing, may impact more than 25% of users, causes data loss, potential chemspill, and no workaround available. Examples include but not limit to:
*#[[Security_Severity_Ratings/Client|sec-critical security bugs]]
*#Sev-blocker or release-tracking+ bugs
*#Permanent test failures that block branch merging
*#New regressions: Not every regression is a catastrophic issue, but we should look into quickly to investigate the impact and solutions timely.

*Review and needinfo requests to unblock others
*: Browser is such a complex system. No one knows every single piece or no one can figure out every single piece shortly. Only when we have collaborative team work, are we able to deliver a satisfying product or bring new values to our users timely. (Yes, '''TIMELY''' again!) It takes time and effort to build a product with high qualities, no doubt. I am not saying we should sacrifice the quality. What I am trying to say here is we have to admit the time-to-market impact or how the life cycle of a bug impacts our user, keep that in mind and guide our work. So with that in mind, unblocking others is a key for us to succeed.
*: To do a proper and thorough and high-quality review may take time. And we should take what it needs to ensure our quality. Communication is nevertheless a key here. If it takes longer to review/respond, communicate. If you are not sure about the priority, communicate. Oh, and, if it's a simple enough review or question (even the priority isn't high), just do it and help things done.

*Serious bugs
*: Bugs that cause major Functionality/product severely impaired. If there's a satisfactory workaround, for example, flipping a preference and explaining to our users about this so they can live with it, we should do it. sec-high security bugs are one example for this category, as well as top crashes. Again, keep an eye on regressions.

*Special programs e.g. WFH bugs, q-flow bugs
*: To react upon the real world situation, priorities change for a given period of time. COVID-19 is an example of how people's working, social and daily lives are largely impacted and changed in a certain period. Some old issues may become much more sever due to this.

*Important partner and webcompat bug fixes
*:

*Bug fixes
*:

*New features
*:Again, though new features are listed at the bottom of the list, it doesn’t mean that new features are always strictly with the lowest priority compared with other engineering tasks. Nevertheless, there are more important things than new feature implementations we need to work on as well.

Add some notes for tests and documents.

== Bug triage ==
Why are we doing triage?
:Ensuring we don’t miss important bugs and timely actions are taken

What counts as being triaged?
:According to [https://firefox-source-docs.mozilla.org/bug-mgmt/policies/triage-bugzilla.html?highlight=triage%20severity|Mozilla's latest triage practice], '''severity''' field is set.

What are the actions to take?
:Paying particular attention to regressions
:Paying particular attention for bugs impacting top websites
:When needinfo someone, be clear that help is needed to try to advance it
:Responding to needinfo requests and not collecting ASSIGNED bugs
:Also, rotation duty of Core: General triage

References:

[https://wiki.mozilla.org/Platform/Layout/Triage| Layout team triage]

[https://wiki.mozilla.org/Platform/DOM_Bug_Triage| DOM team triage]

[https://apenwarr.ca/log/20171213| Backlog management presentation]

== Code review ==
=== What is the purpose of code review ===
“Code review is our basic mechanism for validating the design and implementation of patches. It also helps us maintain a level of consistency in design and implementation practices across the many hackers and among the various modules of Mozilla.” [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Code_Review_FAQ| 1]

Additionally, knowledge sharing is another major advantage.

===What does the code review process look like===
A critical thing to remember is that coding to some extent is a social process. The code review process may start '''before''' an actual patch and actual review request are submitted. '''Communication''' is key. It is very important and helpful that before you start implementing you discuss your implementation plan with the module peers, especially when you are working on something new to you or you are working on a new feature. Because documentation can be lacking or out of date, talking to the other members may save you literally weeks of needless time. It’s also because walking reviewers through your thoughts can help save their time and allow them to provide early feedback, too.

With this thought in mind, the code review process actually contains the [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/How_to_Submit_a_Patch steps] in the red rectangular.

[[File:(Draft) Gecko Platform Code Review Best Practice.png|thumb]]

====Initial communication between requesters & reviewers ====
*Mutual understanding of the priority and the expected timeline
*:As a requester, set a clear expectation. For a new feature or big patch, it’s especially important to plan in advance.
*:As a reviewer, set a clear expectation about your availability, too.

*Check reviewer’s availability before/when submitting a patch to avoid needless waiting time
*:Reviewers should ensure that their phabricator calendars are up-to-date so that requesters will receive warnings when requests are submitted to a reviewer who is not available.
*:Reviewers should ensure their bugzilla user name displays the Out-of-office information, if they are away for more than 2 days.
*:Reviewers should consider to block accepting bugzilla needinfo/review requests, if they are away for more than 2 days.

*Architecture design documents help! Examples:
*:[https://docs.google.com/document/d/1Tk-DY1aLTNtfRqrngAmLo8Eivqo9zohsCgAyNUBfVFQ/edit Lazy image loading architecture review]
*:[https://docs.google.com/document/d/1fOlyHR2R3qFi390fj_j33-LaPd36jzdbKHOF6w7SdNk/edit OOP-iframe event delivery in Fission]

====Creating a patch & testing====
===== Commit messages =====
''“Changesets should have commit messages. The commit message should describe not just the "what" of the change but also the "why". This is especially true in cases when the "what" is obvious from the diff anyway; for larger changes it makes sense to have a summary of the "what" in the commit message.''

''As a specific example, if your diff is a one-line change that changes a method call argument from "true" to "false", having a commit message that says "change argument to mymethod from true to false" is not very helpful at all. A good commit message in this situation will at least mention the meaning for the argument. If that does not make it clear why the change is being made, the commit message should explain the "why".''[https://groups.google.com/g/mozilla.dev.platform/c/qERnoJniCds/m/YWmmKqe4EAAJ 2]

*Describe WHY in addition to WHAT
*Describe the change but not the symptom. Bad example: [Bug XYZ: Crash at Foo::Bar" ]
*For WPTs which will be upstreamed, consider how the commit message will read outside the m-c repository, and at least mention which features the tests are intending to cover.
**For example, a commit message like "Bug 1234 - Part 2: Tests" is not totally terrible in the context of Mozilla Central (though can be better) but "Part 2: Tests" is utterly meaningless upstream.
*Reviewers should feel comfortable to reject a review request if the commit message isn’t well-written or doesn’t provide useful information.
*[[https://groups.google.com/g/mozilla.dev.platform/c/qERnoJniCds/m/6DLNfrGhBQAJ Open question]] People have various preferences on the length of commit messages … We need more discussions and a much better style guide, explaining what makes a good commit message and what makes a good and descriptive bug, with a number of (good and bad) examples.

===== Patch scope & size =====
It’s arguable if the size of a patch matters much and optimizing for “small changes v.s. big diffs” is hard. But a good principle to keep is: '''seek to understand''' (understand the code, implement the change), and '''seek to be understood''' (present the change in an understandable form). Normally, smaller is better.

An example for arranging patches in sequence to [https://phabricator.services.mozilla.com/D63324#1956232 help reviewers]: https://bugzilla.mozilla.org/show_bug.cgi?id=1615581

Ensure to always stick with *the* real problem you want to fix. Be conscious about '''not''' adding unrelated fixes into that patch, even if they are super tiny.

=====Tests=====
*'''ALWAYS''' pursue this target - land code changes along with automated tests. There are exceptions or cases where testing isn’t possible using current testing frameworks. However, always ensure that you’ve thought about automated tests and you have a strong reason why no automated tests are needed or why landing without automated tests is acceptable.
**There are cases when testing isn't possible using current testing frameworks: some parts of DnD, clipboard, printing etc.
**Improving performance can often rely on existing performance tests. Or the patch might improve some very micro level issue, so adding a performance test for that might not be worth.
**Scheduling changes should get tested by overall "do tests still pass" and performance tests (but we do need better tests for responsiveness etc.)
**Scheduling changes for things like CC and GC are tested basically by looking at telemetry data.
*'''Web platform tests (WPT)''' have helped a lot for us and for cross-browser behaviors. WPT should always be the default testing framework, where possible.
*'''Write comments'''! Comments in the tests are particularly useful. It forces the patch author to think which all cases are tested and reviewers can also easily see that.
*Always, ensure that a patch is '''well-tested''' and '''self-reviewed''' before it’s submitted for review.

====Getting reviews and during reviews====
Remember, communication is key! Code reviews are more '''a discussion, not a dictation'''. Patch authors are encouraged to have different opinions than reviewers that not every review comment is being taken, as long as there's sensible discussion and reasoning about the opinions that it's better for the code quality and the users.

Respect each other’s time as yours. While we expect reviewers to get back to the patch authors within 2 days, it's also important that patch authors allocate time to address review comments in the same time frame. This helps the discussion momentum while the memory is still fresh. It may not be a good practice that an author submits a patch to review right before they take vacations without proper communication in advance, because reviewers may need explanation or elaboration from the author when they are conducting a proper review. It won’t be effective if the author is away.

====Checklist====
=====When requesting a code review=====
First thing to remember - You are responsible for the code you write. You are responsible for the issue fixing. You are responsible for the code base quality after your code is landed.

=====When doing a code review=====
*Check mozilla-standard-positions for new WebAPIs; if in doubt, file an issue to request Mozilla’s official position on that.
*Refer to [https://wiki.mozilla.org/ExposureGuidelines ExposureGuidelines] for web observable changes, including sending intent-to-* emails or creating new preferences.
*Be cautious about the follow-up suggestion. Whenever there is a "follow-up", it should be thought of work which is not going to happen ever - except perhaps in one case, when the follow-up blocks some meta bug, where fixing all the blockers are required. For example Fission meta bug has such blockers.
*Functionality
*Life cycle management
*Performance

== Release health and product quality ==
== Roadmap and status communication ==

User:Hsinyi/Gecko engineering

2020-08-03T13:54:11Z

Hsinyi: /* Getting reviews and during reviews */ adding contents

<big><Disclaimer: This document is a draft and a collection of my personal thoughts of gecko engineering practices.></big>

== What should I work on? ==
We want to deliver a product with high qualities to our users, we want to bring new values to our users. This won't happen without collaboration with various teams and our community. Therefore, when we are thinking about what we should work on with which priority, we consider to unblock others and help others as well. Here is a list (in descending order of priority) to show others how our work is being prioritized, not necessarily a how to strictly prioritize the work.

*Catastrophic bugs
*: Bugs that block development/testing, may impact more than 25% of users, causes data loss, potential chemspill, and no workaround available. Examples include but not limit to:
*#[[Security_Severity_Ratings/Client|sec-critical security bugs]]
*#Sev-blocker or release-tracking+ bugs
*#Permanent test failures that block branch merging
*#New regressions: Not every regression is a catastrophic issue, but we should look into quickly to investigate the impact and solutions timely.

*Review and needinfo requests to unblock others
*: Browser is such a complex system. No one knows every single piece or no one can figure out every single piece shortly. Only when we have collaborative team work, are we able to deliver a satisfying product or bring new values to our users timely. (Yes, '''TIMELY''' again!) It takes time and effort to build a product with high qualities, no doubt. I am not saying we should sacrifice the quality. What I am trying to say here is we have to admit the time-to-market impact or how the life cycle of a bug impacts our user, keep that in mind and guide our work. So with that in mind, unblocking others is a key for us to succeed.
*: To do a proper and thorough and high-quality review may take time. And we should take what it needs to ensure our quality. Communication is nevertheless a key here. If it takes longer to review/respond, communicate. If you are not sure about the priority, communicate. Oh, and, if it's a simple enough review or question (even the priority isn't high), just do it and help things done.

*Serious bugs
*: Bugs that cause major Functionality/product severely impaired. If there's a satisfactory workaround, for example, flipping a preference and explaining to our users about this so they can live with it, we should do it. sec-high security bugs are one example for this category, as well as top crashes. Again, keep an eye on regressions.

*Special programs e.g. WFH bugs, q-flow bugs
*: To react upon the real world situation, priorities change for a given period of time. COVID-19 is an example of how people's working, social and daily lives are largely impacted and changed in a certain period. Some old issues may become much more sever due to this.

*Important partner and webcompat bug fixes
*:

*Bug fixes
*:

*New features
*:Again, though new features are listed at the bottom of the list, it doesn’t mean that new features are always strictly with the lowest priority compared with other engineering tasks. Nevertheless, there are more important things than new feature implementations we need to work on as well.

Add some notes for tests and documents.

== Bug triage ==
Why are we doing triage?
:Ensuring we don’t miss important bugs and timely actions are taken

What counts as being triaged?
:According to [https://firefox-source-docs.mozilla.org/bug-mgmt/policies/triage-bugzilla.html?highlight=triage%20severity|Mozilla's latest triage practice], '''severity''' field is set.

What are the actions to take?
:Paying particular attention to regressions
:Paying particular attention for bugs impacting top websites
:When needinfo someone, be clear that help is needed to try to advance it
:Responding to needinfo requests and not collecting ASSIGNED bugs
:Also, rotation duty of Core: General triage

References:

[https://wiki.mozilla.org/Platform/Layout/Triage| Layout team triage]

[https://wiki.mozilla.org/Platform/DOM_Bug_Triage| DOM team triage]

[https://apenwarr.ca/log/20171213| Backlog management presentation]

== Code review ==
=== What is the purpose of code review ===
“Code review is our basic mechanism for validating the design and implementation of patches. It also helps us maintain a level of consistency in design and implementation practices across the many hackers and among the various modules of Mozilla.” [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Code_Review_FAQ| 1]

Additionally, knowledge sharing is another major advantage.

===What does the code review process look like===
A critical thing to remember is that coding to some extent is a social process. The code review process may start '''before''' an actual patch and actual review request are submitted. '''Communication''' is key. It is very important and helpful that before you start implementing you discuss your implementation plan with the module peers, especially when you are working on something new to you or you are working on a new feature. Because documentation can be lacking or out of date, talking to the other members may save you literally weeks of needless time. It’s also because walking reviewers through your thoughts can help save their time and allow them to provide early feedback, too.

With this thought in mind, the code review process actually contains the [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/How_to_Submit_a_Patch steps] in the red rectangular.

[[File:(Draft) Gecko Platform Code Review Best Practice.png|thumb]]

====Initial communication between requesters & reviewers ====
*Mutual understanding of the priority and the expected timeline
*:As a requester, set a clear expectation. For a new feature or big patch, it’s especially important to plan in advance.
*:As a reviewer, set a clear expectation about your availability, too.

*Check reviewer’s availability before/when submitting a patch to avoid needless waiting time
*:Reviewers should ensure that their phabricator calendars are up-to-date so that requesters will receive warnings when requests are submitted to a reviewer who is not available.
*:Reviewers should ensure their bugzilla user name displays the Out-of-office information, if they are away for more than 2 days.
*:Reviewers should consider to block accepting bugzilla needinfo/review requests, if they are away for more than 2 days.

*Architecture design documents help! Examples:
*:[https://docs.google.com/document/d/1Tk-DY1aLTNtfRqrngAmLo8Eivqo9zohsCgAyNUBfVFQ/edit Lazy image loading architecture review]
*:[https://docs.google.com/document/d/1fOlyHR2R3qFi390fj_j33-LaPd36jzdbKHOF6w7SdNk/edit OOP-iframe event delivery in Fission]

====Creating a patch & testing====
===== Commit messages =====
''“Changesets should have commit messages. The commit message should describe not just the "what" of the change but also the "why". This is especially true in cases when the "what" is obvious from the diff anyway; for larger changes it makes sense to have a summary of the "what" in the commit message.''

''As a specific example, if your diff is a one-line change that changes a method call argument from "true" to "false", having a commit message that says "change argument to mymethod from true to false" is not very helpful at all. A good commit message in this situation will at least mention the meaning for the argument. If that does not make it clear why the change is being made, the commit message should explain the "why".''[https://groups.google.com/g/mozilla.dev.platform/c/qERnoJniCds/m/YWmmKqe4EAAJ 2]

*Describe WHY in addition to WHAT
*Describe the change but not the symptom. Bad example: [Bug XYZ: Crash at Foo::Bar" ]
*For WPTs which will be upstreamed, consider how the commit message will read outside the m-c repository, and at least mention which features the tests are intending to cover.
**For example, a commit message like "Bug 1234 - Part 2: Tests" is not totally terrible in the context of Mozilla Central (though can be better) but "Part 2: Tests" is utterly meaningless upstream.
*Reviewers should feel comfortable to reject a review request if the commit message isn’t well-written or doesn’t provide useful information.
*[[https://groups.google.com/g/mozilla.dev.platform/c/qERnoJniCds/m/6DLNfrGhBQAJ Open question]] People have various preferences on the length of commit messages … We need more discussions and a much better style guide, explaining what makes a good commit message and what makes a good and descriptive bug, with a number of (good and bad) examples.

===== Patch scope & size =====
It’s arguable if the size of a patch matters much and optimizing for “small changes v.s. big diffs” is hard. But a good principle to keep is: '''seek to understand''' (understand the code, implement the change), and '''seek to be understood''' (present the change in an understandable form). Normally, smaller is better.

An example for arranging patches in sequence to [https://phabricator.services.mozilla.com/D63324#1956232 help reviewers]: https://bugzilla.mozilla.org/show_bug.cgi?id=1615581

Ensure to always stick with *the* real problem you want to fix. Be conscious about '''not''' adding unrelated fixes into that patch, even if they are super tiny.

=====Tests=====
*'''ALWAYS''' pursue this target - land code changes along with automated tests. There are exceptions or cases where testing isn’t possible using current testing frameworks. However, always ensure that you’ve thought about automated tests and you have a strong reason why no automated tests are needed or why landing without automated tests is acceptable.
**There are cases when testing isn't possible using current testing frameworks: some parts of DnD, clipboard, printing etc.
**Improving performance can often rely on existing performance tests. Or the patch might improve some very micro level issue, so adding a performance test for that might not be worth.
**Scheduling changes should get tested by overall "do tests still pass" and performance tests (but we do need better tests for responsiveness etc.)
**Scheduling changes for things like CC and GC are tested basically by looking at telemetry data.
*'''Web platform tests (WPT)''' have helped a lot for us and for cross-browser behaviors. WPT should always be the default testing framework, where possible.
*'''Write comments'''! Comments in the tests are particularly useful. It forces the patch author to think which all cases are tested and reviewers can also easily see that.
*Always, ensure that a patch is '''well-tested''' and '''self-reviewed''' before it’s submitted for review.

====Getting reviews and during reviews====
Remember, communication is key! Code reviews are more '''a discussion, not a dictation'''. Patch authors are encouraged to have different opinions than reviewers that not every review comment is being taken, as long as there's sensible discussion and reasoning about the opinions that it's better for the code quality and the users.

Respect each other’s time as yours. While we expect reviewers to get back to the patch authors within 2 days, it's also important that patch authors allocate time to address review comments in the same time frame. This helps the discussion momentum while the memory is still fresh. It may not be a good practice that an author submits a patch to review right before they take vacations without proper communication in advance, because reviewers may need explanation or elaboration from the author when they are conducting a proper review. It won’t be effective if the author is away.

== Release health and product quality ==
== Roadmap and status communication ==

User:Hsinyi/Gecko engineering

2020-08-03T13:46:30Z

Hsinyi: /* Creating a patch & testing */ tests

<big><Disclaimer: This document is a draft and a collection of my personal thoughts of gecko engineering practices.></big>

== What should I work on? ==
We want to deliver a product with high qualities to our users, we want to bring new values to our users. This won't happen without collaboration with various teams and our community. Therefore, when we are thinking about what we should work on with which priority, we consider to unblock others and help others as well. Here is a list (in descending order of priority) to show others how our work is being prioritized, not necessarily a how to strictly prioritize the work.

*Catastrophic bugs
*: Bugs that block development/testing, may impact more than 25% of users, causes data loss, potential chemspill, and no workaround available. Examples include but not limit to:
*#[[Security_Severity_Ratings/Client|sec-critical security bugs]]
*#Sev-blocker or release-tracking+ bugs
*#Permanent test failures that block branch merging
*#New regressions: Not every regression is a catastrophic issue, but we should look into quickly to investigate the impact and solutions timely.

*Review and needinfo requests to unblock others
*: Browser is such a complex system. No one knows every single piece or no one can figure out every single piece shortly. Only when we have collaborative team work, are we able to deliver a satisfying product or bring new values to our users timely. (Yes, '''TIMELY''' again!) It takes time and effort to build a product with high qualities, no doubt. I am not saying we should sacrifice the quality. What I am trying to say here is we have to admit the time-to-market impact or how the life cycle of a bug impacts our user, keep that in mind and guide our work. So with that in mind, unblocking others is a key for us to succeed.
*: To do a proper and thorough and high-quality review may take time. And we should take what it needs to ensure our quality. Communication is nevertheless a key here. If it takes longer to review/respond, communicate. If you are not sure about the priority, communicate. Oh, and, if it's a simple enough review or question (even the priority isn't high), just do it and help things done.

*Serious bugs
*: Bugs that cause major Functionality/product severely impaired. If there's a satisfactory workaround, for example, flipping a preference and explaining to our users about this so they can live with it, we should do it. sec-high security bugs are one example for this category, as well as top crashes. Again, keep an eye on regressions.

*Special programs e.g. WFH bugs, q-flow bugs
*: To react upon the real world situation, priorities change for a given period of time. COVID-19 is an example of how people's working, social and daily lives are largely impacted and changed in a certain period. Some old issues may become much more sever due to this.

*Important partner and webcompat bug fixes
*:

*Bug fixes
*:

*New features
*:Again, though new features are listed at the bottom of the list, it doesn’t mean that new features are always strictly with the lowest priority compared with other engineering tasks. Nevertheless, there are more important things than new feature implementations we need to work on as well.

Add some notes for tests and documents.

== Bug triage ==
Why are we doing triage?
:Ensuring we don’t miss important bugs and timely actions are taken

What counts as being triaged?
:According to [https://firefox-source-docs.mozilla.org/bug-mgmt/policies/triage-bugzilla.html?highlight=triage%20severity|Mozilla's latest triage practice], '''severity''' field is set.

What are the actions to take?
:Paying particular attention to regressions
:Paying particular attention for bugs impacting top websites
:When needinfo someone, be clear that help is needed to try to advance it
:Responding to needinfo requests and not collecting ASSIGNED bugs
:Also, rotation duty of Core: General triage

References:

[https://wiki.mozilla.org/Platform/Layout/Triage| Layout team triage]

[https://wiki.mozilla.org/Platform/DOM_Bug_Triage| DOM team triage]

[https://apenwarr.ca/log/20171213| Backlog management presentation]

== Code review ==
=== What is the purpose of code review ===
“Code review is our basic mechanism for validating the design and implementation of patches. It also helps us maintain a level of consistency in design and implementation practices across the many hackers and among the various modules of Mozilla.” [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Code_Review_FAQ| 1]

Additionally, knowledge sharing is another major advantage.

===What does the code review process look like===
A critical thing to remember is that coding to some extent is a social process. The code review process may start '''before''' an actual patch and actual review request are submitted. '''Communication''' is key. It is very important and helpful that before you start implementing you discuss your implementation plan with the module peers, especially when you are working on something new to you or you are working on a new feature. Because documentation can be lacking or out of date, talking to the other members may save you literally weeks of needless time. It’s also because walking reviewers through your thoughts can help save their time and allow them to provide early feedback, too.

With this thought in mind, the code review process actually contains the [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/How_to_Submit_a_Patch steps] in the red rectangular.

[[File:(Draft) Gecko Platform Code Review Best Practice.png|thumb]]

====Initial communication between requesters & reviewers ====
*Mutual understanding of the priority and the expected timeline
*:As a requester, set a clear expectation. For a new feature or big patch, it’s especially important to plan in advance.
*:As a reviewer, set a clear expectation about your availability, too.

*Check reviewer’s availability before/when submitting a patch to avoid needless waiting time
*:Reviewers should ensure that their phabricator calendars are up-to-date so that requesters will receive warnings when requests are submitted to a reviewer who is not available.
*:Reviewers should ensure their bugzilla user name displays the Out-of-office information, if they are away for more than 2 days.
*:Reviewers should consider to block accepting bugzilla needinfo/review requests, if they are away for more than 2 days.

*Architecture design documents help! Examples:
*:[https://docs.google.com/document/d/1Tk-DY1aLTNtfRqrngAmLo8Eivqo9zohsCgAyNUBfVFQ/edit Lazy image loading architecture review]
*:[https://docs.google.com/document/d/1fOlyHR2R3qFi390fj_j33-LaPd36jzdbKHOF6w7SdNk/edit OOP-iframe event delivery in Fission]

====Creating a patch & testing====
===== Commit messages =====
''“Changesets should have commit messages. The commit message should describe not just the "what" of the change but also the "why". This is especially true in cases when the "what" is obvious from the diff anyway; for larger changes it makes sense to have a summary of the "what" in the commit message.''

''As a specific example, if your diff is a one-line change that changes a method call argument from "true" to "false", having a commit message that says "change argument to mymethod from true to false" is not very helpful at all. A good commit message in this situation will at least mention the meaning for the argument. If that does not make it clear why the change is being made, the commit message should explain the "why".''[https://groups.google.com/g/mozilla.dev.platform/c/qERnoJniCds/m/YWmmKqe4EAAJ 2]

*Describe WHY in addition to WHAT
*Describe the change but not the symptom. Bad example: [Bug XYZ: Crash at Foo::Bar" ]
*For WPTs which will be upstreamed, consider how the commit message will read outside the m-c repository, and at least mention which features the tests are intending to cover.
**For example, a commit message like "Bug 1234 - Part 2: Tests" is not totally terrible in the context of Mozilla Central (though can be better) but "Part 2: Tests" is utterly meaningless upstream.
*Reviewers should feel comfortable to reject a review request if the commit message isn’t well-written or doesn’t provide useful information.
*[[https://groups.google.com/g/mozilla.dev.platform/c/qERnoJniCds/m/6DLNfrGhBQAJ Open question]] People have various preferences on the length of commit messages … We need more discussions and a much better style guide, explaining what makes a good commit message and what makes a good and descriptive bug, with a number of (good and bad) examples.

===== Patch scope & size =====
It’s arguable if the size of a patch matters much and optimizing for “small changes v.s. big diffs” is hard. But a good principle to keep is: '''seek to understand''' (understand the code, implement the change), and '''seek to be understood''' (present the change in an understandable form). Normally, smaller is better.

An example for arranging patches in sequence to [https://phabricator.services.mozilla.com/D63324#1956232 help reviewers]: https://bugzilla.mozilla.org/show_bug.cgi?id=1615581

Ensure to always stick with *the* real problem you want to fix. Be conscious about '''not''' adding unrelated fixes into that patch, even if they are super tiny.

=====Tests=====
*'''ALWAYS''' pursue this target - land code changes along with automated tests. There are exceptions or cases where testing isn’t possible using current testing frameworks. However, always ensure that you’ve thought about automated tests and you have a strong reason why no automated tests are needed or why landing without automated tests is acceptable.
**There are cases when testing isn't possible using current testing frameworks: some parts of DnD, clipboard, printing etc.
**Improving performance can often rely on existing performance tests. Or the patch might improve some very micro level issue, so adding a performance test for that might not be worth.
**Scheduling changes should get tested by overall "do tests still pass" and performance tests (but we do need better tests for responsiveness etc.)
**Scheduling changes for things like CC and GC are tested basically by looking at telemetry data.
*'''Web platform tests (WPT)''' have helped a lot for us and for cross-browser behaviors. WPT should always be the default testing framework, where possible.
*'''Write comments'''! Comments in the tests are particularly useful. It forces the patch author to think which all cases are tested and reviewers can also easily see that.
*Always, ensure that a patch is '''well-tested''' and '''self-reviewed''' before it’s submitted for review.

== Release health and product quality ==
== Roadmap and status communication ==

User:Hsinyi/Gecko engineering

2020-08-03T13:43:50Z

Hsinyi: /* Patch scope & size */ adding link

<big><Disclaimer: This document is a draft and a collection of my personal thoughts of gecko engineering practices.></big>

== What should I work on? ==
We want to deliver a product with high qualities to our users, we want to bring new values to our users. This won't happen without collaboration with various teams and our community. Therefore, when we are thinking about what we should work on with which priority, we consider to unblock others and help others as well. Here is a list (in descending order of priority) to show others how our work is being prioritized, not necessarily a how to strictly prioritize the work.

*Catastrophic bugs
*: Bugs that block development/testing, may impact more than 25% of users, causes data loss, potential chemspill, and no workaround available. Examples include but not limit to:
*#[[Security_Severity_Ratings/Client|sec-critical security bugs]]
*#Sev-blocker or release-tracking+ bugs
*#Permanent test failures that block branch merging
*#New regressions: Not every regression is a catastrophic issue, but we should look into quickly to investigate the impact and solutions timely.

*Review and needinfo requests to unblock others
*: Browser is such a complex system. No one knows every single piece or no one can figure out every single piece shortly. Only when we have collaborative team work, are we able to deliver a satisfying product or bring new values to our users timely. (Yes, '''TIMELY''' again!) It takes time and effort to build a product with high qualities, no doubt. I am not saying we should sacrifice the quality. What I am trying to say here is we have to admit the time-to-market impact or how the life cycle of a bug impacts our user, keep that in mind and guide our work. So with that in mind, unblocking others is a key for us to succeed.
*: To do a proper and thorough and high-quality review may take time. And we should take what it needs to ensure our quality. Communication is nevertheless a key here. If it takes longer to review/respond, communicate. If you are not sure about the priority, communicate. Oh, and, if it's a simple enough review or question (even the priority isn't high), just do it and help things done.

*Serious bugs
*: Bugs that cause major Functionality/product severely impaired. If there's a satisfactory workaround, for example, flipping a preference and explaining to our users about this so they can live with it, we should do it. sec-high security bugs are one example for this category, as well as top crashes. Again, keep an eye on regressions.

*Special programs e.g. WFH bugs, q-flow bugs
*: To react upon the real world situation, priorities change for a given period of time. COVID-19 is an example of how people's working, social and daily lives are largely impacted and changed in a certain period. Some old issues may become much more sever due to this.

*Important partner and webcompat bug fixes
*:

*Bug fixes
*:

*New features
*:Again, though new features are listed at the bottom of the list, it doesn’t mean that new features are always strictly with the lowest priority compared with other engineering tasks. Nevertheless, there are more important things than new feature implementations we need to work on as well.

Add some notes for tests and documents.

== Bug triage ==
Why are we doing triage?
:Ensuring we don’t miss important bugs and timely actions are taken

What counts as being triaged?
:According to [https://firefox-source-docs.mozilla.org/bug-mgmt/policies/triage-bugzilla.html?highlight=triage%20severity|Mozilla's latest triage practice], '''severity''' field is set.

What are the actions to take?
:Paying particular attention to regressions
:Paying particular attention for bugs impacting top websites
:When needinfo someone, be clear that help is needed to try to advance it
:Responding to needinfo requests and not collecting ASSIGNED bugs
:Also, rotation duty of Core: General triage

References:

[https://wiki.mozilla.org/Platform/Layout/Triage| Layout team triage]

[https://wiki.mozilla.org/Platform/DOM_Bug_Triage| DOM team triage]

[https://apenwarr.ca/log/20171213| Backlog management presentation]

== Code review ==
=== What is the purpose of code review ===
“Code review is our basic mechanism for validating the design and implementation of patches. It also helps us maintain a level of consistency in design and implementation practices across the many hackers and among the various modules of Mozilla.” [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Code_Review_FAQ| 1]

Additionally, knowledge sharing is another major advantage.

===What does the code review process look like===
A critical thing to remember is that coding to some extent is a social process. The code review process may start '''before''' an actual patch and actual review request are submitted. '''Communication''' is key. It is very important and helpful that before you start implementing you discuss your implementation plan with the module peers, especially when you are working on something new to you or you are working on a new feature. Because documentation can be lacking or out of date, talking to the other members may save you literally weeks of needless time. It’s also because walking reviewers through your thoughts can help save their time and allow them to provide early feedback, too.

With this thought in mind, the code review process actually contains the [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/How_to_Submit_a_Patch steps] in the red rectangular.

[[File:(Draft) Gecko Platform Code Review Best Practice.png|thumb]]

====Initial communication between requesters & reviewers ====
*Mutual understanding of the priority and the expected timeline
*:As a requester, set a clear expectation. For a new feature or big patch, it’s especially important to plan in advance.
*:As a reviewer, set a clear expectation about your availability, too.

*Check reviewer’s availability before/when submitting a patch to avoid needless waiting time
*:Reviewers should ensure that their phabricator calendars are up-to-date so that requesters will receive warnings when requests are submitted to a reviewer who is not available.
*:Reviewers should ensure their bugzilla user name displays the Out-of-office information, if they are away for more than 2 days.
*:Reviewers should consider to block accepting bugzilla needinfo/review requests, if they are away for more than 2 days.

*Architecture design documents help! Examples:
*:[https://docs.google.com/document/d/1Tk-DY1aLTNtfRqrngAmLo8Eivqo9zohsCgAyNUBfVFQ/edit Lazy image loading architecture review]
*:[https://docs.google.com/document/d/1fOlyHR2R3qFi390fj_j33-LaPd36jzdbKHOF6w7SdNk/edit OOP-iframe event delivery in Fission]

====Creating a patch & testing====
===== Commit messages =====
''“Changesets should have commit messages. The commit message should describe not just the "what" of the change but also the "why". This is especially true in cases when the "what" is obvious from the diff anyway; for larger changes it makes sense to have a summary of the "what" in the commit message.''

''As a specific example, if your diff is a one-line change that changes a method call argument from "true" to "false", having a commit message that says "change argument to mymethod from true to false" is not very helpful at all. A good commit message in this situation will at least mention the meaning for the argument. If that does not make it clear why the change is being made, the commit message should explain the "why".''[https://groups.google.com/g/mozilla.dev.platform/c/qERnoJniCds/m/YWmmKqe4EAAJ 2]

*Describe WHY in addition to WHAT
*Describe the change but not the symptom. Bad example: [Bug XYZ: Crash at Foo::Bar" ]
*For WPTs which will be upstreamed, consider how the commit message will read outside the m-c repository, and at least mention which features the tests are intending to cover.
**For example, a commit message like "Bug 1234 - Part 2: Tests" is not totally terrible in the context of Mozilla Central (though can be better) but "Part 2: Tests" is utterly meaningless upstream.
*Reviewers should feel comfortable to reject a review request if the commit message isn’t well-written or doesn’t provide useful information.
*[[https://groups.google.com/g/mozilla.dev.platform/c/qERnoJniCds/m/6DLNfrGhBQAJ Open question]] People have various preferences on the length of commit messages … We need more discussions and a much better style guide, explaining what makes a good commit message and what makes a good and descriptive bug, with a number of (good and bad) examples.

===== Patch scope & size =====
It’s arguable if the size of a patch matters much and optimizing for “small changes v.s. big diffs” is hard. But a good principle to keep is: '''seek to understand''' (understand the code, implement the change), and '''seek to be understood''' (present the change in an understandable form). Normally, smaller is better.

An example for arranging patches in sequence to [https://phabricator.services.mozilla.com/D63324#1956232 help reviewers]: https://bugzilla.mozilla.org/show_bug.cgi?id=1615581

Ensure to always stick with *the* real problem you want to fix. Be conscious about '''not''' adding unrelated fixes into that patch, even if they are super tiny.

== Release health and product quality ==
== Roadmap and status communication ==

User:Hsinyi/Gecko engineering

2020-08-03T13:43:11Z

Hsinyi: /* Creating a patch & testing */ patch scope & size

<big><Disclaimer: This document is a draft and a collection of my personal thoughts of gecko engineering practices.></big>

== What should I work on? ==
We want to deliver a product with high qualities to our users, we want to bring new values to our users. This won't happen without collaboration with various teams and our community. Therefore, when we are thinking about what we should work on with which priority, we consider to unblock others and help others as well. Here is a list (in descending order of priority) to show others how our work is being prioritized, not necessarily a how to strictly prioritize the work.

*Catastrophic bugs
*: Bugs that block development/testing, may impact more than 25% of users, causes data loss, potential chemspill, and no workaround available. Examples include but not limit to:
*#[[Security_Severity_Ratings/Client|sec-critical security bugs]]
*#Sev-blocker or release-tracking+ bugs
*#Permanent test failures that block branch merging
*#New regressions: Not every regression is a catastrophic issue, but we should look into quickly to investigate the impact and solutions timely.

*Review and needinfo requests to unblock others
*: Browser is such a complex system. No one knows every single piece or no one can figure out every single piece shortly. Only when we have collaborative team work, are we able to deliver a satisfying product or bring new values to our users timely. (Yes, '''TIMELY''' again!) It takes time and effort to build a product with high qualities, no doubt. I am not saying we should sacrifice the quality. What I am trying to say here is we have to admit the time-to-market impact or how the life cycle of a bug impacts our user, keep that in mind and guide our work. So with that in mind, unblocking others is a key for us to succeed.
*: To do a proper and thorough and high-quality review may take time. And we should take what it needs to ensure our quality. Communication is nevertheless a key here. If it takes longer to review/respond, communicate. If you are not sure about the priority, communicate. Oh, and, if it's a simple enough review or question (even the priority isn't high), just do it and help things done.

*Serious bugs
*: Bugs that cause major Functionality/product severely impaired. If there's a satisfactory workaround, for example, flipping a preference and explaining to our users about this so they can live with it, we should do it. sec-high security bugs are one example for this category, as well as top crashes. Again, keep an eye on regressions.

*Special programs e.g. WFH bugs, q-flow bugs
*: To react upon the real world situation, priorities change for a given period of time. COVID-19 is an example of how people's working, social and daily lives are largely impacted and changed in a certain period. Some old issues may become much more sever due to this.

*Important partner and webcompat bug fixes
*:

*Bug fixes
*:

*New features
*:Again, though new features are listed at the bottom of the list, it doesn’t mean that new features are always strictly with the lowest priority compared with other engineering tasks. Nevertheless, there are more important things than new feature implementations we need to work on as well.

Add some notes for tests and documents.

== Bug triage ==
Why are we doing triage?
:Ensuring we don’t miss important bugs and timely actions are taken

What counts as being triaged?
:According to [https://firefox-source-docs.mozilla.org/bug-mgmt/policies/triage-bugzilla.html?highlight=triage%20severity|Mozilla's latest triage practice], '''severity''' field is set.

What are the actions to take?
:Paying particular attention to regressions
:Paying particular attention for bugs impacting top websites
:When needinfo someone, be clear that help is needed to try to advance it
:Responding to needinfo requests and not collecting ASSIGNED bugs
:Also, rotation duty of Core: General triage

References:

[https://wiki.mozilla.org/Platform/Layout/Triage| Layout team triage]

[https://wiki.mozilla.org/Platform/DOM_Bug_Triage| DOM team triage]

[https://apenwarr.ca/log/20171213| Backlog management presentation]

== Code review ==
=== What is the purpose of code review ===
“Code review is our basic mechanism for validating the design and implementation of patches. It also helps us maintain a level of consistency in design and implementation practices across the many hackers and among the various modules of Mozilla.” [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Code_Review_FAQ| 1]

Additionally, knowledge sharing is another major advantage.

===What does the code review process look like===
A critical thing to remember is that coding to some extent is a social process. The code review process may start '''before''' an actual patch and actual review request are submitted. '''Communication''' is key. It is very important and helpful that before you start implementing you discuss your implementation plan with the module peers, especially when you are working on something new to you or you are working on a new feature. Because documentation can be lacking or out of date, talking to the other members may save you literally weeks of needless time. It’s also because walking reviewers through your thoughts can help save their time and allow them to provide early feedback, too.

With this thought in mind, the code review process actually contains the [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/How_to_Submit_a_Patch steps] in the red rectangular.

[[File:(Draft) Gecko Platform Code Review Best Practice.png|thumb]]

====Initial communication between requesters & reviewers ====
*Mutual understanding of the priority and the expected timeline
*:As a requester, set a clear expectation. For a new feature or big patch, it’s especially important to plan in advance.
*:As a reviewer, set a clear expectation about your availability, too.

*Check reviewer’s availability before/when submitting a patch to avoid needless waiting time
*:Reviewers should ensure that their phabricator calendars are up-to-date so that requesters will receive warnings when requests are submitted to a reviewer who is not available.
*:Reviewers should ensure their bugzilla user name displays the Out-of-office information, if they are away for more than 2 days.
*:Reviewers should consider to block accepting bugzilla needinfo/review requests, if they are away for more than 2 days.

*Architecture design documents help! Examples:
*:[https://docs.google.com/document/d/1Tk-DY1aLTNtfRqrngAmLo8Eivqo9zohsCgAyNUBfVFQ/edit Lazy image loading architecture review]
*:[https://docs.google.com/document/d/1fOlyHR2R3qFi390fj_j33-LaPd36jzdbKHOF6w7SdNk/edit OOP-iframe event delivery in Fission]

====Creating a patch & testing====
===== Commit messages =====
''“Changesets should have commit messages. The commit message should describe not just the "what" of the change but also the "why". This is especially true in cases when the "what" is obvious from the diff anyway; for larger changes it makes sense to have a summary of the "what" in the commit message.''

''As a specific example, if your diff is a one-line change that changes a method call argument from "true" to "false", having a commit message that says "change argument to mymethod from true to false" is not very helpful at all. A good commit message in this situation will at least mention the meaning for the argument. If that does not make it clear why the change is being made, the commit message should explain the "why".''[https://groups.google.com/g/mozilla.dev.platform/c/qERnoJniCds/m/YWmmKqe4EAAJ 2]

*Describe WHY in addition to WHAT
*Describe the change but not the symptom. Bad example: [Bug XYZ: Crash at Foo::Bar" ]
*For WPTs which will be upstreamed, consider how the commit message will read outside the m-c repository, and at least mention which features the tests are intending to cover.
**For example, a commit message like "Bug 1234 - Part 2: Tests" is not totally terrible in the context of Mozilla Central (though can be better) but "Part 2: Tests" is utterly meaningless upstream.
*Reviewers should feel comfortable to reject a review request if the commit message isn’t well-written or doesn’t provide useful information.
*[[https://groups.google.com/g/mozilla.dev.platform/c/qERnoJniCds/m/6DLNfrGhBQAJ Open question]] People have various preferences on the length of commit messages … We need more discussions and a much better style guide, explaining what makes a good commit message and what makes a good and descriptive bug, with a number of (good and bad) examples.

===== Patch scope & size =====
It’s arguable if the size of a patch matters much and optimizing for “small changes v.s. big diffs” is hard. But a good principle to keep is: '''seek to understand''' (understand the code, implement the change), and '''seek to be understood''' (present the change in an understandable form). Normally, smaller is better.

An example for arranging patches in sequence to help reviewers: https://bugzilla.mozilla.org/show_bug.cgi?id=1615581

Ensure to always stick with *the* real problem you want to fix. Be conscious about '''not''' adding unrelated fixes into that patch, even if they are super tiny.

== Release health and product quality ==
== Roadmap and status communication ==

User:Hsinyi/Gecko engineering

2020-08-03T13:41:26Z

Hsinyi: /* Initial communication between requesters & reviewers */ commit messages

User:Hsinyi/Gecko engineering

2020-08-03T11:56:28Z

Hsinyi: /* Code review */ Initial communication between requesters & reviewers

File:(Draft) Gecko Platform Code Review Best Practice.png

2020-08-03T11:53:00Z

Hsinyi:

code review process

User:Hsinyi/Gecko engineering

2020-08-03T11:45:59Z

Hsinyi: /* Code review */ purpose of code review

User:Hsinyi/Gecko engineering

2020-08-03T11:38:19Z

Hsinyi: /* Bug triage */ more contents

User:Hsinyi/Gecko engineering

2020-08-03T11:32:52Z

Hsinyi: /* What should I work on? */ new features

DOM/Triage

2020-08-03T09:02:55Z

Hsinyi: /* Bugzilla Query List */ editing change

= 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://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" or "task" type - do this daily==
New bugs of "defect" or"task" type that need actions
*[https://bugzilla.mozilla.org/buglist.cgi?chfieldfrom=2020-04-20&o1=notsubstring&j2=OR&v1=needinfo&f5=CP&query_format=advanced&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&email1=intermittent-bug-filer%40mozilla.bugs&f1=flagtypes.name&product=Core&resolution=---&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&emailtype2=notequals&emailreporter2=1&f2=OP&list_id=15354325&email2=wptsync%40mozilla.bugs&query_based_on=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&v3=--&f3=bug_severity&o4=equals&o3=equals&f4=component&v4=untriaged&chfield=%5BBug%20creation%5D&emailtype1=notequals&known_name=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&emailreporter1=1 DOM Core (all types)]
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 (i.e. defects, tasks and enhancements).

*[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)]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20WorkerAndStorage%20-%20new%20Defect%20bugs&sharer_id=434964&list_id=14982384 DOM Workers & Storage(needs update per the new "Severity triage" practice)]
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 fix''able'' 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?
*[https://bugzilla.mozilla.org/buglist.cgi?product=Core&f4=cf_tracking_e10s&query_format=advanced&f1=flagtypes.name&v4=%20&v1=needinfo&o4=notequals&emailreporter2=1&o1=substring&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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&emailreporter1=1&o9=notsubstring&o8=notregexp&f7=status_whiteboard&f9=keywords&emailtype2=notequals&o7=notsubstring&f8=short_desc&f11=CP&query_based_on=DOM%20Core%20defect%20pendingNIs%20%28w%2Fo%20severity%29&f5=short_desc&known_name=DOM%20Core%20defect%20pendingNIs%20%28w%2Fo%20severity%29&email2=intermittent-bug-filer%40mozilla.bugs&chfieldfrom=2016-06-01&bug_severity=--&f2=bug_type&f6=assigned_to&o6=equals&o2=equals&chfield=%5BBug%20creation%5D&o5=notsubstring&f10=OP&v6=nobody%40mozilla.org&list_id=15354385&o3=notregexp&columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cshort_desc%2Cchangeddate%2Cstatus_whiteboard%2Cbug_severity%2Cpriority%2Cflagtypes.name&chfieldto=Now&email1=wptsync%40mozilla.bugs&classification=Components&resolution=---&f3=keywords&emailtype1=notequals DOM Core needinfo? (all types)]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20Fission%20defect%20pendingNIs&sharer_id=434964&list_id=14982428 DOM Fission needinfo? (needs update per the new triage practice)]
*[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? (needs update per the new triage practice) ]

==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:
*[https://bugzilla.mozilla.org/buglist.cgi?f5=CP&emailtype1=notequals&j2=OR&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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&chfield=%5BBug%20creation%5D&o4=equals&emailtype2=notequals&email1=intermittent-bug-filer%40mozilla.bugs&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&chfieldfrom=2020-04-20&f4=component&resolution=---&emailreporter1=1&known_name=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&query_based_on=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&v3=S1&query_format=advanced&list_id=15354367&f1=flagtypes.name&f2=OP&f3=bug_severity&product=Core&email2=wptsync%40mozilla.bugs&emailreporter2=1&o3=equals&o1=notsubstring&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 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 (needs update per the new triage practice)]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20WorkerAndStorage-P1&sharer_id=434964&list_id=14982479 DOM Worker&Storage P1s (needs update per the new triage practice)]

==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:
*[https://bugzilla.mozilla.org/buglist.cgi?o1=notsubstring&f3=bug_severity&f1=flagtypes.name&o3=equals&emailreporter1=1&chfield=%5BBug%20creation%5D&f5=CP&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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%20S1&list_id=15361214&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&email1=intermittent-bug-filer%40mozilla.bugs&query_format=advanced&j2=OR&chfieldfrom=2020-04-20&v3=S1&emailtype2=notequals&emailtype1=notequals&resolution=---&product=Core&query_based_on=DOM%20Core%20S1&emailreporter2=1&email2=wptsync%40mozilla.bugs&o4=equals&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&f4=component&f2=OP DOM Core S1s]

S2 bugs:
*[https://bugzilla.mozilla.org/buglist.cgi?f4=component&chfieldfrom=2020-04-20&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&email1=intermittent-bug-filer%40mozilla.bugs&emailtype2=notequals&o4=equals&chfield=%5BBug%20creation%5D&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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&j2=OR&emailtype1=notequals&f5=CP&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&o1=notsubstring&o3=equals&emailreporter2=1&email2=wptsync%40mozilla.bugs&product=Core&f3=bug_severity&f1=flagtypes.name&f2=OP&list_id=15361211&query_format=advanced&v3=S2&query_based_on=DOM%20Core%20S1&known_name=DOM%20Core%20S1&emailreporter1=1&resolution=--- DOM Core S2s]

P1 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?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:
*[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=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:
*[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?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]

Other useful ones:
*'''[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.

==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?

Old bugs that need re-prioritization or re-validation
*[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=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]

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

DOM/Triage

2020-08-03T09:02:14Z

Hsinyi: /* Severity/Priority nomination */ editing change

= 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://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" or "task" type - do this daily==
New bugs of "defect" or"task" type that need actions
*[https://bugzilla.mozilla.org/buglist.cgi?chfieldfrom=2020-04-20&o1=notsubstring&j2=OR&v1=needinfo&f5=CP&query_format=advanced&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&email1=intermittent-bug-filer%40mozilla.bugs&f1=flagtypes.name&product=Core&resolution=---&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&emailtype2=notequals&emailreporter2=1&f2=OP&list_id=15354325&email2=wptsync%40mozilla.bugs&query_based_on=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&v3=--&f3=bug_severity&o4=equals&o3=equals&f4=component&v4=untriaged&chfield=%5BBug%20creation%5D&emailtype1=notequals&known_name=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&emailreporter1=1 DOM Core (all types)]
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 (i.e. defects, tasks and enhancements).

*[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)]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20WorkerAndStorage%20-%20new%20Defect%20bugs&sharer_id=434964&list_id=14982384 DOM Workers & Storage(needs update per the new "Severity triage" practice)]
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 fix''able'' 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?
*[https://bugzilla.mozilla.org/buglist.cgi?product=Core&f4=cf_tracking_e10s&query_format=advanced&f1=flagtypes.name&v4=%20&v1=needinfo&o4=notequals&emailreporter2=1&o1=substring&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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&emailreporter1=1&o9=notsubstring&o8=notregexp&f7=status_whiteboard&f9=keywords&emailtype2=notequals&o7=notsubstring&f8=short_desc&f11=CP&query_based_on=DOM%20Core%20defect%20pendingNIs%20%28w%2Fo%20severity%29&f5=short_desc&known_name=DOM%20Core%20defect%20pendingNIs%20%28w%2Fo%20severity%29&email2=intermittent-bug-filer%40mozilla.bugs&chfieldfrom=2016-06-01&bug_severity=--&f2=bug_type&f6=assigned_to&o6=equals&o2=equals&chfield=%5BBug%20creation%5D&o5=notsubstring&f10=OP&v6=nobody%40mozilla.org&list_id=15354385&o3=notregexp&columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cshort_desc%2Cchangeddate%2Cstatus_whiteboard%2Cbug_severity%2Cpriority%2Cflagtypes.name&chfieldto=Now&email1=wptsync%40mozilla.bugs&classification=Components&resolution=---&f3=keywords&emailtype1=notequals DOM Core needinfo? (all types)]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20Fission%20defect%20pendingNIs&sharer_id=434964&list_id=14982428 DOM Fission needinfo? (needs update per the new triage practice)]
*[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? (needs update per the new triage practice) ]

==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:
*[https://bugzilla.mozilla.org/buglist.cgi?f5=CP&emailtype1=notequals&j2=OR&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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&chfield=%5BBug%20creation%5D&o4=equals&emailtype2=notequals&email1=intermittent-bug-filer%40mozilla.bugs&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&chfieldfrom=2020-04-20&f4=component&resolution=---&emailreporter1=1&known_name=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&query_based_on=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&v3=S1&query_format=advanced&list_id=15354367&f1=flagtypes.name&f2=OP&f3=bug_severity&product=Core&email2=wptsync%40mozilla.bugs&emailreporter2=1&o3=equals&o1=notsubstring&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 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 (needs update per the new triage practice)]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20WorkerAndStorage-P1&sharer_id=434964&list_id=14982479 DOM Worker&Storage P1s (needs update per the new triage practice)]

==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:
*[https://bugzilla.mozilla.org/buglist.cgi?o1=notsubstring&f3=bug_severity&f1=flagtypes.name&o3=equals&emailreporter1=1&chfield=%5BBug%20creation%5D&f5=CP&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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%20S1&list_id=15361214&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&email1=intermittent-bug-filer%40mozilla.bugs&query_format=advanced&j2=OR&chfieldfrom=2020-04-20&v3=S1&emailtype2=notequals&emailtype1=notequals&resolution=---&product=Core&query_based_on=DOM%20Core%20S1&emailreporter2=1&email2=wptsync%40mozilla.bugs&o4=equals&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&f4=component&f2=OP DOM Core S1s]

S2 bugs:
*[https://bugzilla.mozilla.org/buglist.cgi?f4=component&chfieldfrom=2020-04-20&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&email1=intermittent-bug-filer%40mozilla.bugs&emailtype2=notequals&o4=equals&chfield=%5BBug%20creation%5D&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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&j2=OR&emailtype1=notequals&f5=CP&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&o1=notsubstring&o3=equals&emailreporter2=1&email2=wptsync%40mozilla.bugs&product=Core&f3=bug_severity&f1=flagtypes.name&f2=OP&list_id=15361211&query_format=advanced&v3=S2&query_based_on=DOM%20Core%20S1&known_name=DOM%20Core%20S1&emailreporter1=1&resolution=--- DOM Core S2s]

P1 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?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:
*[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=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:
*[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?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]

Other useful ones:
*'''[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 CoreNew 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?

Old bugs that need re-prioritization or re-validation
*[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=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]

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

DOM/Triage

2020-08-03T08:56:49Z

Hsinyi: /* Bugzilla Query List */ DOM Core S1 & S2

= 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://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" or "task" type - do this daily==
New bugs of "defect" or"task" type that need actions
*[https://bugzilla.mozilla.org/buglist.cgi?chfieldfrom=2020-04-20&o1=notsubstring&j2=OR&v1=needinfo&f5=CP&query_format=advanced&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&email1=intermittent-bug-filer%40mozilla.bugs&f1=flagtypes.name&product=Core&resolution=---&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&emailtype2=notequals&emailreporter2=1&f2=OP&list_id=15354325&email2=wptsync%40mozilla.bugs&query_based_on=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&v3=--&f3=bug_severity&o4=equals&o3=equals&f4=component&v4=untriaged&chfield=%5BBug%20creation%5D&emailtype1=notequals&known_name=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&emailreporter1=1 DOM Core (all types)]
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 (i.e. defects, tasks and enhancements).

*[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)]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20WorkerAndStorage%20-%20new%20Defect%20bugs&sharer_id=434964&list_id=14982384 DOM Workers & Storage(needs update per the new "Severity triage" practice)]
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 fix''able'' 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?
*[https://bugzilla.mozilla.org/buglist.cgi?product=Core&f4=cf_tracking_e10s&query_format=advanced&f1=flagtypes.name&v4=%20&v1=needinfo&o4=notequals&emailreporter2=1&o1=substring&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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&emailreporter1=1&o9=notsubstring&o8=notregexp&f7=status_whiteboard&f9=keywords&emailtype2=notequals&o7=notsubstring&f8=short_desc&f11=CP&query_based_on=DOM%20Core%20defect%20pendingNIs%20%28w%2Fo%20severity%29&f5=short_desc&known_name=DOM%20Core%20defect%20pendingNIs%20%28w%2Fo%20severity%29&email2=intermittent-bug-filer%40mozilla.bugs&chfieldfrom=2016-06-01&bug_severity=--&f2=bug_type&f6=assigned_to&o6=equals&o2=equals&chfield=%5BBug%20creation%5D&o5=notsubstring&f10=OP&v6=nobody%40mozilla.org&list_id=15354385&o3=notregexp&columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cshort_desc%2Cchangeddate%2Cstatus_whiteboard%2Cbug_severity%2Cpriority%2Cflagtypes.name&chfieldto=Now&email1=wptsync%40mozilla.bugs&classification=Components&resolution=---&f3=keywords&emailtype1=notequals DOM Core needinfo? (all types)]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20Fission%20defect%20pendingNIs&sharer_id=434964&list_id=14982428 DOM Fission needinfo? (needs update per the new triage practice)]
*[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? (needs update per the new triage practice) ]

==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:
*[https://bugzilla.mozilla.org/buglist.cgi?f5=CP&emailtype1=notequals&j2=OR&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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&chfield=%5BBug%20creation%5D&o4=equals&emailtype2=notequals&email1=intermittent-bug-filer%40mozilla.bugs&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&chfieldfrom=2020-04-20&f4=component&resolution=---&emailreporter1=1&known_name=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&query_based_on=DOM%20Core%20new%20bugs%20no%20pending%20NI%20%28w%2Fo%20severity%29&v3=S1&query_format=advanced&list_id=15354367&f1=flagtypes.name&f2=OP&f3=bug_severity&product=Core&email2=wptsync%40mozilla.bugs&emailreporter2=1&o3=equals&o1=notsubstring&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 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 (needs update per the new triage practice)]
*[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DOM%20WorkerAndStorage-P1&sharer_id=434964&list_id=14982479 DOM Worker&Storage P1s (needs update per the new triage practice)]

==Priority nomination==
Make P2s to P1s, and P3s to P2s/P1s after review. (De-)Nomination happens at least once a release.

* are any of these super-urgent and thus really P1?
* 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?
* is a bug even valid anymore?

== Bugzilla Query List ==
S1 bugs:
*[https://bugzilla.mozilla.org/buglist.cgi?o1=notsubstring&f3=bug_severity&f1=flagtypes.name&o3=equals&emailreporter1=1&chfield=%5BBug%20creation%5D&f5=CP&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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%20S1&list_id=15361214&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&email1=intermittent-bug-filer%40mozilla.bugs&query_format=advanced&j2=OR&chfieldfrom=2020-04-20&v3=S1&emailtype2=notequals&emailtype1=notequals&resolution=---&product=Core&query_based_on=DOM%20Core%20S1&emailreporter2=1&email2=wptsync%40mozilla.bugs&o4=equals&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&f4=component&f2=OP DOM Core S1s]

S2 bugs:
*[https://bugzilla.mozilla.org/buglist.cgi?f4=component&chfieldfrom=2020-04-20&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&email1=intermittent-bug-filer%40mozilla.bugs&emailtype2=notequals&o4=equals&chfield=%5BBug%20creation%5D&component=DOM%3A%20Core%20%26%20HTML&component=DOM%3A%20Drag%20%26%20Drop&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&j2=OR&emailtype1=notequals&f5=CP&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&o1=notsubstring&o3=equals&emailreporter2=1&email2=wptsync%40mozilla.bugs&product=Core&f3=bug_severity&f1=flagtypes.name&f2=OP&list_id=15361211&query_format=advanced&v3=S2&query_based_on=DOM%20Core%20S1&known_name=DOM%20Core%20S1&emailreporter1=1&resolution=--- DOM Core S2s]

P1 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?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:
*[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=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:
*[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?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]

Other useful ones:
*'''[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 CoreNew 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?

Old bugs that need re-prioritization or re-validation
*[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=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]

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

DOM/Triage

2020-08-03T08:47:10Z

Hsinyi: /* Bugzilla Query List */ DOM Core new WPTs

DOM/Triage

2020-08-03T08:42:23Z

Hsinyi: /* New bugs of "defect" or "task" type - do this daily */ editing change

DOM/Triage

2020-08-03T08:41:43Z

Hsinyi: /* New bugs of "defect" or "task" type - do this daily */ editing change

DOM/Triage

2020-07-28T17:15:57Z

Hsinyi: /* Unanswered-needinfo new defect bugs - do this weekly */ dom core update

DOM/Triage

2020-07-28T17:08:04Z

Hsinyi: /* P1 bugs (including defect, task, enhancement) - do this weekly */ DOM Core S1

DOM/Triage

2020-07-28T16:54:12Z

Hsinyi: /* Unanswered-needinfo new defect bugs - do this weekly */ Fission and W&S teams need update

DOM/Triage

2020-07-28T16:52:15Z

Hsinyi: /* Unanswered-needinfo new defect bugs - do this weekly */ DOM Core update, add Drag & Drop

DOM/Triage

2020-07-28T16:48:00Z

Hsinyi: /* New bugs of "defect" or "task" type - do this daily */ DOM Core, add Drag& Drop

User:Hsinyi/Gecko engineering

2020-06-16T14:50:48Z

Hsinyi: /* Bug triage */ editorial

User:Hsinyi/Gecko engineering

2020-06-16T14:50:02Z

Hsinyi: /* Bug triage */ adding references

User:Hsinyi/Gecko engineering

2020-06-10T13:36:42Z

Hsinyi: special programs

User:Hsinyi/Gecko engineering

2020-06-10T06:21:17Z

Hsinyi: Add Permanent test failure as an example for catastrophic bugs

User:Hsinyi/Gecko engineering

2020-06-10T06:17:52Z

Hsinyi: serious bugs