Releases/Fennec 14.0b8/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:

Build Engineers

{aki} - Tracking bug: bug 767050

Signed-off Revision(s)

• Build 2: f54b2bbd3baf
• Build 3: #

L10N changesets

Instructions on how to get them

• Fennec: link to the json

Tags

Manually tag the automation code, then record the generated tags below. (details)

Build #	Branch, Tags	Changeset
2	14_0_Beta, FENNEC_14_0b8_RELEASE, FENNEC_14_0b8_BUILD2	f54b2bbd3baf
3	MOBILE80_#_RELBRANCH, FENNEC_VERSION_RELEASE, FENNEC_VERSION_BUILD3	#

Build data

Fennec

Build #	Type	Build ID	Build machine	Time to build
2	android
	android-xul
3	android
	android-xul

Notes

Build 2

Did you ship the L10n milestone & get l10n-changesets

Yes.

Axel created a fennec14_beta_b8.2 milestone; I shipped that.

Set reserved slaves

5

Preparing to start Automation

• Blassey created the 14_0_Beta relbranch off the MOBILE140_2012061216_RELBRANCH, since MOBILE140_2012061216_RELBRANCH is branded for official (release). The 14_0_Beta relbranch was created off the changeset previous to changing branding.
• Axel created the fennec14_beta_b8.2 l10n milestone; we could do the same through the milestone creation page.
• Got signoff/go from Axel + Alex.
• Landed config files: default production including the shipped l10n changesets.
• Tagged buildbot-configs, buildbotcustom, tools
• updated+reconfiged bm13
• Ran release sanity:

PYTHONPATH=. ../bin/python ../tools/buildbot-helpers/release_sanity.py -u aki -V 14.0b8 --branch mozilla-beta --build-number 2 \
-c release-fennec-mozilla-beta.py --products fennec --l10n-dashboard-version 14_beta_b8.2 --dryrun localhost:9001 2>&1 | tee aki.out

• Re-ran without dryrun.

Tag

• I was slightly worried about the relbranch only existing on mozilla-beta, but encountered no problems.

Source

No problems.

Build

Fennec

No problems.

Fennec repacks

No problems.

Android Signing

# cltsign@signing1
cd signing-work/
hg --cwd mozharness/ pull
hg --cwd mozharness/ up -C
python2.6 ~/signing-work/mozharness/scripts/sign_android.py --config-file signing/android_mozilla-beta.py --platform android

Reset reserved slaves

0

Release Day

Publish Fennec to the Play Store (for beta releases and release releases)

Push the files (for beta releases and release releases)

Did so via push_fennec.sh.

Play Store (for beta releases and release releases)

Alex did this.

Build 3

Due to bug 762098 ; we need a new l10n milestone after ja-JP signoff.

DONE TO HERE

Did you ship the L10n milestone & get l10n-changesets

https://wiki.mozilla.org/Release:Release_Automation_on_Mercurial:Starting_a_Release#L10N_Changesets

• Aki created a fennec14_beta_b8.3 milestone.

Set reserved slaves

https://wiki.mozilla.org/Release:Release_Automation_on_Mercurial:Starting_a_Release#Setting_reserved_slaves

Preparing to start Automation

https://wiki.mozilla.org/Release:Release_Automation_on_Mercurial:Starting_a_Release#Starting_the_automation

Android Signing

https://wiki.mozilla.org/Release:Release_Automation_on_Mercurial:Tagging_through_Signing#Android

Reset reserved slaves

https://wiki.mozilla.org/Release:Release_Automation_on_Mercurial:Tagging_through_Signing#Reset_reserved_slaves

Release Day

Publish Fennec to the Play Store (for beta releases and release releases)

Push the files (for beta releases and release releases)

https://wiki.mozilla.org/Release:Release_Automation_on_Mercurial:Updates_through_Shipping#Push_the_files

Play Store (for beta releases and release releases)

https://wiki.mozilla.org/Release:Release_Automation_on_Mercurial:Updates_through_Shipping#Play_Store