Confirmed users
2,816
edits
Release Management/Tracking rules: Difference between revisions
Jump to navigation
Jump to search
m
Release Management/Tracking rules (view source)
Revision as of 19:23, 3 December 2019
, 3 December 2019→Not a regression: Request tracking: added some criteria for release blockers
Ritu Kothari (talk | contribs) m (→Not a regression: Request tracking: adding bugzilla) |
m (→Not a regression: Request tracking: added some criteria for release blockers) |
||
| Line 38: | Line 38: | ||
Not every regression can or should be tracked. We can trust to the regression triage team (which includes relman). | Not every regression can or should be tracked. We can trust to the regression triage team (which includes relman). | ||
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". | 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. | ||
* A truly massive crash (with a signature higher in rank in crash-stats than OOM|small) | |||
* 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 major privacy or data loss issue | |||
= Misc = | = Misc = | ||