Release Management/Tracking rules: Difference between revisions

Jump to navigation Jump to search
m
→‎Release blocking issues: added telemetry/rev
m (→‎Release blocking issues: added telemetry/rev)
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. And, generally something that would be a release blocker would also be a potential dot release driver.  
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. And, generally something that would be a release blocker would also be a potential dot release driver.  


Any of these might be a release blocker:
Any of these might be a release blocker / dot release driver:


* 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)
Line 49: Line 49:
* 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)
* a severe bug that affects all users in a particular locale/language (example, RTL issues, or IME keyboards)
* a severe bug that affects all users in a particular locale/language (example, RTL issues, or IME keyboards)
* a bug that seriously impacts revenue
* a bug that means we aren't getting telemetry important for future planning or features
* severe perf issue that is affecting users in the wild
* severe perf issue that is affecting users in the wild
* a major privacy or data loss issue
* a major privacy or data loss issue
Confirmed users
2,816

edits

Navigation menu