25
edits
Platform/Layout/Triage: Difference between revisions
Jump to navigation
Jump to search
Merging triage page with backlog page
(→Common Triage Queries: Updated link text, shortened urls, removed unused triage query) |
(Merging triage page with backlog page) |
||
| Line 3: | Line 3: | ||
This page contains information related to bug triage processes and procedures for Gecko layout and CSS bugs. | This page contains information related to bug triage processes and procedures for Gecko layout and CSS bugs. | ||
= Components | = Components = | ||
The following are the Bugzilla components in the <code>Core</code> product that the Platform Layout team is responsible for | The following are the Bugzilla components in the <code>Core</code> product that the Platform Layout team is responsible for: | ||
* [https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&component=CSS+Parsing+and+Computation CSS Parsing and Computation] | * [https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&component=CSS+Parsing+and+Computation CSS Parsing and Computation] | ||
| Line 29: | Line 29: | ||
= Triage Guidelines = | = Triage Guidelines = | ||
The definition of Triaged is bugs of type <code>defect</code> where the component is not <code>UNTRIAGED</code>, and a Severity value not equal to <code>--</code> or <code>N/A</code>. | |||
<br/>Bugs of type Task or Enhancement may have a Severity of <code>N/A</code>, but defects must have a Severity that is neither <code>--</code> nor <code>N/A</code>. | |||
For an overview of Bugzilla triage see the documentation [https://firefox-source-docs.mozilla.org/bug-mgmt/policies/triage-bugzilla.html Triage for Bugzilla] | |||
== How To Triage == | == How To Triage == | ||
Ensure that the bug is in the proper component. Is it a | Ensure that the bug is in the proper component. Is it a Layout bug? If not, move it to a more appropriate component and allow the triage owners of that component to take over from there. | ||
Otherwise, if you can reproduce the bug: | Otherwise, if you can reproduce the bug: | ||
| Line 50: | Line 48: | ||
* Consider asking for QA support (MoCo employees only). | * Consider asking for QA support (MoCo employees only). | ||
== Severity | == Severity == | ||
Severity levels in Bugzilla are designated S1 - S4, in decreasing order. | Severity levels in Bugzilla are designated S1 - S4, in decreasing order. For a bug to be considered triaged, the severity level on the bug ''must'' be set. Generally, only Mozilla Layout team members or other designated contributors should be setting severity levels on bugs in layout or CSS-related components. Bugzilla users without edit bug access do not have the ability to set severity. | ||
=== S1 | === S1 - Catastrophic === | ||
Blocks development/testing, may impact more than 25% of users, causes data loss, potential chemspill, and no workaround available. Encountering an S1 layout bug should be '''very rare'''! | Blocks development/testing, may impact more than 25% of users, causes data loss, potential chemspill, and no workaround available. Encountering an S1 layout bug should be '''very rare'''! | ||
| Line 64: | Line 62: | ||
* Crashes on frequently-visited sites, or printing crashes that affect many users | * Crashes on frequently-visited sites, or printing crashes that affect many users | ||
=== S2 | === S2 - Serious === | ||
Major functionality/product severely impaired and a satisfactory workaround doesn't exist. | Major functionality/product severely impaired and a satisfactory workaround doesn't exist. | ||
| Line 76: | Line 74: | ||
* Webcompat issues that cause more than minor cosmetic site breakage, particularly those for which a work around is cumbersome, tedious or difficult for authors to deploy | * Webcompat issues that cause more than minor cosmetic site breakage, particularly those for which a work around is cumbersome, tedious or difficult for authors to deploy | ||
=== S3 | === S3 - Normal === | ||
Blocks non-critical functionality and a work around exists | Blocks non-critical functionality and a work around exists | ||
| Line 87: | Line 85: | ||
* Most smaller to medium-sized performance issues, where performance is not a severe impediment to accessing a site for either desktop or mobile users | * Most smaller to medium-sized performance issues, where performance is not a severe impediment to accessing a site for either desktop or mobile users | ||
=== S4 | === S4 - Small/Trivial === | ||
Minor significance, cosmetic issues, low or no impact to users | Minor significance, cosmetic issues, low or no impact to users | ||
| Line 105: | Line 103: | ||
* '''[https://mzl.la/3IqoE8w Recently Triaged to S1 or S2]''': Bugs that were triaged at S1 or S2 in the last 30 days, are not stalled, and not resolved. | * '''[https://mzl.la/3IqoE8w Recently Triaged to S1 or S2]''': Bugs that were triaged at S1 or S2 in the last 30 days, are not stalled, and not resolved. | ||
* '''[https://github.com/mozilla/wg-decisions/issues/ CSS Working Group Resolutions]''': Resolutions from the CSSWG for which we should decide whether or not to file a bug. | * '''[https://github.com/mozilla/wg-decisions/issues/ CSS Working Group Resolutions]''': Resolutions from the CSSWG for which we should decide whether or not to file a bug. | ||
= How We Track Our Backlog = | |||
All tracking of backlog and work-in-progress items happens in [https://bugzilla.mozilla.org/ Bugzilla]. | |||
<br/> | |||
===== Flags ===== | |||
There are several flag used to track work in Bugzilla including: | |||
* [https://wiki.mozilla.org/BMO/UserGuide#Tracking_Flags Tracking Flags] | |||
* [https://wiki.mozilla.org/BMO/UserGuide#Status_Flags Status Flags] | |||
* [https://wiki.mozilla.org/BMO/UserGuide#Project_Flags Project Flags] | |||
* [https://wiki.mozilla.org/BMO/UserGuide#Needinfo_Flag Need Info Flags] | |||
===== Assigned ===== | |||
A bug is considered "assigned" if it has both a valid assignee AND its status is set to <code>ASSIGNED</code>. Having only one of these fields set is not sufficient for it to be tracked as an assigned bug. <code>nobody[at]mozilla.org</code> is not a valid assignee for a bug to be considered assigned. | |||
= Common Backlog Queries = | |||
* [https://mzl.la/3SYnmGO Untriaged Defects] | |||
* [https://mzl.la/4c13viY Unassigned S1 and S2 Defects] | |||
* [https://mzl.la/48LwO6a Triaged S1 and S2 Defects] | |||
* '''[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&classification=Other&status_whiteboard_type=casesubstring&query_format=advanced&status_whiteboard=layout%3Abacklog Entire Layout Backlog]''': All bugs that have been tagged as backlog candidates or are on the official backlog. For more detailed backlog tracking see our [https://wiki.mozilla.org/Platform/Layout/Backlog backlog page]. | |||
* '''[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&classification=Other&status_whiteboard_type=casesubstring&query_format=advanced&status_whiteboard=%5Blayout%3Abacklog%3Aquality%5D High-Priority Quality Bugs]''': Backlog items specifically related to improving product quality (not new features/enhancements) that will improve Firefox for many sites or users. Bugs in this list ''should meet at least one of the following criteria'': | |||
** Known webcompat bug of some significance (P1 or P2 webcompat priority, or otherwise has known webcompat challenges for multiple sites or users) | |||
** Performance-related bug the fixing of which will likely improve layout performance for multiple sites | |||
** Bug tracking spec changes that could result in future webcompat issues if left unaddressed | |||
** Bugs that have been highly-upvoted by users | |||
* '''[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&classification=Other&status_whiteboard_type=casesubstring&query_format=advanced&status_whiteboard=%5Blayout%3Abacklog%3Acode-quality%5D Code Quality Bugs]''': Backlog items related to improving code quality and reducing tech debt. Fixing these bugs should be primarily motivated by improving code cleanliness and developer productivity. | |||