Releases/Firefox 11.0b6/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

John Ford, Hal Wine - Tracking bug: bug #

Signed-off Revision(s)

Build 1: #

L10N changesets

Instructions on how to get them

• Firefox: link to the l10n-changesets
• Fennec: link to the json

Tags

Build #	Branch, Tags	Changeset
	MOBILE110_2012030517_RELBRANCH, FENNEC_11_0b6_BUILD1 FENNEC_11_0b6_RELEASE	377c06cd1151
	GECKO110_2012030517_RELBRANCH, FIREFOX_11_0b6_BUILD1 FIREFOX_11_0b6_RELEASE	d1f6bc5e555a

Build data

Firefox

Build #	Type	Build ID	Build machine	Time to build
1	Linux		mv-moz2-linux-ix-slave10	1 hrs, 6 mins, 54 secs
	Linux64		moz2-linux64-slave06	4 hrs, 5 mins, 9 secs
	Mac		moz2-darwin10-slave41	3 hrs, 14 mins, 32 secs
	Windows		mw32-ix-slave03	3 hrs, 27 mins, 46 secs

Fennec

Build #	Type	Build ID	Build machine	Time to build
1	android-xul	mv-moz2-linux-ix-slave08	51 mins, 45 secs

Notes

Build 1

Syncing repos

(eg: mozilla-beta -> mozilla-release for new Firefox releases)

Diff mozconfigs

If this is a *.0 beta -> release. May also need to update the whitelist of nightly vs release differences for release sanity.

Preparing to start Automation

• Set clobbers for any master, any branch and any builder
• Reserve slaves
• 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.0b6-candidates
ln -s ../candidates/11.0b6-candidates 11.0b6-candidates

• Update l10n changesets for desktop, mobile
  • firefox: [1]
  • fennec: [2]
• 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

hg tag -f FIREFOX_11_0b6_RELEASE FIREFOX_11_0b6_BUILD1 FENNEC_11_0b6_RELEASE FENNEC_11_0b6_BUILD1 -r 06aec21cda52

• update and reconfigure the master
• start automation

cd /builds/buildbot/build1/master
source ../bin/activate
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u jhford \
 -pfirefox,fennec -V 11.0b6 --branch mozilla-beta --build-number 1 \
 -c release-firefox-mozilla-beta.py -c release-fennec-mozilla-beta.py \
 --dryrun localhost:9001

PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u jhford  -pfirefox,fennec -V 11.0b6 --branch mozilla-beta --build-number 1  -c release-firefox-mozilla-beta.py -c release-fennec-mozilla-beta.py  localhost:9001

E-mail Metrics

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

For 9.0b2 it would be

Firefox,firefox,firefox,11.0b6,11.0
Fennec,firefox-mobile,fennec,11.0b6,11.0

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.

Start autosign

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

PRODUCT=firefox
VERSION=11.0b6
BUILD=1
TAG=FIREFOX_11_0b6_RELEASE
REPO='releases/mozilla-beta'
EMAIL=release@mozilla.com
KEYDIR=d:/2011-keys
RELCONFIG=mozilla/release-firefox-mozilla-beta.py

cd ${HOME}/hg-tools/
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}

Instructions are in Signing

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

NOTE: use new signcode keys from d:/2011-keys and QUIT SIGNCODE when you're done with keymaster

Follow instructions in XULRunner Signing (aut required).

Android Signing

Instructions in MobileSigning

Now run on signing1.

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

It is supposed to be triggered automatically after updates are done. File a bug if it doesn't.

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

Going to Beta

Run backupsnip

NOTE: Remember to do this at least an hour ahead of the expected "go to beta" email.

Before Release Day

Assuming this is not a chemspill.

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

Publish Fennec to the Android Market

Push the files

• Use this script and run it as ffxbld@stage (please push you changes prior to using it)

Android Market

IMPORTANT - Make sure to follow instructions!

• download multi apk (e.g. multi/fennec-10.0b6.multi.android-arm.apk)
• visit https://market.android.com/publish
• choose "Firefox Beta" or "Firefox"
• select the "APK Files" tab and choose "Upload APK"
  • choose the multi apk that you downloaded and hit "upload"
    • NOTE: the progress bar does not seem to show progress (at least on Google Chrome)
  • when it finishes uploading, verify VersionCode is the build date (almost anyway, the market reports an hour later than our buildID)
  • hit "Save"
• activate new apk (You should see an Error message since both apk's are active)
• deactivate old apk (You should not see the Error message anymore)
• hit "Save"
• If this is a beta 1, go to "Product Details" tab -> Recent Changes, change the url to http://www.mozilla.com/en-US/mobile/{VERSION}beta/releasenotes/
  • and hit "Save"

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

Also for older releases:

• https://developer.mozilla.org/en/XULRunner_1.9.2_Release_Notes
• 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.