Checklist

• Ship the l10n milestone
• Set reserved_slaves
• Check to make sure you have all of the different types of slaves that you need
• Start the automation
• E-mail Metrics
• Sign Android builds
• Reset reserved_slaves
• Publish Fennec
• Run pushsnip

Notes

Build 1

Starting the Release

• Attempted to create l10n milestones for Firefox and Fennec, only got the Firefox one. Axel fixed it up by hand.
• Set reserved_slaves:

cd /builds/buildbot/build1
echo 8 > master/reserved_slaves

• Made sure had enough slaves to do the release.
  • 5 lion, 6 win32, plenty of linux - no need to do any additional locking
• Created the candidates directory:

# ffxbld@stage
version=14.0b10
product=firefox
cd /pub/mozilla.org/$product/nightly/
mkdir ../candidates/$version-candidates
ln -s ../candidates/$version-candidates $version-candidates

• Landed l10n-changesets and release config updates
• Tagged buildbot-configs, buildbotcustom, tools with {FIREFOX,FENNEC}_14_0b10_{RELEASE,BUILD1}
• Updated and reconfiged buildbot-master13
• Ran release sanity:

cd /builds/buildbot/build1/master
source ../bin/activate
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u bhearsum -V 14.0b10 --branch mozilla-beta --build-number 1 \
    --release-config release-firefox-mozilla-beta.py --release-config release-fennec-mozilla-beta.py --products firefox,fennec  \
    --dryrun localhost:9001

• No issues discovered by release sanity, so I started the release:

PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u bhearsum -V 14.0b10 --branch mozilla-beta --build-number 1     --release-config release-firefox-mozilla-beta.py --release-config release-fennec-mozilla-beta.py --products firefox,fennec  localhost:9001

E-mailed Metrics

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

Firefox,firefox,firefox,14.0b10,14.0
Fennec,firefox-mobile,fennec,14.0b10,14.0

Sign Android Builds

As cltsign@signing1:

cd ~/signing-work/mozharness
hg pull -u && hg up -C
python2.6 ~/signing-work/mozharness/scripts/sign_android.py --config-file signing/android_mozilla-beta.py --platform android

Failures during AV scan

The AV scan showed up red because the following files showed a 'CL_EFORMAT: Bad format or broken data ERROR' error:

 /pub/mozilla.org/firefox/nightly/14.0b10-candidates/build1/update/linux-x86_64/pt-PT/firefox-14.0b10.complete.mar
 /pub/mozilla.org/firefox/nightly/14.0b10-candidates/build1/linux-i686/en-ZA/firefox-14.0b10.tar.bz2
 /pub/mozilla.org/firefox/nightly/14.0b10-candidates/build1/win32/ta-LK/Firefox Setup 14.0b10.exe
 /pub/mozilla.org/firefox/nightly/14.0b10-candidates/build1/win32/cy/Firefox Setup 14.0b10.exe

This launchpad bug suggested that updating the virus definitions should fix it. I asked dumitru to do that and re-ran clamdscan by hand after it had finished. Even after that the same error kept coming back. nthomas found that the ClamAV on upload-cron was able to scan these files fine, so he did so and they passed. Nothing to worry about here, given that.

Hit Force Build on the master for release-mozilla-beta-push_to_mirrors after QA asked about lack of notification about releasetest being available.

Reset reserved_slaves

cd /builds/buildbot/build1/master
echo 0 > reserved_slaves

Publish to Beta Channel

As ffxbld@aus3-staging.mozilla.org:

cd /opt/aus2/snippets/staging
~/bin/pushsnip Firefox-14.0b10-build1

Build 2 (Fennec only)

Build2 happened because I screwed up the l10n changesets by not including the multilocale portion. To fix:

• Pinged Axel, who pointed me at: https://l10n.mozilla.org/shipping/json-changesets?ms=fennec14_beta_b10&platforms=android&multi_android-multilocale_repo=releases%2Fmozilla-beta&multi_android-multilocale_rev=default&multi_android-multilocale_path=mobile%2Fandroid%2Flocales%2Fmaemo-locales - which had the correct l10n changesets

Starting the Automation

• Landed correct l10n-changesets and bumped buildNumber to 2 for Fennec.
• Tagged buildbot-configs, buildbotcustom, tools with FENNEC_14_0b10_{RELEASE,BUILD2}
• Updated and reconfiged buildbot-master13
• Ran release sanity:

cd /builds/buildbot/build1/master
source ../bin/activate
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u bhearsum -V 14.0b10 --branch mozilla-beta --build-number 2 \
    --release-config release-fennec-mozilla-beta.py --products fennec  \
    --dryrun localhost:9001

• No issues discovered by release sanity, so I started the release:

PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u bhearsum -V 14.0b10 --branch mozilla-beta --build-number 2 \

   --release-config release-fennec-mozilla-beta.py --products fennec  \
   localhost:9001

Sign Android Builds

As cltsign@signing1:

cd ~/signing-work/mozharness
hg pull -u && hg up -C
python2.6 ~/signing-work/mozharness/scripts/sign_android.py --config-file signing/android_mozilla-beta.py --platform android

Publish Fennec

• Updated push_fennec.sh as ffxbld@stage and ran it.
• Uploaded APK to Google Play store and activated it.

Bugs Hit

• bug 769215 - update the l10n milestone documentation to include creation/renaming
• bug 769328 - rename maemo-locales to multi-locales or something else more intuitive