canmove, Confirmed users
1,635
edits
No edit summary |
|||
| Line 98: | Line 98: | ||
** Less predictability of release & merge dates around year end | ** Less predictability of release & merge dates around year end | ||
*** However, we could mitigate this by looking at the dates for the next two or three years now, and publishing a calendar. If we've a consistent rule, then it makes it easier. | *** However, we could mitigate this by looking at the dates for the next two or three years now, and publishing a calendar. If we've a consistent rule, then it makes it easier. | ||
== Option 6 - "Manual only release" == | |||
* '''Details''' | |||
** We only release the manual updates on mozilla.org and the MU / Check for Updates. Automatic updates are disabled for desktop (obviously mobile would be fully released) until Jan. I think this is mechanically possible, not 100% positive. | |||
* '''Official Ship''' | |||
** December 20th (note that anyone seeking out the update will get it, so we are officially shipped) | |||
* '''Benefits''' | |||
** Hit our date in the eyes of external / press people | |||
** Slow ramp | |||
** 9.0.1 has less urgency / impact (we don't normally yank the builds from mozilla.org in chemspills) | |||
* '''Downsides''' | |||
** What do we do about security announcements? | |||
** Possibly some press about slow uptake / Firefox 9 not being accepted | |||
** Most of the additional testing would be on the pave-over / new install path, not updates | |||
*** There would still be some updates due to the manual check for updates, but not much | |||