154
edits
Platform/Layout/Triage: Difference between revisions
Jump to navigation
Jump to search
→Severity Levels (In Decreasing Order): Add S2
(→Components We Triage: Minor formatting) |
(→Severity Levels (In Decreasing Order): Add S2) |
||
| Line 50: | Line 50: | ||
* Consider asking for QA support (MoCo employees only). | * Consider asking for QA support (MoCo employees only). | ||
== Severity Levels | == Severity Levels == | ||
Severity levels in Bugzilla are designated S1 - S4, in decreasing order. | Severity levels in Bugzilla are designated S1 - S4, in decreasing order. | ||
=== S1 (Catastrophic) === | === S1 (Catastrophic) === | ||
Blocks development/testing, may impact more than 25% of users, causes data loss, potential chemspill, and no workaround available. | 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'''! | ||
Examples of S1 layout bugs: | Examples of S1 layout bugs: | ||
* Any security bug with the sec-critical keyword | * Any security bug with the <code>sec-critical</code> keyword | ||
* Bugs that cause severe layout breakage on high-traffic sites, particularly breakage that results in missing or unintentionally hidden content | * Bugs that cause severe layout breakage on high-traffic sites, particularly breakage that results in missing or unintentionally hidden content | ||
* Layout bugs that break the browser user interface in significant ways | * Layout bugs that break the browser user interface in significant ways | ||
* | * Most startup crashes, unless very, very low-volume | ||
* 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 (Serious) === | |||
Major functionality/product severely impaired and a satisfactory workaround doesn't exist. | |||
Examples of S2 layout bugs: | |||
* Any security bugs with the <code>sec-high</code> keyword | |||
* Very, very low-volume startup crashes | |||
* Most other crashes unless they are very, very low volume | |||
* Severe performance issues, such as very long restyle times or very long reflows, particularly if affecting frequently-visited sites | |||
* Bugs that cause obviously visible broken layout or unintentionally hidden content | |||
* Print output bugs that cause data loss (such as missing pages, missing content) | |||
* 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 | |||