Confirmed users
2,816
edits
Release Management/Uplift rules: Difference between revisions
Jump to navigation
Jump to search
m
Release Management/Uplift rules (view source)
Revision as of 20:30, 17 October 2016
, 17 October 2016→Release Uplift: more notes about blocking bugs and startup crashes
m (→Release Uplift: added some criteria for uplift. To do: add example bugs for each point.) |
m (→Release Uplift: more notes about blocking bugs and startup crashes) |
||
| Line 47: | Line 47: | ||
==Release Uplift== | ==Release Uplift== | ||
Some issues are bad enough that we don't want to wait till the next major release. We do major releases every 6-8 weeks. Most fixes can wait that long. Candidates for uplift to release may be drivers of a dot release, or may be "ridealongs" nice but not crucial to have. | Some issues are bad enough that we don't want to wait till the next major release. We do major releases every 6-8 weeks. Most fixes can wait that long. Candidates for uplift to release may be drivers of a dot release, or may be "ridealongs" nice but not crucial to have. If it would be a release blocker, it might be a good dot release driver. | ||
Each dot release will mean annoyance for users, and will also result in an increased chance for some users of being "orphaned" on that version. | Each dot release will mean annoyance for users, and will also result in an increased chance for some users of being "orphaned" on that version. | ||
| Line 55: | Line 55: | ||
For uplift requests to release, please give as much data as possible to help with the decision. It is also helpful if you can specify if your fix affects desktop, fennec, or both. | For uplift requests to release, please give as much data as possible to help with the decision. It is also helpful if you can specify if your fix affects desktop, fennec, or both. | ||
* Major top crash | * Major top crash (above or near the level for oom crashes). Provide evidence of impact. | ||
* High volume startup crash. | |||
* Security issue that doesn't need a chemspill, but that is bad enough to drive a dot release | * Security issue that doesn't need a chemspill, but that is bad enough to drive a dot release | ||
* Functional regression with a broad impact (We can see from telemetry it's affecting many users, or we have many reports from support.mozilla.org, input.m.o, or other user reports) | * Functional regression with a broad impact (We can see from telemetry it's affecting many users, or we have many reports from support.mozilla.org, input.m.o, or other user reports) | ||