Releases/Firefox 9.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 701054

Signed-off Revision(s)

Build 1:

L10N changesets

Instructions on how to get them

• Firefox: link, removed csb, mn, sw per bug 710420
• Fennec: link

Tags

Build #	Branch, Tags	Changeset
	MOBILE80_#_RELBRANCH, FENNEC_VERSION_RELEASE, FENNEC_VERSION_BUILD1	#
	GECKO80_#_RELBRANCH, FIREFOX_VERSION_BUILD1 FIREFOX_VERSION_RELEASE	#

Build data

Firefox

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

Fennec

Build #	Type	Build ID	Build machine	Time to build
1	android
	linux
	macosx
	win32

Notes

Build 1

Syncing repos

• reserved linux64-ix-slave15 for this task
• mozilla-beta -> mozilla-release was done by Christian Legnitto (as well as updating browser/locales/shipped_locales to eliminate non-release locales that were in beta releases mn,sw,csb)
• Did l10n repo sync on reserved linux64-ix-slave15 as per instructions
• It took 27m13.876s

Diff mozconfigs

If this is a *.0 beta -> release

Preparing to start Automation

• Set clobbers for the appropriate masters.
• Reserve slaves

echo "10" > reserved_slaves_bm07-build1

• Had to land new android mozconfigs (default and production) ahead of time to get a green build on mozilla-release
• HERE
• Update l10n changesets for desktop, mobile
• 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
• update and reconfigure the master
• start automation

source ../bin/activate
PYTHONPATH=. ../bin/python ../tools/buildbot-helpers/release_sanity.py -u rail \
 -V 9.0 --branch mozilla-release --build-number 1 -c release-firefox-mozilla-release.py \
 -c release-fennec-mozilla-release.py --dryrun --products firefox,fennec localhost:9001

• it failed trying to fetch l10n dashboard (9.0 vs 9). TODO: file a bug
• Start automation:

PYTHONPATH=. ../bin/python ../tools/buildbot-helpers/release_sanity.py -u rail \
 -V 9.0 --branch mozilla-release --build-number 1 -c release-firefox-mozilla-release.py \
 -c release-fennec-mozilla-release.py -b --products firefox,fennec localhost:9001

E-mail Metrics

And for 9.0 final it's

Firefox,firefox,firefox,9.0,9.0
Fennec,firefox-mobile,fennec,9.0,9.0

E-mail mirrors@mozilla.org

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

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 9.0 and 3.6.25 coming to mirrors Dec 19
Body:
Hi,

We're planning on pushing our Firefox 9.0 and 3.6.25 releases to mirrors sometime next Monday, December 19.

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.

Tag

No problems.

Bouncer Submitter

No problems.

Source

No problems.

Start autosign

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

# created in ~/tmp/sign_9.0.sh
PRODUCT=firefox
VERSION=9.0
BUILD=1
TAG=FIREFOX_9_0_RELEASE
REPO='releases/mozilla-release'
EMAIL=release@mozilla.com
KEYDIR=d:/2011-keys
RELCONFIG=mozilla/release-firefox-mozilla-release.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 CombinedSigning

Build

Firefox

No problems

Firefox repacks

No problems

Fennec

Android

No problems

Desktop Builds

No problems

Mobile Desktop repacks

(aki): win32-mobile repacks died on a unicode env var. Catlee noted this is because json loads a unicode string; simplejson loads a string.

I backed out http://hg.mozilla.org/build/buildbot-configs/rev/1d21e762cca7; if we re-tag and rerun the repacks, it should work.

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

Source

No problems

Build

No problems

Signing

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

Partner Repack

Firefox

No problems

Fennec

N/A

Android Signing

Instructions in [MobileSigning https://intranet.mozilla.org/Build:MobileSigning]

NOTE: It can be started in a different Windows without having to wait for Firefox signing to finish.

Used this script

Android Signature Verification

No problems

Major Update

N/A

Push files to internal mirrors

Mirrors Policy

Publish Fennec to the Android Market

Push the files

• as ffxbld@stage...

Android Market

IMPORTANT - Make sure to follow instructions!

• download multi apk (e.g. multi/fennec-9.0.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 build date
  • 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}/releasenotes/
  • and hit "Save"

Update symlinks

Once we're signed off on the release channel.