Releases/Firefox 3.6.27/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:

• bug 727740 - mozconfig comparison assumes in-tree mozconfigs since bug 697611
• bug 727751 - xulrunner source failure on 1.9.2

Build Engineers

nthomas - Tracking bug: bug 727630

Signed-off Revision(s)

Build 1: fd6d19a5ae84

L10N changesets

Left unchanged from 3.6.26

Tags

Build #	Branch, Tags	Changeset
1	GECKO19227_2012021601_RELBRANCH, FIREFOX_3_6_27_BUILD1 FIREFOX_3_6_27_RELEASE	73ffd608342e

Build data

Firefox

Build #	Type	Build ID	Build machine	Time to build
1	Linux	20120216013254	mv-moz2-linux-ix-slave05	37 mins, 31 secs
	Linux64
	Mac
	Windows

Notes

Build 1

Preparing to start Automation

• Set clobbers for "any master", "mozilla-1.9.2", "any builder"
• Reserve slaves
• Update l10n changesets for desktop, mobile No l10n changes for a chemspill
• Landed automation configs
• Tagged buildbot-configs, buildbotcustom, & tools with build & release tags
• update and reconfigure the master
• start automation

cd /builds/buildbot/build1/master
source ../bin/activate
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u nthomas -p firefox -V 3.6.27 --branch  mozilla-1.9.2 --build-number 1 -c release-firefox-mozilla-1.9.2.py --dryrun localhost:9001

This failed because bug 697611 assumes that there is a mozconfigs dict defined in the release config, filed bug 727740. Worked around by cloning tools to ~cltbld/tools and updating to FIREFOX_3_6_26_RELEASE. Retry:

PYTHONPATH=. python ~/tools/buildbot-helpers/release_sanity.py -u nthomas -p firefox -V 3.6.27 --branch  mozilla-1.9.2 --build-number 1 -c release-firefox-mozilla-1.9.2.py --dryrun localhost:9001
...
2012-02-16 00:48:00,842 : INFO : Comparing l10n changesets on dashboard https://l10n-stage-sj.mozilla.org/shipping/l10n-changesets?ms=fx3.6.27 to on-disk l10n-changesets_mozilla-1.9.2 ...
2012-02-16 00:48:01,977 : ERROR : cannot find l10n dashboard at https://l10n-stage-sj.mozilla.org/shipping/l10n-changesets?ms=fx3.6.27
2012-02-16 00:48:01,977 : ERROR : Error verifying l10n dashboard changesets

The real thing

PYTHONPATH=. python ~/tools/buildbot-helpers/release_sanity.py -u nthomas -p firefox -V 3.6.27 --branch  mozilla-1.9.2 --build-number 1 -c release-firefox-mozilla-1.9.2.py localhost:9001 -b

E-mail Metrics

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

Firefox,firefox,firefox,3.6.27,3.6
Firefox,firefox,firefox,3.6.28pre,3.6

E-mail mirrors@mozilla.org

Combined message with 10.0.2 sent.

Tag

No problems

Bouncer Submitter

No problems

Source

No problems

Start autosign

PRODUCT=firefox
VERSION=3.6.27
BUILD=1
TAG=FIREFOX_3_6_27_RELEASE
REPO='releases/mozilla-1.9.2'
EMAIL=release@mozilla.com
KEYDIR=d:/2011-keys
RELCONFIG=mozilla/release-firefox-mozilla-1.9.2.py

cd ${HOME}/hg-tools/ # if it exists, otherwise create a fresh clone
hg pull && hg up -r ${TAG}

mkdir -p ~/signing-work/${PRODUCT}-${VERSION}/lib/python
cd ~/signing-work/${PRODUCT}-${VERSION}
cp ~/hg-tools/release/signing/* .
rsync -av ~/hg-tools/lib/python/ ./lib/python/
make autosign PRODUCT=${PRODUCT} VERSION=${VERSION} BUILD=${BUILD} REPO=${REPO} EMAIL=${EMAIL} KEYDIR=${KEYDIR} RELCONFIG=${RELCONFIG}

Build

Firefox

linux32 ok

Firefox repacks

linux32 ok

Fennec

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

Failed

mv mozilla-1.9.2/obj-firefox/dist/source/xulrunner-3.6.27.source.tar.bz2 source/xulrunner-3.6.27.source.tar.bz2
mv: cannot stat `mozilla-1.9.2/obj-firefox/dist/source/xulrunner-3.6.27.source.tar.bz2': No such file or directory

Filed bug 727751.

Manual fix:

# cltbld@moz2-linux-slave36
cd /builds/slave/rel-m-192-xr-source/
mv mozilla-1.9.2/obj-firefox/dist/source/xulrunner-1.9.2.27.source.tar.bz2 source/xulrunner-3.6.27.source.tar.bz2
export POST_UPLOAD_CMD='post_upload.py -p xulrunner -v 3.6.27 -n 1 -c'
export UPLOAD_HOST=stage.mozilla.org
export UPLOAD_SSH_KEY=~/.ssh/xrbld_dsa
export UPLOAD_TO_TEMP=1
export UPLOAD_USER=xrbld
python /builds/slave/rel-m-192-xr-source/tools/buildfarm/utils/retry.py -s 1 -r 5 -t 1260 python mozilla-1.9.2/build/upload.py --base-path . source/xulrunner-3.6.27.bundle source/xulrunner-3.6.27.source.tar.bz2

Build

linux32 + win32 ok

Signing

NOTE: use new signcode keys from d:/2011-keys and QUIT SIGNCODE when you're done with keymaster

Follow instructions in XULRunner Signing (aut required).

Partner Repack

N/A

Android Signing

N/A

Major Update

Major update generation is not kicked off automatically. You should only create them once the final builds for the "latest" build are ready. For instance, the 3.6.26 builds got created a week before the 10.0 release but the "final" 10.0 builds were not created after few days.

Follow instructions from the Major update documentation.

Reset reserved slaves

This is also a good time to QUIT SIGNCODE on keymaster if you've still got it running.

Check permissions / AV scan

It is supposed to be triggered automatically after updates are done. File a bug if it doesn't.

Going to Beta

Run backupsnip

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

Before 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

Push to external mirrors

if this is a chemspill you will want to ping justdave (or other sysadmin) in #release-drivers 
and ask them to enable CDN

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"

Update XULRunner wiki page

For major releases or chemspills, update the links on:

• https://developer.mozilla.org/en/XULRunner
• https://developer.mozilla.org/en/Gecko_SDK

Also for older releases:

• https://developer.mozilla.org/en/XULRunner_1.9.2_Release_Notes
• https://developer.mozilla.org/en/Gecko_SDK

Push to Release Channel

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

Update symlinks

Once we're signed off on the release channel.

Remove index.html files

If you created them earlier to hide the release.