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 663967

Signed-off Revision(s)

Build 1: 19e59b25e886 (was sent email with signoff for e1251d5e4cc2 which was corrected to 19e...)

L10N changesets

Tags

Build #	Tag	Changeset
1	GECKO50_2011061316_RELBRANCH	937762949167
	FIREFOX_5_0b6_RELEASE FIREFOX_5_0b6_BUILD1	937762949167

Build data

Build #	Type	Build ID	Build machine	Time to build
1	Linux	20110613165758	mv-moz2-linux-ix-slave13	1 hrs, 7 mins, 58 secs
	Linux64		moz2-linux64-slave02	1 hrs, 8 mins, 23 secs
	Mac		moz2-darwin10-slave16	???
	Windows		mw32-ix-slave17	2 hrs, 49 mins, 14 secs

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_0b6_RELEASE and FIREFOX_5_0b6_BUILD1
• Update pm03 checkouts & reconfigured
• Ran release_sanity dry run with:

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

• And then to start the release:

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

Tag

Worked

Start Autosign

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

PRODUCT=firefox
VERSION=5.0b6
BUILD=1
TAG=FIREFOX_5_0b6_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}

Bouncer Submitter

Worked fine.

Source

Worked fine.

Build/Repack

• Linux: No problems
• Linux64: No problems
• Win32: No problems
• Mac OS X 64bit: No problems

Reset reserved_slaves

[cltbld@production-master03 builder_master]$ pwd
/builds/buildbot/builder_master
[cltbld@production-master03 builder_master]$ echo 0 > reserved_slaves_pm03

Signing

No problems. Closed signcodepwd.exe after signing finished. Got "signature verification succeeded" mail a few hours later.

L10n Verify

Windows, Linux and Linux64 all showed the same diff, which was expected due to the ja locale changeset changing. ja-JP on mac did not have this change.

diff -r firefox-5.0b6-build1/diffs/linux-x86_64.ja.diff firefox-5.0b5-build1/diffs/linux-x86_64.ja.diff
14351c14351
< > <!ENTITY fullScreenExit.label		"全画面表示モードを終了">
---
> > <!ENTITY fullScreenExit.label		"フルスクリーンモードを終了">

Updates

5.* -> 5.0b6

Generation

Generated properly

Update Verify

still need to check update_verify

4 -> 5.0b6

Generation

Landed update verify and [??? patcher config] bumps

Bumped FIREFOX_4_0_1_RELEASE tag on buildbot-configs, FIREFOX_4_0_1_{BUILD1,RELEASE}_RUNTIME on tools.

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

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.0b6
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'

Verification

Update Verify

To force all of the verify builders, used the following script:

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

Push Files

As in 5.0b2, we'll be pushing to a few internal mirrors rather than the whole network. To set this up, added the following to stage:/pub/mozilla.org/zz/rsyncd-mozilla-releases.exclude:

- firefox/releases/5.0b6

...and waited a few minutes, to ensure that the rsync servers have the file.

Then, forced the "release-mozilla-beta-push_to_mirrors" builder with the following properties:

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

Final Verify

Triggered manually, because we're not going to get enough uptake to have them fire automatically.

Push snippets

We elected not to continue with the 4->5b6 snippets, so we are only pushing 5bX->5b6

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

And for the pushes:

~/bin/pushsnip Firefox-5.0b6-build1