Confirmed users
978
edits
User:Hsinyi/Gecko engineering: Difference between revisions
special programs
(Add Permanent test failure as an example for catastrophic bugs) |
(special programs) |
||
| Line 5: | Line 5: | ||
*Catastrophic bugs | *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]] | *#[[Security_Severity_Ratings/Client|sec-critical security bugs]] | ||
*#Sev-blocker or release-tracking+ bugs | *#Sev-blocker or release-tracking+ bugs | ||
| Line 16: | Line 16: | ||
*Serious bugs | *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, | *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 bug fixes | *Important partner and webcompat bug fixes | ||
*: | |||
*Bug fixes | *Bug fixes | ||
*: | |||
*New features | *New features | ||