MozillaWiki

Webtools:Thunderbird Release Notes: Difference between revisions

(Initial WIP version)
 
(Bring up to date for maintenance releases.)
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
__TOC__
__TOC__
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.
Note that this list is specific to  '''Thunderbird''', see [[Webtools:Release_Notes]] for Firefox specific information.


== Beta Release ==
== Stable Release on beta channel for a period of time ==
 
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 ===
=== Update mozillamessaging.com ===


* `svn copy` trunk/en-US/thunderbird/3.0.1rc to trunk/en-US/thunderbird/3.0.2rc
* File locations:
* Update the php header of TBD file(s)
** 3.0 builds: [http://svn.mozilla.org/mozillamessaging.com/sites/mozillamessaging.com/trunk/en-US/thunderbird/3.0.xrc/ trunk/en-US/thunderbird/3.0.xrc]
* Update other release note text as appropriate
** 3.1 builds: [http://svn.mozilla.org/mozillamessaging.com/sites/mozillamessaging.com/trunk/en-US/thunderbird/3.1.xrc/ trunk/en-US/thunderbird/3.1.xrc]
* Update the php header of whatsnew/index.html and releasenotes/index.html file(s) to include the new dates, versions and bug fix versions.
* Update other release note text as appropriate - e.g. known issues.
* Have QA look at the staging site with your changes
* Have QA look at the staging site with your changes
* Once QA is happy, merge to production
* 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.
* Once on production, request Build/IT to add redirects for the current version to the beta pages.
 
== Final release of a Maintenance release ==


== Final Release ==
These instructions assume you are updating Thunderbird, the current version is 3.1.1, and the new version is 3.1.2. Substitute as appropriate. In every case and change, '''make sure all pages validate properly'''.


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


* Create in-product pages for Firefox 3.0.2 release
''When releasing a new version of a product, there is one bug that is filed under Websites :: www.mozilla.com:
* Copy localized in-product pages for Firefox 3.0.2 release
** pascalc does this usually, so you just need to tag his changes''


=== Update product-details ===
* ''Update product-details for Thunderbird x.x.x release''


* Follow the directions in the [http://svn.mozilla.org/libs/product-details/firefoxDetails.class.php top of the class]
* Follow the directions in the [http://svn.mozilla.org/libs/product-details/thunderbirdDetails.class.php 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
** When you commit this change, make note of the revision
* Note that you should check the <code>shipped-locales</code> file to make sure no locales were added/removed for this release
* Note that you should check the <code>shipped-locales</code> file to make sure no locales were added/removed for this release
** If something needs to be changed, update product-details appropriately
** If something needs to be changed, update product-details appropriately


=== Update mozilla.com ===
=== Update mozillamessaging.com ===
 
Release Preparation:
 
* `svn copy` /en-US/thunderbird/3.1.1 to /en-US/thunderbird/3.1.2
* Edit /en-US/thunderbird/3.1.2/releasenotes/index.html
** Update the header to include the new versions and dates (these get reflected throughout the file.
** Ensure Known Issues is up to date.
** Ensure no changes in other sections.
* Add release to /en-US/thunderbird/releases/index.html
* If beta locales are being added or removed, ensure /styles/l10n.css is updated.
 
==== Pulling in product-details changes ====
 
Note: product-details for "trunk" updates whenever product-details updates. Only staging and production are limited to a specific revision of product-details.


* `svn copy` /en-US/firefox/3.0.1 to /en-US/firefox/3.0.2
* Run `svn propedit svn:externals .` in /tags/staging/includes/ and change the product-details external (-r<rev>) to whatever revision you just committed. Then commit the change.
* Edit /en-US/firefox/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/firefox/releases/index.html
* Run `svn propedit svn:externals` in / and change the product-details external (-r<rev>) to whatever revision you just committed
* Make sure pascalc has copied all the localized in-product pages and updated their versions properly for this release
* Have QA look at the staging site with your changes
* Have QA look at the staging site with your changes
* Once QA is happy, merge to production (don't forget the .htaccess revert and the localized in-product pages!)
* Notify (irc works):
** mozilla-europe
** mozilla-japan
** mozilla china (?)
=== Update mozilla-europe.org ===


'''This applies to both Thunderbird and Firefox except for the news item'''
==== Actual Release: ====


==== Before the release: ====
* '''For 3.0.x releases only:''' Run [http://hg.mozilla.org/users/bugzilla_standard8.plus.com/drivertools/file/default/website/copyLocales.py 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.x.x pages to 3.x.x (i.e. no longer to the beta 3.0.xrc directory)


* warn localizers about the imminent release through the mailing list
=== Update mozilla-europe.org ===
* change /xx/l10n/product.php files to update the product version number to 2.0.0.x (still used in the old function generating release notes links on the site)
* make sure we have the 2.0.0.x number into the php function that generates breadcrumbs if it is more than 2.0.0.20
* copy mozilla-europe.org/products/firefox/2.0.0.10/* into mozilla-europe.org/products/firefox/2.0.0.11/*
* create /bg/2.0.0.x/releasenotes folder and put the release notes from the previous en-GB version in it (bg is not a public language, we use it to provide diffs to localizers)
* get the final en-US release notes and commit the changes to /bg/2.0.0.x/releasenotes/
* check that it looks good on the staging site and that html is still valid
* create 2.0.0.x/releasenotes/ folders for all languages with the en-GB release notes in it
* Run `svn propedit svn:externals` in the production local copy and change the product-details external (-r<rev>) to the latest revision indicated in http://viewvc.svn.mozilla.org/vc/libs/product-details/?view=log
* commit changes to the production tag and file a Mozilla IT bug to svn up along with mozilla.com changes
* copy the minor release news item template for all our locales from mozilla europe internal wiki into Dotclear and set it as unpublished, change the news to the new product version number and put the news as "unpublished", put them online when it is officially released. This should be done ONLY if it is a security release, not a regression fix release like 2.0.0.11
* send the diff of changes from /bg/.../2.0.0.x/releasenotes/ using a link to viewvc.svn.mozilla.org to mozilla europe localizers via the mailing list
* if release notes for some locales are translated before the release, tag them for production and inform mozilla IT of the revision numbers involved through the Mozilla IT bug you filed previously to publish your changes


==== After the release ====
Pascalc normally does this I believe, see [[Webtools:Release_Notes#Update_mozilla-europe.org]].
* release is usually around 2AM for Europe, localizers translate the changes in the following days, tag the translation for production as they get done and file individual bugs to have them published by Mozilla IT

Latest revision as of 11:51, 4 August 2010

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

Stable Release on beta channel for a period of time

Update mozillamessaging.com

  • File locations:
  • Update the php header of whatsnew/index.html and releasenotes/index.html file(s) to include the new dates, versions and bug fix versions.
  • Update other release note text as appropriate - e.g. known issues.
  • 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 current version to the beta pages.

Final release of a Maintenance release

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

Update product-details

When releasing a new version of a product, there is one bug that is filed under Websites :: www.mozilla.com:

  • Update product-details for Thunderbird x.x.x release
  • 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.1.1 to /en-US/thunderbird/3.1.2
  • Edit /en-US/thunderbird/3.1.2/releasenotes/index.html
    • Update the header to include the new versions and dates (these get reflected throughout the file.
    • Ensure Known Issues is up to date.
    • Ensure no changes in other sections.
  • Add release to /en-US/thunderbird/releases/index.html
  • If beta locales are being added or removed, ensure /styles/l10n.css is updated.

Pulling in product-details changes

Note: product-details for "trunk" updates whenever product-details updates. Only staging and production are limited to a specific revision of product-details.

  • Run `svn propedit svn:externals .` in /tags/staging/includes/ and change the product-details external (-r<rev>) to whatever revision you just committed. Then commit the change.
  • Have QA look at the staging site with your changes

Actual Release:

  • For 3.0.x releases only: 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.x.x pages to 3.x.x (i.e. no longer to the beta 3.0.xrc directory)

Update mozilla-europe.org

Pascalc normally does this I believe, see Webtools:Release_Notes#Update_mozilla-europe.org.

Retrieved from "https://wiki.mozilla.org/index.php?title=Webtools:Thunderbird_Release_Notes&oldid=242928"