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

  • Fennec was en-US only, needed to tweak config.py and use an empty l10n json file ({})
  • had troubles pushing to hg over ssh
  • release sanity
  • bug 723308 - update release sanity whitelists

Build Engineers

rail - Tracking bug: bug 718777

Signed-off Revision(s)

Build 1:

L10N changesets

Instructions on how to get them

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

N/A

Diff mozconfigs

If this is a *.1 beta -> release

Preparing to start Automation

  • Set clobbers for the appropriate masters
  • Reserve slaves
 echo "10" > master/reserved_slaves_bm08-build1
  • 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
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u rail -pfirefox,fennec \
  -V 11.0b1 --branch mozilla-beta --build-number 1 -c release-firefox-mozilla-beta.py -c release-fennec-mozilla-beta.py \
  --dryrun  localhost:9001 2>&1 | tee rail.out
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u rail -pfirefox,fennec \
 -V 11.0b1 --branch mozilla-beta --build-number 1 -c release-firefox-mozilla-beta.py -c release-fennec-mozilla-beta.py \
 -b  localhost:9001 2>&1 | tee rail.out

E-mail Metrics

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

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

E-mail mirrors@mozilla.org

N/A

Tag

No problems

Bouncer Submitter

No problems

Source

Start autosign

N/A

Build

Firefox

Firefox repacks

Fennec

Android
Desktop Builds

n/a

Mobile Desktop repacks

n/a

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

used this script

Partner Repack

Firefox

Fennec

Firefox Signing

Android Signing

Instructions in MobileSigning

Landed this patch

As cltsign@signing1:

cd ~/signing-work/
hg clone http://hg.mozilla.org/build/mozharness/
python2.6 mozharness/scripts/sign_android.py --config-file signing/android_mozilla-beta.py

Android Signature Verification

No problems

L10N verify

Updates

Update verify

Major Update

n/a

Update verify

Reset reserved slaves

GOING TO BETA

Run backupsnip

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

Push to beta

PRE-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 files to internal mirrors

Done the day before release OR ASAP for chemspills: Mirrors Policy

Final verification

Push index file to mirrors

n/a

Push to external mirrors

n/a

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"

Push XULRunner to Mirrors

Update XULRunner wiki page

n/a

Push to Release Channel

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

Update symlinks

n/a

Remove index.html files

n/a

Update browser choice website

n/a