Releases/Firefox 5.0b4/BuildNotes
Notes About Releasing
Please update the Release:Primer for future releases (bug fixes, changes to automation) as needed
Build Engineers
bhearsum - bug 660940
Signed-off Revision(s)
Build 1: [1]
L10N changesets
From Axel's webapp.
Tags
| Build # | Tag | Changeset |
| 1 | GECKO50_2011060309_RELBRANCH | bca54750eec4 |
| FIREFOX_5_0b4_RELEASE FIREFOX_5_0b4_BUILD1 | bca54750eec4 |
Build data
| Build # | Type | Build ID | Build machine | Time to build |
| 1 | Linux | 20110603100923 | mv-moz2-linux-ix-slave18 | 1 hrs, 5 mins, 4 secs |
| Linux64 | moz2-linux64-slave02 | 1 hrs, 9 mins, 24 secs | ||
| Mac | moz2-darwin10-slave23 | 4 hrs, 11 mins, 4 secs | ||
| Windows | mw32-ix-slave17 | 2 hrs, 41 mins, 44 secs |
Notes
Build 1
Setup
- Marked "Any master", "mozilla-beta", "Any builder" for a clobber
- About an hour ahead of the expected "go", set reserved_slaves to 6:
[cltbld@production-master03 builder_master]$ pwd /builds/buildbot/builder_master [cltbld@production-master03 builder_master]$ echo 6 > reserved_slaves_pm03
- Hit "ship it" button on "Firefox 5 Beta Build 4" (https://l10n-stage-sj.mozilla.org/shipping/milestones)
- Landed configs, merged configs & custom to production.
- Tagged buildbot-configs, buildbotcustom, and tools with FIREFOX_5_0b4_RELEASE and FIREFOX_5_0b4_BUILD1
- Update pm03 checkouts & reconfiged
- Ran release_sanity dry run with:
PYTHONPATH=.:tools/lib/python/ python tools/buildbot-helpers/release_sanity.py -u bhearsum -V 5.0b4 --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 bhearsum -V 5.0b4 --branch mozilla-beta --build-number 1 -c release-firefox-mozilla-beta.py localhost:9010
Tag
No problems.
Start Autosign
Once mozilla-beta was tagged, on keymaster, started signcodepwd.exe, opened a cygwin terminal and run the following:
PRODUCT=firefox
VERSION=5.0b4
BUILD=1
TAG=FIREFOX_5_0b4_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
No problems
Source
No problems
Build/Repack
- Linux: No problems
- Linux64: No problems
- Windows: No problems
- Mac: 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
A few legitimate looking string changes.
Updates (5.0b[1-3] -> 5.0b4)
No problems -- including with the update verify config bump.
Update verify
All green. Manually looked at logs 1/10 and 10/10 for each platform - no differences between 5.0b3+MAR and 5.0b4 in any of them.
Updates (4.0many -> 5.0b4)
Manually bumped patcher config and update verify config. Bumped FIREFOX_4_0_1_RELEASE tag on buildbot-configs, FIREFOX_4_0_1_{BUILD1,RELEASE}_RUNTIME on tools.
Generation was done on mv-moz2-linux-ix-slave13, using the UPDATE_PACKAGING_R14 tag, and re-using the updates directory from the 5.0b[12] -> 5.0b3 updates run, to save time & energy.
cd /builds/slave/rel-beta-updates/build/patcher-configs
cvs up
perl patcher2.pl --download --app=firefox --brand=Firefox --config=patcher-configs/moz20-branch-major-update-patcher2.cfg
cd temp/firefox
ln -s 5.0b4 4.0.1-5.0b4
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.0b4
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.0b4-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.0b4-build1-4.0.1-build1
# push test snippets live
bash -c 'ssh -l cltbld -i ~/.ssh/cltbld_dsa aus2-staging.mozilla.org ~/bin/backupsnip Firefox-5.0b4-build1-4.0.1-build1-test'
bash -c 'ssh -l cltbld -i ~/.ssh/cltbld_dsa aus2-staging.mozilla.org ~/bin/pushsnip Firefox-5.0b4-build1-4.0.1-build1-test'
Update Verify
To force all of the verify builders, used the following script (warning: not OS X compatible):
for p in linux linux64 macosx64 win32; do
for i in `seq 1 10`; do
curl "http://production-master01.build.mozilla.org:8010/builders/release-mozilla-2.0-${p}_major_update_verify_${i}%2F10/force" >/dev/null
done
done
Differences in all platforms:
diff -r source/firefox/defaults/pref/channel-prefs.js target/firefox/defaults/pref/channel-prefs.js
1,2c1,2
< //@line 2 "/builds/slave/rel-2.0-lnx-bld/build/browser/app/profile/channel-prefs.js"
< pref("app.update.channel", "release");
---
> //@line 2 "/builds/slave/rel-beta-lnx-bld/build/browser/app/profile/channel-prefs.js"
> pref("app.update.channel", "beta");
WARN: non-binary files found in diff
Locale specific differences:
- en-ZA: answers.xml, creativecommons.xml
- ro: creativecommons.xml
Which all look like legitimate search engine changes.
And platform specific differences,:
- Mac:
Only in source/Firefox.app: force_plist_reload
Which is OK because bug 386760 removed that file in 5.0.
Why did de, fy-NL, el, en-US, kk, nso, and sq not have this line?
- Windows:
Only in source/bin: D3DCompiler_42.dll Only in source/bin: d3dx9_42.dll
Which is OK because these files were replaced with _43 versions when bug 648804 landed.
Channel switching snippets
# cltbld@aus2-staging cd /opt/aus2/snippets/staging mkdir -p Firefox-5.0b4-build1-channel-switching/Firefox/ rsync -a Firefox-5.0b4-build1-4.0.1-build1/Firefox/4.0.1 Firefox-5.0b4-build1-channel-switching/Firefox/ cd Firefox-5.0b4-build1-channel-switching/Firefox/ mv 4.0.1 5.0 for d in 5.0/*; do mv -v $d/* $d/30000000000000 done
Permissions check and A/V Scan
No permissions problems, A/V scan found no viruses.
A/V Notification
Mail got stuck in moderation, like previous Betas. No real problems, but filed bug 662262 on whitelisting mail from masters.
DID NOT RELEASE
We decided not to release this because we'd rather wait for 5.0b5.