352
edits
B2G/QA/Process: Difference between revisions
Jump to navigation
Jump to search
→QA Process: blocking criteria
(→Mozilla QA Process Overview: typo) |
(→QA Process: blocking criteria) |
||
| Line 52: | Line 52: | ||
Refer to [[B2G/QA/Triage|this page]] for the detailed information on how we use Bugzilla for triage process. <br> | Refer to [[B2G/QA/Triage|this page]] for the detailed information on how we use Bugzilla for triage process. <br> | ||
Refer to [[B2G/Triage|this page]] for B2G triage process. | Refer to [[B2G/Triage|this page]] for B2G triage process. | ||
=== When to Block a Bug for Release === | |||
'''Should Block''' | |||
* Features our product team has committed us to | |||
* Major issue in new feature - especially those in which a large number of users will be impacted, or a smaller number of users will be significantly impacted | |||
* Major identifiable regression (perf or otherwise) | |||
* Non-localizable strings | |||
* Top Crashes | |||
* sec-high, sec-critical Security bugs | |||
* Smoke-test regression (special-case insta-blocker) | |||
* Data loss | |||
* Issues that block partner certification (basically legal issues) | |||
* Issues getting a lot of support calls with partners or on SUMO (exceptions need to be made after FC though) | |||
* Issues critical around updates (especially if there's been a repro) | |||
* Anything critical around the first time experience | |||
* Major Dialer, SMS, and VM communication issues (lower bar than other blockers - it's a phone) | |||
* Issues that prevent automated tests in established testsuites (visible test suites on b2g integration branches on TBPL) from running green at least 90% of the time. | |||
* Certification Waivers | |||
'''Should Not Block''' - any exceptions to these rules must be discussed on b2g-release-drivers@mozilla.org or with Release Management | |||
* Enhancements | |||
* New Features (Not committed for the release) | |||
* New perf requirements (see enhancements) | |||
* Non-critical string changes (think of the l10n, people) | |||
* Polish and other minor issues | |||
* Unfinished localization (except perhaps in the last 3 weeks) | |||
* Issues requiring the user to "zoom in and out and in and out and in and out..." | |||
* Issues in languages not being shipped in the version of B2G | |||
* Bugs without clear STR or that are not reproducible | |||
* Bugs that do not impact production phones or the simulator | |||
'''Needs Decision''' | |||
* Non-regression bugs that we chose not to block on in the last release | |||
* (though, sometimes this is because partner said "we won't block this time if you fix in the next release) | |||