Canmove, confirm
1,635
edits
Changes
→The plan
* <strike>We will do the advertised update to 4.0.1 as planned on May 3rd</strike> '''[done]'''
** <strike>We need to be sure we don’t offer Firefox 4 for those on 10.4 or PPC macs, {{bug|644887}} and {{bug|643860}}</strike> '''[done]'''
** We will wait at least a week or so for uptake
==== Option 1 ====
<span style="color: green">'''This is the plan of record / preferred option. It depends on {{bug|650030}} and if the investigation turns out negative or isn't done in time we will fallback to option #1 above'''</span>
* On June 21 we release Firefox 3.6.18 as an minor update to BOTH 3.6.17 and 3.5.19 users** Whether this option is possible depends on changes to release automation not yet fully spec'd, and work not yet started. See details in {{bug|650030}} ==== Option 1 2 ====<span style="color: redorange">'''This is not ideal from a product or security standpointbut is the backup plan if {{bug|650030}} says option #1 is untenable'''</span>
* On June 21st we are releasing Firefox 5 and 3.6.18. We hope that people will hear the news and get Firefox 5
'''ADU Target: 1 million'''
* A week or so after we send 3.6.18 to remaining 3.5.x users as a minor update(once the advertised update uptake rate has leveled off)
==== Option 2 3 ====
<span style="color: red">'''We do not want to do this as 3.5 is still supported / not at risk yetuntil the Firefox 5 / Firefox 3.6.18 release on June 21'''</span>
* <strike>On May 31st we send Firefox 3.6.17 to remaining 3.5.x users as a minor update</strike>
** <strike>Whether this option is possible depends on changes to release automation not yet fully spec'd, and work not yet started. See details in {{bug|650030}}</strike>
==== Option 4 ====
<span style="color: orangered">'''This is not ideal from a product or security standpoint but and is the backup plan if {{bug|650030}} says additional work when we can piggyback off of Firefox 5 in option #2 is untenable1'''</span>
* On June 21, release a "no-change-but-version-bump" FF4.0.2, and prompt FF3.0, 3.5, 3.6 users to upgrade to that instead. This is something we know we can do easily, and is better then creating a "no-change-but-version-bump" FF3.5.20 (which was proposed in emails).
