Notes About Releasing

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

Bugs hit

Build Engineers

bhearsum - Tracking bug: bug 719216

Signed-off Revision(s)

Build 1: acddb6b6a01c

L10N changesets

Doesn't exist.

Tags

Build data

Firefox

Notes

Build 1

Preparing to start Automation

• No clobber necessary because this is the first release on the branch
• Didn't adjust reserved slaves because it was still set to 10 from the 10.0 release, which was more or less done.
• Pushed the default branch of mozilla-release to mozilla-esr10
• Landed the wordmark update on the ESR repo: https://bugzilla.mozilla.org/attachment.cgi?id=591983&action=edit
• Copied l10n-changesets_mozilla-release to l10n-changesets_mozilla-esr10
• Landed release config update & l10n-changesets patch
• Tag buildbot-configs, buildbotcustom, & tools with build & release tags
• update and reconfigure the master
• start automation:

# Dry-run
source ../bin/activate
PYTHONPATH=. ../bin/python ../tools/buildbot-helpers/release_sanity.py -u bhearsum -V 10.0esr --branch mozilla-esr10 --build-number 1 -c release-firefox-mozilla-esr10.py --dryrun --products firefox localhost:9001
# Failed because it claimed mozconfigs were missing (it was looking in the buildbot-configs repo instead of the source one), and also because the l10n dashboard check failed (because we have no milestone for esr)
PYTHONPATH=. ../bin/python ../tools/buildbot-helpers/release_sanity.py -u bhearsum -V 10.0esr --branch mozilla-esr10 --build-number 1 -c release-firefox-mozilla-esr10.py --bypasscheck --products firefox localhost:9001

E-mail Metrics

Sent the following mail to metrics-alerts@mozilla.org:

Firefox,firefox,firefox,10.0esr,10.0

NOTE: metrics e-mailed me later to say that the last part of this line should always be '10.0esr', until we have a new ESR - because it represents the "major" version associated with the specific minor version. So, the mail for 10.0.1esr should be: Firefox,firefox,firefox,10.0esr,10.0esr

Tag

No problems.

Bouncer Submitter

No problems.

Source

No problems.

Start autosign

NOTE: use new signcode keys from d:/2011-keys

Ran the following on keymaster:

PRODUCT=firefox
VERSION=10.0esr
BUILD=1
TAG=FIREFOX_10_0esr_RELEASE
REPO='releases/mozilla-esr10'
EMAIL=release@mozilla.com
KEYDIR=d:/2011-keys
RELCONFIG=mozilla/release-firefox-mozilla-esr10.py
cd ${HOME}/hg-tools/ # if it exists, otherwise create a fresh clone
hg pull && hg up -r ${TAG}
mkdir -p ~/signing-work/${PRODUCT}-${VERSION}/lib/python
cd ~/signing-work/${PRODUCT}-${VERSION}
cp ~/hg-tools/release/signing/* .
rsync -av ~/hg-tools/lib/python/ ./lib/python/
make autosign PRODUCT=${PRODUCT} VERSION=${VERSION} BUILD=${BUILD} REPO=${REPO} EMAIL=${EMAIL} KEYDIR=${KEYDIR} RELCONFIG=${RELCONFIG}

Build

Firefox

Firefox repacks

• Linux repack 5/6 failed due to an hg timeout.
  • Used "rebuild" to retrigger it.

No further problems

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

Firefox Signing

No problems with signing, got "signature verification succeeded" mail.

Reset reserved slaves

This is also a good time to QUIT SIGNCODE on keymaster if you've still got it running.

Check permissions / AV scan

• Triggered with "force build"
• No permissions or virus problems.

Push files to internal mirrors

• First time only addition to stage:/pub/mozilla.org/zz/rsyncd-mozilla-releases.exclude of

- firefox/releases/*esr*

• Triggered with "force build".

Final verification