Releases/AuroraBuildNotesTemplate
Contents
- 1 Notes about this template
- 2 Notes About Releasing
- 3 Bugs hit
- 4 Build Engineers
- 5 Signed-off Revision(s)
- 6 L10N changesets
- 7 Tags
- 8 Build data
- 9 Notes
Notes about this template
This template is for the Mobile 14.0bX betas-off-aurora only. If you're looking for a build notes template for a different release, you probably want Releases/BuildNotesTemplate.
Notes About Releasing
Please update the Aurora Notes Template and the Release:Primer for future releases (bug fixes, changes to automation) as needed.
You will need to build a 14.0bX build using the fennec mozilla-aurora config files, then a new build or respin (depending on code changes) of the 13.0b2 build# android-xul build for tablets. Both will go to the market.
Bugs hit
Enter any bugs pre-existing or newly discovered and filed during the release:
- bug - description
Build Engineers
{name} - Tracking bug: bug #
Signed-off Revision(s)
L10N changesets
- 14.0bN will get Aurora changesets from this dashboard link. This link will change over time, so won't be useful for verifying later, but isn't dependent on a milestone being created per beta.
- 13.0b2 build# spin# will have an empty l10n-changesets_mobile-beta.json
Tags
Manually tag the automation code, then record the generated tags below. (details)
Build # | Branch, Tags | Changeset |
1 | MOBILE140_#_RELBRANCH, FENNEC_VERSION_RELEASE, FENNEC_VERSION_BUILD1 | # |
13.0b2 build# spin# | MOBILE130_2012050119_RELBRANCH FENNEC_13_0b2_BUILD# FENNEC_13_0b2_RELEASE | # |
Build data
Fennec
Build # | Type | Build ID | Build machine | Time to build |
1 | android | |||
android-xul | ||||
13.0b2 build # spin # | android-xul |
Notes
Build 1
Preparing to start Automation
- Set clobbers for mozilla-aurora
- Reserve slaves on bm12
- Update l10n changesets for mobile (see above)
- Land configs
- Tag buildbot-configs, buildbotcustom, & tools with build & release tags.
hg tag -f FENNEC_14_0b1_{RELEASE,BUILD1}
- update and reconfigure the master
- release-sanity
# For 14.0b1 build 1: # cltbld@bm12 cd /builds/buildbot/build1/master source ../bin/activate PYTHONPATH=. ../bin/python ../tools/buildbot-helpers/release_sanity.py -u aki -V 14.0b1 --branch mozilla-aurora --build-number 1 -c release-fennec-mozilla-aurora.py -m -l --products fennec --dryrun localhost:9001 2>&1 | tee aki.out
- start automation ← monitor progress on buildbot (e.g. aurora)
PYTHONPATH=. ../bin/python ../tools/buildbot-helpers/release_sanity.py -u aki -V 14.0b1 --branch mozilla-aurora --build-number 1 -c release-fennec-mozilla-aurora.py -m -l --products fennec localhost:9001 2>&1 | tee aki2.out
E-mail Metrics
Use the address "metrics-alerts < AT > mozilla < PERIOD > org"
# For 14.0b1 : Fennec,firefox-mobile,fennec,14.0b1,14.0
Tag
Source
Build
Fennec
Fennec repacks
Android Signing
# cltsign@signing1 cd signing-work hg --cwd mozharness pull hg --cwd mozharness up -C -r default python26 mozharness/scripts/sign_android.py --cfg signing/android_mozilla-aurora.py --platform android
email r-d
Email r-d that all native fennec builds are ready for testing
Reset reserved slaves
13.0b2 build # spin #
Preparing to start Automation
- Determine if we need to do this (we may not have to anymore)
- Set clobbers for mozilla-beta
- Reserve slave on bm13
- L10n changesets for 13.0b2 build3 spin1 will remain empty {}
- Verify that nothing has changed in 13.0b2 land since the previous spin.
IF NO CODE HAS CHANGED
If no code has changed since the previous 13.0b2 build, we can just respin the previous build:
- Create a build#-spin# directory on stage, and softlink the build# to it.
- The spin# will increment instead of the build#.
- For build3-spin2:
# ffxbld@stage cd /pub/mozilla.org/mobile/candidates/13.0b2-candidates mkdir build3-spin2 rm build3 ln -s build3-spin2 build3
- Hit "rebuild" on the latest release-mozilla-beta-android-xul_build.
- This will upload into the build#-spin# directory instead of overwriting the previous build.
IF CODE HAS CHANGED
- Land 13.0b2 configs : increment the build number.
- Create a build#-spin# directory on stage, and softlink the build# to it.
- The build# will increment, and this will be a spin 1.
- For build3-spin1:
# ffxbld@stage cd /pub/mozilla.org/mobile/candidates/13.0b2-candidates mkdir build3-spin1 ln -s build3-spin1 build3
- Tag buildbot-configs, buildbotcustom, & tools with build & release tags.
hg tag -f FENNEC_13_0b2_{RELEASE,BUILD#}
- update and reconfigure the master
- release-sanity
# For 13.0b2 build 3: # cltbld@bm13 cd /builds/buildbot/build1/master source ../bin/activate PYTHONPATH=. ../bin/python ../tools/buildbot-helpers/release_sanity.py -u aki -V 13.0b2 --branch mozilla-beta --build-number 3 -c release-fennec-mozilla-beta.py --products fennec --dryrun localhost:9001 2>&1 | tee aki.out
- start automation ← monitor progress on buildbot (e.g. beta)
PYTHONPATH=. ../bin/python ../tools/buildbot-helpers/release_sanity.py -u aki -V 13.0b2 --branch mozilla-beta --build-number 3 -c release-fennec-mozilla-beta.py --products fennec localhost:9001 2>&1 | tee aki.out
Tagging
(only runs if code has changed)
Source
(only runs if code has changed)
Build
Fennec
Android Signing
# cltsign@signing1 cd signing-work hg --cwd mozharness pull hg --cwd mozharness up -C -r default python26 mozharness/scripts/sign_android.py --config-file signing/android_mozilla-beta.py
Release Day
Publish Fennec to the Play Store (for beta releases and release releases)
Push the files (for beta releases and release releases)
- Modify this script and run it as ffxbld@stage (please push your changes prior to using it, and grab latest on stage via curl -O http://hg.mozilla.org/build/braindump/raw-file/tip/releases-related/push_fennec.sh)
- version/build number embedded in script, so always needs update!
Play Store (for beta releases and release releases)
IMPORTANT - Make sure to follow instructions!
The 14.0b# build *must* be uploaded before the 13.0b2 build!
- download 14.0b# and 13.0b2 multi apk (e.g. [1] and [2])
- visit https://market.android.com/publish
- choose "Firefox Beta" or "Firefox"
- select the "APK Files" tab and choose "Upload APK"
- choose the 14.0b# 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 the versionCode is the build date (almost anyway, the market reports an hour later than our buildID)
- hit "Save"
- choose the 14.0b# multi apk that you downloaded and hit "upload"
- Repeat with the 13.0b2 multi apk
- when it finishes uploading, verify the versionCode is larger than the 14.0b# versionCode.
- activate new 14.0b# and 13.0b2 apks (You should see an Error message since both apk's are active)
- deactivate old apks (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"