Webtools:Thunderbird Release Notes

These instructions assume you are updating Thunderbird, the current version is 3.0.1, and the new version is 3.0.2. Substitute as appropriate. In every case and change, make sure all pages validate properly.

Note that this list is specific to Thunderbird, see Webtools:Release_Notes for Firefox specific information.

Beta Release

TBD:

When putting a new stability/security release version of Firefox on the beta channel prior to final release, there is one bug filed under Websites :: www.mozilla.com:

• Create in-product pages and add rewrite for Firefox 3.0.2 beta release

Note that no changes to product-details or mozilla-europe.org are made.

Update mozillamessaging.com

• `svn copy` trunk/en-US/thunderbird/3.0.1rc to trunk/en-US/thunderbird/3.0.2rc
• Update the php header of TBD file(s)
• Update other release note text as appropriate
• Have QA look at the staging site with your changes
• Once QA is happy, merge to production
• Once on production, request Build/IT to add redirects for the 3.0.2 version to the beta pages.

Final Release

TBD: When releasing a new version of a product, there are two bugs that are filed under Websites :: www.mozilla.com:

• Update product-details for Thunderbird 3.0.2 release
• Create in-product pages for Thunderbird 3.0.2 release

Update product-details

• Follow the directions in the top of the class. Don't commit yet.
• Run export_json.php. Don't commit yet.
• File a bug (Websites :: www.mozilla.com I guess) and get the diff reviewed.
• Once reviewed, commit change notify on bug.
  • When you commit this change, make note of the revision
• Note that you should check the shipped-locales file to make sure no locales were added/removed for this release
  • If something needs to be changed, update product-details appropriately

Update mozillamessaging.com

Release Preparation:

• `svn copy` /en-US/thunderbird/3.0.1 to /en-US/thunderbird/3.0.2
• Edit /en-US/thunderbird/3.0.2/releasenotes/index.html to have correct information for this release (change version number, update links, update release date, update known issues, remove Solaris builds section for now, etc.)
• Add release to /en-US/thunderbird/releases/index.html
• Run `svn propedit svn:externals` in /tags/staging/includes/ and change the product-details external (-r<rev>) to whatever revision you just committed
• Have QA look at the staging site with your changes

Actual Release:

• Run copyLocales.py in the top-level svn directory to copy all the locale pages (whatsnew and start) from 3.0.1 to 3.0.2.
• Merge pages to staging
• Once QA is happy with staging, merge to production.
• Request Build/IT to point 3.0.2 pages back to 3.0.2 (i.e. no longer to the beta 3.0.2rc directory)
• Notify (irc works):
  • mozilla-europe
  • mozilla-japan
  • mozilla china (?)

Update mozilla-europe.org

See Webtools:Release_Notes#Update_mozilla-europe.org