canmove, Confirmed users, Bureaucrats and Sysops emeriti
3,628
edits
Webtools:Release Notes: Difference between revisions
no edit summary
No edit summary |
|||
| (10 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
These instructions assume you are updating Firefox, 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'''. | |||
These instructions assume you are updating Firefox, 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 | |||
Note that this list is specific to Firefox, see [[Webtools:Thunderbird_Release_Notes]] for Thunderbird specific information. | |||
Once everything has been tagged for production, the QA contact for the release will file a bug under mozilla.org :: Server Operations: Web Content Push to have the pages pushed live at the appropriate time. Note that the website changes need to be live '''''at least 15-30 minutes prior''''' to Build & Release pushing out update snippets in order to make sure that users do not see 404 errors for pages. | |||
== Beta Release == | == Beta Release == | ||
| Line 10: | Line 13: | ||
Note that no changes to product-details or mozilla-europe.org are made. | Note that no changes to product-details or mozilla-europe.org are made. | ||
=== mozilla.com === | === Update mozilla.com === | ||
* `svn copy` /en-US/firefox/3.0.1rc to /en-US/firefox/3.0.2rc | * `svn copy` /en-US/firefox/3.0.1rc to /en-US/firefox/3.0.2rc | ||
| Line 26: | Line 29: | ||
* Create in-product pages for Firefox 3.0.2 release | * Create in-product pages for Firefox 3.0.2 release | ||
* Copy localized in-product pages for Firefox 3.0.2 release | * 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 === | ||
| Line 50: | Line 54: | ||
=== Update mozilla-europe.org === | === Update mozilla-europe.org === | ||
( | '''This applies to both Thunderbird and Firefox except for the news item''' | ||
==== 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 | |||