Webtools:Thunderbird Release Notes: Difference between revisions

Jump to navigation Jump to search
Bring up to date for maintenance releases.
(Bring up to date for maintenance releases.)
 
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 ==
== Final release of a Maintenance release ==


TBD:
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'''.
''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''
=== Update product-details ===
* ''Create in-product pages for Thunderbird 3.0.2 release''


=== 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 [http://svn.mozilla.org/libs/product-details/thunderbirdDetails.class.php top of the class]. Don't commit yet.
* Follow the directions in the [http://svn.mozilla.org/libs/product-details/thunderbirdDetails.class.php top of the class]. Don't commit yet.
Line 46: Line 38:
Release Preparation:
Release Preparation:


* `svn copy` /en-US/thunderbird/3.0.1 to /en-US/thunderbird/3.0.2
* `svn copy` /en-US/thunderbird/3.1.1 to /en-US/thunderbird/3.1.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.)
* 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
* 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.
* 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
* Have QA look at the staging site with your changes


Actual Release:
==== Actual Release: ====


* 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.
* '''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
* Merge pages to staging
* Once QA is happy with staging, merge to production.
* 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)
* Request Build/IT to point 3.x.x pages to 3.x.x (i.e. no longer to the beta 3.0.xrc directory)
* Notify (irc works):
** mozilla-europe
** mozilla-japan
** mozilla china (?)


=== Update mozilla-europe.org ===
=== Update mozilla-europe.org ===


See [[Webtools:Release_Notes#Update_mozilla-europe.org]]
Pascalc normally does this I believe, see [[Webtools:Release_Notes#Update_mozilla-europe.org]].
canmove, Confirmed users, Bureaucrats and Sysops emeriti
3,627

edits

Navigation menu