Releases/Firefox 18.0/BuildNotes

Build 1

Checklist

• Ship the l10n milestone ^{DESKTOP MOBILE RELEASE BETA}
• Land patches and reconfig^{DESKTOP MOBILE RELEASE BETA ESR}
• Start the automation ^{DESKTOP MOBILE RELEASE BETA ESR}
• Sign Android builds ^{MOBILE RELEASE BETA}
• Push to mirrors ^{DESKTOP RELEASE}
• Publish Fennec ^{MOBILE RELEASE BETA} NB: Push armv6 apk as well, like we do for betas
• Run pushsnip ^{DESKTOP RELEASE BETA ESR}
• Update bouncer links ^{DESKTOP BETA RELEASE}
• Update XULRunner wiki pages ^{DESKTOP RELEASE}
• Post-release tasks ^{DESKTOP RELEASE BETA ESR}
• Get the Browser Choice website updated ^{DESKTOP RELEASE}

Notes

Tracking bug 810325 release engineer kmoir

Release was submitted using release-runner

bugs hit

bug 826825 Remove mn, sw during beta-release migration for Firefox 18

A bug wasn't opened to remove the mn and sw locales for the release, so I removed them manually in the changesets submitted to the release runner. However, they still existed in https://hg.mozilla.org/releases/mozilla-release/file/3a7b66445659/browser/locales/shipped-locales so relman had to fix this and issue a new changeset to us. Once this was releasesd, bhearsum retagged our repos and I reran the tagging builds that failed.

kmoir, jhopkins: so, we all need to "force build" our "source", "build", "bouncer submitter", and "xulrunner build" builders (if you have them) because buildbot schedulers are dumb

source

build win32 macosx64 linux linux64

bouncer submitter

xulrunner win32 macosx64 linux linux64

Fennec

source

build android android-armv6

xulrunner_macosx64 had a compile error, bhearsum identfied it as a known intermittent issue and reran the build

should check the Fennec build on Monday and ensure the build ids are okay for shipping.

Because of rebuilding tag instead of re-doing sendchanges, all repacks are failing because "script_repo_revision" isn't set. These can be fixed by forcing the failed builders and setting a "script_repo_revision" property to the release tag (eg, FIREFOX_18_0_RELEASE). I've done this for all failed repacks that I've seen. (Though, some have additional problems, see below for details).

Linux repacks failed with "cannot create executable" during configure. This is because the gcc path is incorrect. The mozconfigs were updated for official betas recently for mock slaves, but we missed the esr's -release dir's:

http://hg.mozilla.org/build/buildbot-configs/rev/4f68d76200ef#l16.1

Catlee fixed this http://diff.pastebin.mozilla.org/2039996.

The android repacks were failing because bug 814191 wasn't landed. I didn't realize that this had to be landed before the beta. I landed this patch, catlee landed the buildbot configs and retagged them and restarted the failed repacks.

catlee and I landed two patches: http://hg.mozilla.org/build/buildbot-configs/rev/e8b7870b1d96 http://hg.mozilla.org/build/mozharness/rev/522935ecb3c1

catlee re-tagged buildbot-configs with:

 FENNEC_18_0_RELEASE
 FENNEC_18_0_BUILD1
 FIREFOX_18_0_RELEASE
 FIREFOX_18_0_BUILD1
   

catlee re-triggered:

Firefox 18 32/64-bit linux repacks
Fennec 18 repacks

When signing the Android builds, this message appeared

5:18:53    ERROR - Unable to download android:multi unsigned apk!
15:18:53    ERROR - Unable to download android-armv6:multi unsigned apk!
15:18:53    ERROR - Downloaded 29 of 31 unsigned apks successfully.
15:18:53     INFO - Signed 29 of 29 apks successfully.
15:18:53     INFO - Copying logs to upload dir...
15:18:53     INFO - mkdir: /home/cltsign/signing-work/release/upload/logs

Don't recall that from before, not sure if this is normal.

No, it's not, nthomas opened bug 827224