Notes About Releasing

Please update the Release:Primer for future releases (bug fixes, changes to automation) as needed

Bugs hit

Also check the "known issues" page.

Build Engineers

jhford - bug 664213

Signed-off Revision(s)

Build 1: f1acd88f828e

L10N changesets

used the beta 6 changesets

Tags

Build #	Tag	Changeset
1	GECKO50_2011061416_RELBRANCH	3fb6ad7c725e
	FIREFOX_5_0b7_RELEASE FIREFOX_5_0b7_BUILD1	3fb6ad7c725e

Build data

Build #	Type	Build ID	Build machine	Time to build
1	Linux	20110614174314	mv-moz2-linux-ix-slave10	???
	Linux64		moz2-linux64-slave02	???
	Mac		moz2-darwin10-slave48	???
	Windows		mw32-ix-slave17	???

Notes

Build 1

Setup

• Marked "Any master", "mozilla-beta", "Any builder" for a clobber
• there were still 6 reserved slaves from beta5
• Hit "ship it" button on "Firefox 5 Beta Build 6"</i> (https://l10n-stage-sj.mozilla.org/shipping/milestones)
• Landed configs, merged configs & custom to production.
• Tagged buildbot-configs, buildbotcustom, and tools with FIREFOX_5_0b7_RELEASE and FIREFOX_5_0b7_BUILD1
• Update pm03 checkouts & reconfigured
• Ran release_sanity dry run with

PYTHONPATH=.:tools/lib/python/ python tools/buildbot-helpers/release_sanity.py -u jhford -V 5.0b7 --branch mozilla-beta --build-number 1 -c release-firefox-mozilla-beta.py --dryrun localhost:9010

which had an error due to the milestone not being created in the l10n dashboard.

• And then to start the release:

PYTHONPATH=.:tools/lib/python/ python tools/buildbot-helpers/release_sanity.py -u jhford -V 5.0b7 --branch mozilla-beta --build-number 1 -c release-firefox-mozilla-beta.py localhost:9010 -b 

NOTE THE -b IS BECAUSE OF l10n Dashboard issue

Tag

Worked as expected

Bouncer Submitter

No problmes

Start Autosign

Once mozilla-beta was tagged, on keymaster, started signcodepwd.exe, opened a cygwin terminal and ran the following:

PRODUCT=firefox
VERSION=5.0b7
BUILD=1
TAG=FIREFOX_5_0b7_RELEASE
REPO='releases/mozilla-beta'
EMAIL=release@mozilla.com
KEYDIR=d:/2010-keys
RELCONFIG=mozilla/release-firefox-mozilla-beta.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}

Source

No problems

Build/Repack

No problems

Signing

No problems, received "signature verification succeeded" mail.

L10n Verify

All green, no string changes.

Update Generation (5.0b[1-6] -> 5.0b7)

No problems

Update Verify

No problems, all green. Spot checked 2 logs for each platform in detail, no differences in any of them.

Permissions check & AV

No problems or viruses found.

Push files

Like past Betas, this is only going to internal mirrors, so we add the following line to stage:/pub/mozilla.org/zz/rsyncd-mozilla-releases.exclude:

- firefox/releases/5.0b7

After waiting a few minutes to make sure this file was synced to the rsync server, forced the "release-mozilla-beta-push_to_mirrors" with the following properties:

release_config: mozilla/release-firefox-mozilla-beta.py
script_repo_revision: FIREFOX_5_0b7_RELEASE

Update Generation (4.0 -> 5.0)

Landed patcher config and update verify config bumps.

Retagged new update verify config revision with FIREFOX_4_0_1_{BUILD1,RELEASE}_RUNTIME. No need to retag buildbot-configs because we didn't bump them.

Did work on mv-moz2-linux-ix-slave13.build.mozilla.org as it was already set up for update generation

cd /builds/slave/rel-beta-updates/build/patcher-configs
cvs up
cd ..
perl patcher2.pl --download --app=firefox --brand=Firefox --config=patcher-configs/moz20-branch-major-update-patcher2.cfg

cd temp/firefox
ln -s 5.0b7 4.0.1-5.0b7
cd ../..

perl patcher2.pl --create-patches --partial-patchlist-file=patchlist.cfg --app=firefox --brand=Firefox --config=patcher-configs/moz20-branch-major-update-patcher2.cfg

# remove partials for 4.0.1
cd temp/firefox/4.0.1-5.0b7
find aus2{,.test} -name partial.txt -exec rm {} \;

# check releasetest == beta
bash /builds/slave/rel-beta-updates//tools/release/compare-channel-snippets.sh aus2 beta aus2.test releasetest

# push up to aus
rsync -av -e 'ssh -oIdentityFile=~/.ssh/cltbld_dsa' aus2.test/ cltbld@aus2-staging.mozilla.org:/opt/aus2/snippets/staging/Firefox-5.0b6-build1-4.0.1-build1-test
rsync -av -e 'ssh -oIdentityFile=~/.ssh/cltbld_dsa' aus2/ cltbld@aus2-staging.mozilla.org:/opt/aus2/snippets/staging/Firefox-5.0b6-build1-4.0.1-build1

bash -c 'ssh -l cltbld -i ~/.ssh/cltbld_dsa aus2-staging.mozilla.org ~/bin/backupsnip Firefox-5.0b6-build1-4.0.1-build1-test'
bash -c 'ssh -l cltbld -i ~/.ssh/cltbld_dsa aus2-staging.mozilla.org ~/bin/pushsnip Firefox-5.0b6-build1-4.0.1-build1-test'

These really should have been Firefox-5.0b7-... instead of Firefox-5.0b6-....

Update Verify

Kicked off with

for p in linux linux64 macosx64 win32; do
  for i in 1 2 3 4 5 6 7 8 9 10; do
    curl "http://production-master1.build.sjc1.mozilla.com:8010/builders/release-mozilla-2.0-${p}_major_update_verify_${i}%2F10/force" >/dev/null
  done
done

Final Verify

Linux64, Windows and Mac all failed because of specific update.xml files not being present. I double checked those URLS and they now work. I have also re-triggered the failing platforms

Push Snippets

Because the 5*->5.0b7 updates were tested before the 4*->5.0b7 updates, and because we want this out to users asap, we are pushing the 5->5.0b7 snippets separately.

cd /opt/aus2/snippets/staging
~/bin/backupsnip Firefox-5.0b7-build1

And for the pushes:

~/bin/pushsnip Firefox-5.0b7-build1

4->5.0b7 go to beta was given later. The directory that the snippets were pushed to aus2-staging was labeled with b6 instead of b7. Verified that the snippets will point to b7 builds

Verified that the directory only contains beta 7 related snippets with:

$ cd /opt/aus2/snippets/staging/Firefox-5.0b6-build1-4.0.1-build1-test
$ grep -r 20110613165758 .

cd /opt/aus2/snippets/staging
~/bin/backupsnip Firefox-5.0b6-build1-4.0.1-build1-test

And for the pushes:

~/bin/pushsnip Firefox-5.0b6-build1-4.0.1-build1-test

Turns out re-pushing the test snippets isn't what we need. Lets try that again:

~/bin/backupsnip Firefox-5.0b6-build1-4.0.1-build1
~/bin/pushsnip   Firefox-5.0b6-build1-4.0.1-build1