Webtools:Thunderbird Release Notes: Difference between revisions

Webtools:Thunderbird Release Notes (view source)

Revision as of 21:47, 18 January 2010

1,872 bytes removed , 18 January 2010

→‎Final Release

Standard8

canmove, Confirmed users, Bureaucrats and Sysops emeriti

3,628

edits

@@ Line 29: / Line 29: @@
 ''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
+* ''Update product-details for Thunderbird 3.0.2 release''
-* Copy localized in-product pages for Firefox 3.0.2 release
+* ''Create in-product pages for Thunderbird 3.0.2 release''
-** pascalc does this usually, so you just need to tag his changes''
 === Update product-details ===
-* 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
 * 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
-=== Update mozilla.com ===
+=== Update mozillamessaging.com ===
-* `svn copy` /en-US/firefox/3.0.1 to /en-US/firefox/3.0.2
+Release Preparation:
-* 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
+* `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 / 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
-* Once QA is happy, merge to production (don't forget the .htaccess revert and the localized in-product pages!)
+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.
+* 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
@@ Line 56: / Line 65: @@
 === Update mozilla-europe.org ===
-'''This applies to both Thunderbird and Firefox except for the news item'''
+See [[Webtools:Release_Notes#Update_mozilla-europe.org]]
-==== Before the release: ====
-* warn localizers about the imminent release through the mailing list
-* 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 ====
-* 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