canmove, Confirmed users
1,635
edits
Releases/Firefox 5/Risk mitigation strategies: Difference between revisions
Jump to navigation
Jump to search
Releases/Firefox 5/Risk mitigation strategies (view source)
Revision as of 00:06, 18 June 2011
, 18 June 2011→Outcome
No edit summary |
|||
| Line 138: | Line 138: | ||
** Discounted | ** Discounted | ||
* Argued to throttle @ 100% and then cut it off when we hit enough of an audience or to throttle at some percentage and later increase to 100% | * Argued to throttle @ 100% and then cut it off when we hit enough of an audience or to throttle at some percentage and later increase to 100% | ||
* '''Decided to throttle automatic updates to 25-33% for a maximum of 48 hours''' | * '''Decided to throttle automatic updates to 25-33% for a maximum of 51 hours (48 + 3 hours to get us to a regular PDT time)''' | ||
** Asked for 72 hours, security team was more comfortable with 72 hours | |||
** Staying throttled (or turning off updates entirely) after 51 hours needs to have clear justification and signoff from the security team | |||
* clegnitto and joduinn decided on 33% (based on some made up numbers) as they would rather overshoot than undershoot | * clegnitto and joduinn decided on 33% (based on some made up numbers) as they would rather overshoot than undershoot | ||
* clegnitto will work with metrics to get hourly ADU reports | * clegnitto will work with metrics to get hourly ADU reports | ||