Releases/Firefox 6.0/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

• bug 678467 - Mobile partner repacks should be triggered automatically

Build Engineers

rail - Tracking bug: bug 676083

Sync mozilla-beta to mozilla-release

Done on mv-moz2-linux-ix-slave11

• synced mozilla-beta to mozilla-release (including l10n repos) according to the documentation

L10N changesets

• Firefox: no new signoffs, copied from beta
• Fennec: no new signoffs, copied from beta

Tags

Build #	Branch, Tags	Changeset
1	MOBILE60_2011081116_RELBRANCH, FENNEC_VERSION_RELEASE, FENNEC_VERSION_BUILD1	70592ed81659
	GECKO60_2011081114_RELBRANCH, FIREFOX_VERSION_BUILD1 FIREFOX_VERSION_RELEASE	218ed8178b1e

Build data

Firefox

Build #	Type	Build ID	Build machine	Time to build
1	Linux	20110811165603	mv-moz2-linux-ix-slave08	2 hrs, 12 mins, 55 secs
	Linux64		moz2-linux64-slave09	3 hrs, 16 mins, 28 secs
	Mac		moz2-darwin10-slave52	4 hrs, 3 mins, 49 secs
	Windows		mw32-ix-slave09	2 hrs, 32 mins, 46 secs

Fennec

Build #	Type	Build ID	Build machine	Time to build
1	android	20110811165229	mv-moz2-linux-ix-slave16	1 hrs, 31 mins, 51 secs
	maemo5-gtk	20110811165229	mv-moz2-linux-ix-slave06	1 hrs, 27 mins, 12 secs
	linux	20110811172233	mv-moz2-linux-ix-slave19	1 hrs, 50 secs
	macosx	20110811165229	bm-xserve16	1 hrs, 45 mins, 23 secs
	win32	20110811165229	mw32-ix-slave10	1 hrs, 18 mins, 25 secs

Notes

used buildbot-master07

Build 1

• pushed debsign changes
• pushed synced mozconfigs
• set clobberer
• synced mozilla-beta to mozilla-release (including l10n repos) according to the documentation
• Landed a patch which enables beta channel for release builds
• reserved 10 slaves

echo "10" > master/reserved_slaves_bm07-build1

• There is no new l10n changesets available, so I copied beta l10n changesets files to the corresponding release files (submitted as a part of configs patch)
• Landed configs
• Tagged tools, buildbotcustom, buildbot-configs, mozharness with FIREFOX_6_0_BUILD1 FIREFOX_6_0_RELEASE FENNEC_6_0_BUILD1 FENNEC_6_0_RELEASE tags
• updated master

# in /builds/buildbot/build1
make update

• release sanity:

source ../bin/activate
PYTHONPATH=. ../bin/python ../tools/buildbot-helpers/release_sanity.py -u rail \
 -V 6.0 --branch mozilla-release --build-number 1 -c release-firefox-mozilla-release.py \
 --dryrun --products firefox,fennec localhost:9001

• failed:

2011-08-11 16:33:43,053 : ERROR : cannot find l10n dashboard at https://l10n-stage-sj.mozilla.org/shipping/l10n-changesets?ms=fx6.0
2011-08-11 16:33:43,053 : ERROR : Error verifying l10n dashboard changesets

• ignorable, since there is no dashboard entry for 6.0
• started automation:

source ../bin/activate
PYTHONPATH=. ../bin/python ../tools/buildbot-helpers/release_sanity.py -u rail \
 -V 6.0 --branch mozilla-release --build-number 1 -c release-firefox-mozilla-release.py \
 -b --products firefox,fennec localhost:9001

• Realized that al win32 builds were pending. There were only 3 slaves attached to bm07 and all were busy.
• moved mw32-ix-slave10 and mw32-ix-slave09 to bm07. Released when updates started.

E-mail Socorro-dev

Sent an email to socorro-dev with the body "Build IDs will go here: https://wiki.mozilla.org/Releases/Firefox_6.0/BuildNotes#Build_data"

Tag

No problems

Bouncer Submitter

No problems

Added Firefox-6.0-Partial-5.0 and Firefox-6.0-Partial-6.0b5 Bouncer products and the corresponding locations to handle manual updates.

Source

No problems.

Start autosign

Saved the following as ~/tmp/sign_6.0.sh

PRODUCT=firefox
VERSION=6.0
BUILD=1
TAG=FIREFOX_6_0_RELEASE
REPO='releases/mozilla-release'
EMAIL=release@mozilla.com
KEYDIR=d:/2010-keys
RELCONFIG=mozilla/release-firefox-mozilla-release.py

cd ${HOME}/hg-tools/
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}

First attempt failed. Blat was trying to connect to mail.mozilla.com, but it was blocked. I changed its config by editing registry "HKEYCU/Software/Public domain/Blat/SMTP server". Set to mail.build.mozilla.org.

Build

Firefox

No problems

Fennec

Android

No problems

Maemo5-GTK

No problems

Desktop Builds

No problems

Desktop repacks

No problems

XULRunner

Source

Failed because mv-moz2-linux-ix-slave17.build.mozilla.org was unable to upload files (missing xrbld key). Copied the key from another slaved, rebuilt.

Build

No problems

Signing

PRODUCT=xulrunner
VERSION=6.0
BUILD=1
TAG=FIREFOX_6_0_RELEASE
REPO="releases/mozilla-release"
EMAIL=release@mozilla.com
KEYDIR=d:/2010-keys

cd ~/hg-tools
hg pull
hg up -r ${TAG}

mkdir -p ~/signing-work/${PRODUCT}-${VERSION}
cd ~/signing-work/${PRODUCT}-${VERSION}
cp ~/hg-tools/release/signing/* .

make setup PRODUCT=${PRODUCT} VERSION=${VERSION} \
  BUILD=${BUILD} REPO=${REPO} EMAIL=${EMAIL} KEYDIR=${KEYDIR} USE_NEW=1
rsync -av -e "ssh -i /home/cltsign/.ssh/xrbld_dsa" \
  --exclude=*.txt --exclude=*-symbols.zip \
  xrbld@stage.mozilla.org:/home/ftp/pub/${PRODUCT}/nightly/${VERSION}-candidates/build${BUILD}/ \
 unsigned-build${BUILD}
rsync -av --exclude=unsigned unsigned-build${BUILD}/ \
 signed-build${BUILD}/
rsync -av unsigned-build${BUILD}/unsigned/ \
 signed-build${BUILD}/

make checksum-files create-sigs stage verify-sigs \
  PRODUCT=${PRODUCT} VERSION=${VERSION} BUILD=${BUILD} \
  REPO=${REPO} EMAIL=${EMAIL} KEYDIR=${KEYDIR} USE_NEW=1

rmdir signed-build${BUILD}/contrib{,-localized}

rsync -av -e "ssh -i /home/cltsign/.ssh/xrbld_dsa" \
  signed-build${BUILD}/ \
  xrbld@stage.mozilla.org:/home/ftp/pub/${PRODUCT}/nightly/${VERSION}-candidates/build${BUILD}/

Repacks

Firefox

No problems

Fennec

No problems

Partner Repack

Firefox

No problems

Fennec

Had to trigger builds manually. Filed bug 678467

Firefox Signing

No problems.

Android Signing

followed instructions

Android Signature Verification

Green. Need to check why r-d email was sent twice.

Updates

mozilla-releases updates

Generation

No problems

mozilla-release Update verify

no problems

5.0 -> 6.0 updates

Since most of win32 and linux users are on 5.0 (5.0.1 had mac only update path), I generated 5.0-6.0 partial updates

Generation

Used mv-moz2-linux-ix-slave17 which generated updates

cd /builds/slave/rel-m-rel-updates/build

cp patcher-configs/mozRelease-branch-patcher2.cfg patcher-configs/mozRelease-from-5.0-branch-patcher2.cfg
# patcher-configs/mozRelease-from-5.0-branch-patcher2.cfg
# removed all past-update lines
# removed all versions except 5.0 and 6.0
# s/5.0.1/5.0/g
# attached as https://bugzilla.mozilla.org/attachment.cgi?id=552629

perl patcher2.pl --download --app=firefox --brand=Firefox --config=patcher-configs/mozRelease-from-5.0-branch-patcher2.cfg
time perl patcher2.pl --create-patches --partial-patchlist-file=patchlist.cfg --app=firefox --brand=Firefox --config=patcher-configs/mozRelease-from-5.0-branch-patcher2.cfg

find temp/firefox/5.0-6.0/ftp/firefox/nightly/6.0-candidates/build1 -type f -exec chmod 644 '{}' ';'
find temp/firefox/5.0-6.0/ftp/firefox/nightly/6.0-candidates/build1 -type d -exec chmod 755 '{}' ';'

rsync -avn -e 'ssh -oIdentityFile=~/.ssh/ffxbld_dsa' '--exclude=*complete.mar' temp/firefox/5.0-6.0/ftp/firefox/nightly/6.0-candidates/build1/update ffxbld@stage-old.mozilla.org:/pub/mozilla.org/firefox/nightly/6.0-candidates/build1/

rsync -av -e 'ssh -oIdentityFile=~/.ssh/cltbld_dsa' temp/firefox/5.0-6.0/aus2.test/ cltbld@aus2-staging.mozilla.org:/opt/aus2/snippets/staging/Firefox-6.0-build1-5.0-build1-test

rsync -av -e 'ssh -oIdentityFile=~/.ssh/cltbld_dsa' temp/firefox/5.0-6.0/aus2.beta/ cltbld@aus2-staging.mozilla.org:/opt/aus2/snippets/staging/Firefox-6.0-build1-5.0-build1-beta

rsync -av -e 'ssh -oIdentityFile=~/.ssh/cltbld_dsa' temp/firefox/5.0-6.0/aus2/ cltbld@aus2-staging.mozilla.org:/opt/aus2/snippets/staging/Firefox-6.0-build1-5.0-build1

Push to the betatest channel

# cltbld@aus2-staging.mozilla.org
~/bin/backupsnip Firefox-6.0-build1-5.0-build1-test
~/bin/pushsnip Firefox-6.0-build1-5.0-build1-test

Merge with automatically generated snippets:

# cltbld@aus2-staging.mozilla.org
cd /opt/aus2/snippets/staging/
# release channel
rsync -avP Firefox-6.0-build1/ Firefox-6.0-build1-with-5.0-partials/
rsync -avP Firefox-6.0-build1-5.0-build1/ Firefox-6.0-build1-with-5.0-partials/

# beta channel
rsync -avP Firefox-6.0-build1-beta/ Firefox-6.0-build1-with-5.0-6.0b5-partials-beta/
rsync -avP Firefox-6.0-build1-5.0-build1-beta/ Firefox-6.0-build1-with-5.0-6.0b5-partials-beta/

Publish Fennec

Create bouncer entry for maemo

Added Firefox-Mobile-6.0 product with location /mobile/releases/maemo/:lang/firefox.install for maemo platform

Publish to the Android Market

IMPORTANT - Apparently it is possible for the old apk to "come back from the dead" and on this release it turned out that a second visit to the (insert expletive here) Market was necessary to re-activate the 6.0b4 apk AGAIN. So watch your back with anything to do with the Market and check it twice.
PROTIP: after publishing new apk on android marketplace, ask anyone in RelEng who has an android device to check for updates. Some delay in seeing new apk might be caused by cache-needing-to-refresh. However, a multi-hour delay in seeing new apk means there is something wrong with the settings in marketplace website. Fixing this may require going to the "upload new apk" tab, then clicking the "advanced" tab and looking at the build ids to compare to the build date you're expecting.