Thunderbird/Release Driving/Rapid Release Activities/Release and Beta Copy

From MozillaWiki
Jump to: navigation, search

There are several parts to creating the copy for a release. This page applies to both beta and main releases, and notes where differences occur.

Note: On this page we're using Thunderbird 11 beta 1 as the example for beta releases, and Thunderbird 11 as the example for main releases
Note: Where <release> is indicated, replace it with the release version number or version number and beta, e.g. 11.0 or 11.0beta

Prepare for the copy in svn

Betas that won't be released

$ cd mozilla.org/branches/staging/thunderbird
$ svn update
$ svn copy en-US/thunderbird/17.0beta/ en-US/thunderbird/18.0beta/

For the first beta in the series of ones that won't be released:

$ svn copy en-US/thunderbird/17.0/system-requirements/ en-US/thunderbird/18.0beta/system-requirements/

Finally:

$ svn commit -m "Copy beta pages in preparation for Thunderbird 18 beta release"

Beta prior to a major release

$ cd mozilla.org/branches/staging/thunderbird
$ svn update
$ svn copy en-US/thunderbird/23.0beta/ en-US/thunderbird/24.0beta/
$ mkdir en-US/thunderbird/24.0/
$ svn add en-US/thunderbird/24.0/
$ svn copy en-US/thunderbird/23.0beta/system-requirements/ en-US/thunderbird/24.0/system-requirements/
$ svn commit -m "Copy beta pages in preparation for Thunderbird 24 beta release"

Release

Note: This section assumes beta copy for the release has already been done
$ cd mozilla.org/branches/staging/thunderbird
$ svn update
$ svn copy en-US/thunderbird/17.0/releasenotes/ en-US/thunderbird/24.0/releasenotes/
$ svn copy en-US/thunderbird/17.0/whatsnew/ en-US/thunderbird/24.0/whatsnew/
$ svn commit -m "Copy release pages in preparation for Thunderbird 24 release"

Get the list of bugs fixed so far (buglist.html)

Note: Make sure that checking bug milestones has been done before this step to get more accurate results

Beta

$ hg clone http://hg.mozilla.org/users/bugzilla_standard8.plus.com/drivertools/
$ cd mozilla.org/staging/thunderbird
$ python /path/to/drivertools/website/fixed_bugs.py --app thunderbird --version 11 --milestone \
    --html --no_auth --verbose --beta --auto-update

Release

$ hg clone http://hg.mozilla.org/users/bugzilla_standard8.plus.com/drivertools/
$ cd mozilla.org/staging/thunderbird
$ python /path/to/drivertools/website/fixed_bugs.py --app thunderbird --version 11 --milestone \
    --html --no_auth --verbose --auto-update

Update the What's New page (whatsnew/index.html)

  • Edit en-US/thunderbird/<release>/whatsnew/index.html
  • Update the variables in the php header
  • Update the what's new section
  • commit the changes
  • check the changes on the staging site

Update the Release Notes page (releasenotes/index.html)

  • Edit en-US/thunderbird/<release>/releasenotes/index.html
  • Update the variables in the php header
  • Update the what's new section
  • Update the known issues section (use relnote bugs link on branch tracking page, and add as necessary)
  • Check the rest of the text
  • Commit the changes
  • Check the changes on the staging site

Update the System Requirements page

  • Edit en-US/thunderbird/<release>/systemrequirements/index.html
  • Update the page title in the header & body
  • Change the requirements if needed
  • commit the changes
  • check the changes on the staging site

Update the list of builds (all-beta.html)

This is to update the list displayed on the channels and the all-beta.html page.

cd mozilla.org/branches/staging/thunderbird
  • Run
python /path/to/generateThunderbirdDetails.py --version <version> --do-beta --autoland
Note: <version> should be replaced by the full version of the release, e.g. 11.0 or 11.0b1

This will update includes/thunderbirdBetaBuildDetails.php and commit it for you. The website normally picks up changes within 10-20 minutes.