Confirmed users
1,321
edits
Webtools:Release Notes: Difference between revisions
→Before the release:
mNo edit summary |
|||
| Line 59: | Line 59: | ||
* warn localizers about the imminent release through the mailing list | * warn localizers about the imminent release through the mailing list | ||
* change /xx/l10n/product.php files to update the version number to 2.0.0.x (still used in the old function generating release notes links on the site) | * 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 | * 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 the 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) | * 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/ | * 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 | * 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 | * 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 revision | * 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 | * 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. | * 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 | * 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 ==== | ==== 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 | * 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 | ||