Canmove, confirm
1,635
edits
Changes
→The plan
* <strike>We will update the google homepage snippets for 3.5 users, encouraging them to get the latest Firefox 4</strike> '''[done]'''
* 3.5.19 is the last planned update to Firefox 3.5
* <strike>When 3.5.19 is released we will redirect the whatsnew/firstrun pages</strike> '''[done]'''
** http://www.mozilla.com/en-US/firefox/unsupported/whatsnew
** http://www.mozilla.com/en-US/firefox/unsupported/firstrun
** <strike>We need to be sure we don’t offer Firefox 4 for those on 10.4 or PPC macs, {{bug|643872}}</strike> '''[done]'''* <strike>When 3.5.19 is released we blog/announce about 3.5 being dead and encourage users to update to Firefox 4 (and say the prompt will be released on the 3rd)</strike> '''[done]'''
''-- Wait for the whatsnew/firstrun pages and press announcement to work --''
'''ADU Target: 11 million'''
* <strike>We will do the advertised update to 4.0.1 as planned on May 3rd</strike> '''[done]'''** 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
'''ADU Target: 5 million'''
* On May 17th we will switch the snippets over to the “unsupported” snippets'''[IN PROCESS]'''
** The unsupported version snippets are at http://google_snippets.stage.mozilla.com/en-3.0/snippet-1.html
** We need to be sure we don’t offer Firefox 4 for those on 10.4 or PPC macs
*** The snippets are generic and point to Mozilla.com, so {{bug|643872}} covers this
* At the same time we also put a big warning on all Mozilla web properties, pointing them to the new version to download
'''ADU Target: 4 million'''
==== Option 1 ====
<span style="color: red">'''This is not ideal from a product or security standpoint'''</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
* A week or so after we send 3.6.18 to remaining 3.5.x users as a minor update
==== Option 2 ====
<span style="color: red">'''We do not want to do this as 3.5 is still supported / not at risk yet'''</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 3 ====
<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 #4 below'''</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 4 ====
<span style="color: orange">'''This is not ideal from a product or security standpoint but is the backup plan if {{bug|650030}} says option #2 is untenable'''</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).
