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

lsblakk - Tracking bug: bug 695722

Signed-off Revision(s)

Build 1: 04778346a3b0

L10N changesets

Instructions on how to get them

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

Tags

Build #	Branch, Tags	Changeset
	MOBILE70_#_RELBRANCH, FENNEC_VERSION_RELEASE, FENNEC_VERSION_BUILD1	#
	GECKO70_#_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

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 linux-ix-slave02 as per instructions

Diff mozconfigs

If this is a *.0 beta -> release added to the mozconfig_whitelist for PGO differences in release configs that are known and intentional diff

Preparing to start Automation

• Set clobber for 'any master', 'mozilla-release', 'any builder'
• reserved 10 slaves

echo "10" > master/reserved_slaves_bm07-build1

• Landed automation configs & l10n updates
• Tagged buildbot-configs (production), buildbotcustom (production-0.8), tools (default) with build & release tags

hg tag -f FIREFOX_8_0_BUILD1 FIREFOX_8_0_RELEASE FENNEC_8_0_BUILD1 FENNEC_8_0_RELEASE

• release_sanity dry run

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

dry-run failed verify_l10n_dashboard because the url for the dashboard was https://l10n-stage-sj.mozilla.org/shipping/l10n-changesets?ms=fx8 and the release_sanity looks for https://l10n-stage-sj.mozilla.org/shipping/l10n-changesets?ms=fx8.0

• release_sanity -real-real with -b to bypass the dashboard check

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

• start automation
• not reconfiguring other masters, it's EOD Pacific time on a Friday, sent an email to release@mozilla.com to notify for Monday morning
• returned linux-ix-slave02 to the pool now that l10n repos are synched

E-mail Metrics

Only for beta1 and 1.9.2 releases

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 {VERSION} coming to mirrors tomorrow
Body:
We're planning on pushing our Firefox {VERSION} release to mirrors sometime over 
the next 24 hours in time.
# 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.

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

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

Publish Fennec

Push the files

(only for < 8.0b*) TODO: review as we are going to ask release-drivers about this step

Publish to the Android Market

IMPORTANT - Make sure to follow instructions!

• download multi apk (e.g. multi/fennec-8.0b4.multi.eabi-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}beta/releasenotes/

• • and hit "Save"

Update symlinks

Once we're signed off on the release channel.

Remove index.html files

If you created them earlier to hide the release.