Releases/Firefox 11.0/BuildNotes

Notes About Releasing

Please update the Notes Template and the Release:Primer for future releases (bug fixes, changes to automation) as needed

Bugs hit

Enter any bugs pre-existing or newly discovered and filed during the release:

• bug - description

Build Engineers

rail - Tracking bug: bug 718778

Signed-off Revision(s)

Build 1: c081ebf13261

L10N changesets

Instructions on how to get them

• Firefox: l10n-changesets
• Fennec: N/A

Tags

Build #	Branch, Tags	Changeset
GECKO11_#_RELBRANCH, FIREFOX_VERSION_BUILD1 FIREFOX_VERSION_RELEASE	#

Build data

Firefox

Build #	Type	Build ID	Build machine	Time to build
1	Linux
	Linux64
	Mac
	Windows

Notes

The release is Firefox only, Fennec is supposed to be released off mozilla-esr10

Build 1

Syncing repos

03-08-2012: DONE mozilla-beta -> mozilla-release & l10n repos sync Note - new locale, lij, didn't have anything in the l10n/mozilla-release/lij repo so I had to push the beta repo to it:

# in lij.beta
hg push -f -e "ssh -l ffxbld -i ~/.ssh/ffxbld_dsa" ssh://hg.mozilla.org/releases/l10n/mozilla-release/lij

Then continued the script with a subset of locales

• Sanity check:

diff -Naur --exclude='.hg*' mozilla-beta mozilla-release > beta-release.diff

• Inspected beta-release.diff. The differences were expected (shipped-locales without mn, sw and android mozconfig changes landed after migration)

Preparing to start Automation

• Set clobbers for the appropriate masters. Doing this 24-48 hours in advance should speedup the build.
• For build1 only, create a symlink for your $version (eg 11.0b4, 10.0.2esr, 10.0.2, 3.6.27) (until bug 725839 is resolved)

# ffxbld@stage
cd /pub/mozilla.org/firefox/nightly/
mkdir ../candidates/11.0-candidates
ln -s ../candidates/11.0-candidates 11.0-candidates

• Reserve slaves

echo "10"> master/reserved_slaves_bm08-build1

• Update l10n changesets for desktop
• Land automation configs (are you or buildduty going to reconfig? great, merge. otherwise double-land only your configs)
• Tag buildbot-configs, buildbotcustom, & tools with build & release tags (FIREFOX_11_0_RELEASE FIREFOX_11_0_BUILD1)
• update and reconfigure the master
• start automation

# Dry-run
source ../bin/activate
PYTHONPATH=. ../bin/python ../tools/buildbot-helpers/release_sanity.py -u rail \
  -V 11.0 --branch mozilla-release --build-number 1 -c release-firefox-mozilla-release.py \
  --products firefox --l10n-dashboad-version=11 --dryrun localhost:9001

• Failed because beta-only locales was listed on the l10n dashboard:

2012-03-09 11:48:54,898 : ERROR :       locale mn missing in config
2012-03-09 11:48:54,898 : ERROR :       locale sw missing in config
2012-03-09 11:48:54,898 : ERROR : Error verifying l10n dashboard changesets

• reran

# Dry-run
source ../bin/activate
PYTHONPATH=. ../bin/python ../tools/buildbot-helpers/release_sanity.py -u rail \
  -V 11.0 --branch mozilla-release --build-number 1 -c release-firefox-mozilla-release.py \
  --products firefox --l10n-dashboad-version=11 --bypass-l10n-check --dryrun localhost:9001

PYTHONPATH=. ../bin/python ../tools/buildbot-helpers/release_sanity.py -u rail \
  -V 11.0 --branch mozilla-release --build-number 1 -c release-firefox-mozilla-release.py \
  --products firefox --l10n-dashboad-version=11 --bypass-l10n-check localhost:9001

E-mail Metrics

Use the address "metrics-alerts < AT > mozilla < PERIOD > org"

And for 11.0 final it's

Firefox,firefox,firefox,11.0,11.0

E-mail mirrors@mozilla.org

Not necessary for rapid release betas, files only go as far as the 'internal mirrors'.

Coordinate yourself with the person creating the ESR and the latest release which normally go out at the same time.

They want to know approximately what time push to external mirrors will occur. Ideally this is a 24hr notice to them, with the estimated time.

Subject: Firefox 11.0 [and {VERSION2}] coming to mirrors on {DATE}
Body:
We're planning on pushing our Firefox 11.0 [and {VERSION2}] release(s) to mirrors 24 hours before {DATE}.
# If this is a chemspill, please mention that in the email as it will mean pinging 
# for CDN to be enabled when the push to internal mirrors happens

If you believe these releases or these dates will cause any problems,
please notify release at mozilla.com. If you have any problems with mirror
status/weights/etc, please notify mirror-submissions at mozilla.org.

Edit rsync exclude files

Edit /pub/mozilla.org/zz/rsyncd-mozilla-releases.exclude on stage so that it excludes the current release. This prevents external mirrors from picking up the new release prematurely.

For rapid release betas, this is not necessary as there's already an exclude that matches beta releases.

Unittests / Talos

1. Look to see that they ran
2. Document any oranges (per platform) for unittests - if possible, try to confirm it's known/random
3. Make sure there's no red/failures that we need to have a dev look at

XULRunner

Signing

Use this script

Push to internal mirrors

This is done by automation for rapid release betas.

For other releases, this should be done manually at this point, after check permissions / AV scan have completed.

• Make sure the rsync excludes have been updated (Releases/BuildNotesTemplate#Edit_rsync_exclude_files)
• Force build the push to mirrors builder. Make sure at least 15 minutes have elapsed since editing the rysnc module to give it time to sync out.

Mirrors Policy

Before Release Day

Run backupsnip for release snippets

Do this the night before release day as it can take up to two hours.

Push to external mirrors

if this is a chemspill you will want to ping justdave (or other sysadmin) in #release-drivers 
and ask them to enable CDN

Release Day

Update XULRunner wiki page

For major releases or chemspills, update the links on:

• https://developer.mozilla.org/en/XULRunner
• https://developer.mozilla.org/en/Gecko_SDK

Push to Release Channel

Once there is enough uptake and we get "go" from release driver.

Update symlinks

Once we're signed off on the release channel.

Remove index.html files

If you created them earlier to hide the release.