View source for Tbird Major Update 1.5.0.x to 2.0.0.x

'''Tracking page for Thunderbird Major Update for 1.5.0.x to 2.0.0.x'''

== Schedule ==
'''Completed (during first attempt):'''
* Update message and EULA for enUS + placeholder pages for l10n: 
* Update messages and EULAs for l10n: 
** Test page for l10n review: http://www.chevrel.org/mozco/20migration/display.php
* Delete any non-translated placeholder detail pages and confirm redirects to en-US are working properly: 

'''To Do:'''
* Notify mirrors/partners: (justin/kev)
* Build prep: Mon.  (ongoing)
* QA cycle: Mon.  (ongoing)
* MU on "beta" channel: 
* MU and pave-over CJKT testing: 
* Major Update release date: TBD

== Test recommendations ==
*'''Highly recommend''' testing MU with a test profile instead of using your work email profile, or make a backup of your profile.

== QA ==

== Early test instructions from Scott ==

I've put together some update snippets for QA to start testing major update
from 1.5.0.12 to 2.0.0.6. Stealing Nick's instructions...

Here's the steps to do a quick major update test without AUS. This
points to the existing 2.0.0.4 complete mar, there is no partial for
major update. It also fudges the EULA and HTML pane by using the
Firefox 2 content.

*1. Set up 1.5.0.12 and a profile you're willing to test with
*2. Go to the Config Editor in the Advanced pane of the Options
*3. make a new string pref app.update.url.override
*4. set it to one of these URLs
    http://people.mozilla.com/~mscott/tb2006/major-update/update-win.xml
    http://people.mozilla.com/~mscott/tb2006/major-update/update-linux.xml
    http://people.mozilla.com/~mscott/tb2006/major-update/update-mac.xml

Note: you should see the Firefox license and the Firefox major update dialog.
That's expected since I'm pointing those urls right now in the xml snippets.

I tested windows but not Mac or Linux so it's possible I have a mistake in the
XML files for those platforms. If it doesn't work, let's start there first :)

== Note from Tomcat ==

Other steps to test this:
** Shutdown Thunderbird 1.5.0.12 !
** Open the File '''all-thunderbird.js''' in the Mozilla Thunderbird\defaults\pref directory
** There is a string called  '''//pref("app.update.url.override", "");'''
** Change this string to '''pref("app.update.url.override", "theupdatepath");''' 
** like '''pref("app.update.url.override", "http://people.mozilla.com/~mscott/tb2006/major-update/update-win.xml");'''
** save the changes
** Start Thunderbird 1.5.0.12 - Check for updates .....done :)

'''Test Results (during first attempt):'''

=='''Current Test Results'''==
===[http://wiki.mozilla.org/Firefox:1.5.0.x:Tbird_Major_Update_TestDay1.5.0.x_to_2.0.0.x'''Test Plan''']===
===[http://wiki.mozilla.org/Firefox:1.5.0.x:Tbird_Major_Update_1.5.0.x_to_2.0.0.x'''Test Day Results''']===
===[http://wiki.mozilla.org/Firefox:1.5.0.x:Tbird_Major_Update_Vista1.5.0.x_to_2.0.0.x'''Vista Specific Test Results''']===
===[http://wiki.mozilla.org/Firefox:1.5.0.x:Tbird_Major_Update_Results1.5.0.x_to_2.0.0.x''' Test Results Page''']===
* '''Test Tracking'''
* 1.5.0.x -> 2.0.0.x major update testing
** Test all possible update paths for major update; ongoing, initial tests PASS for 1.5.0.10 -> 2.0.0.2, need to retest for 1.5.0.12 -> 2.0.0.6) -  (for enUS across major platforms) (QA team)
** Focused testing should include:
*** Minor updates for 1.5.0.11 -> 1.5.0.12  (releasetest,)
*** Major updates for 1.5.0.12 -> 2.0.0.6  (releasetest, )
*** Verify that active-update.xml includes channel attribute and completed update is shown in Update History
** Regression testing should cover:
*** Installing over a pending update state build and checking to see if the installer cleans up all pending related files/directories (and that update does not resume on restart) - this may or may not work as expected, we need to verify the behavior

* Run test automation for update/AUS configs 
** Sign off on build verification results for update checker - 
* Final round of staged update testing
** Spot check enUS and P1 locales on all platforms (including Vista) and verify the new Update messages and EULAs -'

* Partner Builds update testing 
** Verify list of all partner build update/fallback paths -  
** Test null updates for fallback paths
*** Test automation already re-ran and verified - (run null snippet/fallback script)
*** Spot checks for partner builds - 
**** USE https://intranet.mozilla.org/Firefox:Distribution:Major_Update_TestPlan for reference (and ping rhelmer for any confusion about which builds to test and what channels should fallback)

== Build ==
* Stage Updates for final round of QA (on test channels) - 
** point to new l10n update messages and EULAs
** verify all update paths and setup bouncer/AUS
** run update verifications scripts for all locales/platforms
*** http://people.mozilla.org/~rhelmer/logs/15012-majorupdate/

* Partner Builds Updates - 
** verify all partner build update paths
** setup null updates for fallback
** stage updates for QA

* Push the button: TBD

== Lessons learned from Firefox MU ==
Looking for feedback here from Jay, juanb and others as to what snags we hit while testing Firefox MU that could help us cover all bases with Tbird MU.
* Have a plan
* Backup your profile
* Take notes