Webtools:Release Notes: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 55: Line 55:
=== Update mozilla-europe.org ===
=== Update mozilla-europe.org ===


(pascal - what goes on here?)
'''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 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 (usually I put numbers up to 2.0.0.12 in advance)
* add generic php redirects for locale fallback /products/firefox/2.0.0.x/...
* 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 revision given by mozilla.com webdevs
* 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.
* 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
===== 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
Confirmed users
1,311

edits

Navigation menu