Confirmed users
2,816
edits
Release Management/Tracking rules: Difference between revisions
Release Management/Tracking rules (view source)
Revision as of 19:25, 3 December 2019
, 3 December 2019→Release blocking issues: added perf
m (added a sentence and heading) |
m (→Release blocking issues: added perf) |
||
| Line 41: | Line 41: | ||
For a very serious issue that would block either a release, or the release of a feature, relman can mark the tracking flag as "blocking". This is a judgement call by the release owner, based on how severe we think the impact is on users. Any of these might be a release blocker: | For a very serious issue that would block either a release, or the release of a feature, relman can mark the tracking flag as "blocking". This is a judgement call by the release owner, based on how severe we think the impact is on users. Any of these might be a release blocker: | ||
* A truly massive crash (with a signature higher in rank in crash-stats than OOM|small) | * A truly massive crash (with a signature higher in rank in crash-stats than OOM|small) | ||
* A horrible startup crash | |||
* a major browser/feature functionality bug that affects a large number of users | * a major browser/feature functionality bug that affects a large number of users | ||
* a severe bug that affects all users on a particular platform (Mac, Linux, or particular hardware) | * a severe bug that affects all users on a particular platform (Mac, Linux, or particular hardware) | ||
* severe perf issue that is affecting users in the wild | |||
* a major privacy or data loss issue | * a major privacy or data loss issue | ||