Webtools:Release Notes: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
mNo edit summary
(What really happens)
Line 1: Line 1:
{{draft}}
{{draft}}
These instructions assume you are updating Firefox, the current version is 3.0, and the new version is 3.1. Substitute as appropriate. When releasing a new version of a product, there are several bugs that are filed under Websites::www.mozilla.com:
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'''.


* Create firstrun page
== Beta Release ==
* Create whatsnew page
* Create releasenotes pages
* Create localized in-product pages


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:


== Update product-details ==
* 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.
 
=== mozilla.com ===
 
* `svn copy` /en-US/firefox/3.0.1rc to /en-US/firefox/3.0.2rc
* Replace "Firefox 3.0.1" with "Firefox 3.0.2" in both /en-US/firefox/3.0.2rc/releasenotes/index.html and /en-US/firefox/3.0.2rc/whatsnew/index.html (there are at least four places to change)
* Update the release date in /en-US/firefox/3.0.2rc/releasenotes/index.html (make sure to correctly specify if this is RC1, RC2, etc.)
* Edit .htaccess, uncomment the "Temporary rewrite" RewriteRule for Firefox betas, and change the two places that refer to 3.0.1 to 3.0.2 (3\.0\.1 and 3.0.1)
* Have QA look at the staging site with your changes
* Once QA is happy, merge to production
* Once tagged for production, comment out the RewriteRule in the trunk version of .htaccess and commit
 
 
== Final Release ==
 
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
* Copy localized in-product pages for Firefox 3.0.2 release
 
=== 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/firefoxDetails.class.php top of the class]
** When you commit this change, make note of the revision
** 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 mozilla.com ==


* ''Find the bug holding the firstrun content'' and place it in /en-US/firefox/3.1/firstrun/index.html
* `svn copy` /en-US/firefox/3.0.1 to /en-US/firefox/3.0.2
* ''Find the bug holding the whatsnew content'' and place it in /en-US/firefox/3.1/whatsnew/index.html
* 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, etc.)
* ''Find the bug holding the releasenotes'' and place them in /en-US/firefox/3.1/releasenotes/index.html
* Add release to /en-US/firefox/releases/index.html
** Make sure these pages conform to our template, use PHP headers/footers, and validate!
* Run `svn propedit svn:externals` in / and change the product-details external (-r<rev>) to whatever revision you just committed
* run `svn propedit svn:externals` and change the product-details external 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
* Have QA look at the staging site with your changes
* Once QA is happy, merge to production
* Once QA is happy, merge to production (don't forget the localized in-product pages!)
* Notify (irc works):
* Notify (irc works):
** mozilla-europe
** mozilla-japan
** mozilla-japan
** mozilla china (?)


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


(pascal - what goes on here?)
(pascal - what goes on here?)

Revision as of 07:37, 21 November 2007

Draft-template-image.png THIS PAGE IS A WORKING DRAFT Pencil-emoji U270F-gray.png
The page may be difficult to navigate, and some information on its subject might be incomplete and/or evolving rapidly.
If you have any questions or ideas, please add them as a new topic on the discussion page.

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.

Beta Release

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.

mozilla.com

  • `svn copy` /en-US/firefox/3.0.1rc to /en-US/firefox/3.0.2rc
  • Replace "Firefox 3.0.1" with "Firefox 3.0.2" in both /en-US/firefox/3.0.2rc/releasenotes/index.html and /en-US/firefox/3.0.2rc/whatsnew/index.html (there are at least four places to change)
  • Update the release date in /en-US/firefox/3.0.2rc/releasenotes/index.html (make sure to correctly specify if this is RC1, RC2, etc.)
  • Edit .htaccess, uncomment the "Temporary rewrite" RewriteRule for Firefox betas, and change the two places that refer to 3.0.1 to 3.0.2 (3\.0\.1 and 3.0.1)
  • Have QA look at the staging site with your changes
  • Once QA is happy, merge to production
  • Once tagged for production, comment out the RewriteRule in the trunk version of .htaccess and commit


Final Release

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
  • Copy localized in-product pages for Firefox 3.0.2 release

Update product-details

  • Follow the directions in the top of the class
    • When you commit this change, make note of the revision
  • Note that you should check the shipped-locales 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

  • `svn copy` /en-US/firefox/3.0.1 to /en-US/firefox/3.0.2
  • 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, etc.)
  • Add release to /en-US/firefox/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 localized in-product pages!)
  • Notify (irc works):
    • mozilla-europe
    • mozilla-japan
    • mozilla china (?)

Update mozilla-europe.org

(pascal - what goes on here?)

Retrieved from "https://wiki.mozilla.org/index.php?title=Webtools:Release_Notes&oldid=75425"