Releases/Firefox 2.0.0.20/BuildNotes

Build Engineers

bhearsum got us started, then nthomas
Version/config bump bug

Bonsai queries

Build1: cvsroot

Tags

Build 1:

Module	Parent Branch	Created Tag/Branch	Pull date
cvsroot/mozilla	MOZILLA_1_8_BRANCH	GECKO181_20081217_RELBRANCH	2008-12-02 20:33 PST
	GECKO181_20081217_RELBRANCH	FIREFOX_2_0_0_20_RELEASE, FIREFOX_2_0_0_20_BUILD1	2008-12-17 08:18 PST
l10n/l01n	MOZILLA_1_8_BRANCH	GECKO181_20081217_RELBRANCH	2008-12-02 20:33 PST
	GECKO181_20081217_RELBRANCH	FIREFOX_2_0_0_20_RELEASE, FIREFOX_2_0_0_20_BUILD1	2008-12-17 08:58 PST

Build data

Type	Build machine
Windows	production-pacifica-vm
Mac	bm-xserve05
Linux	production-prometheus-vm

Notes

Build 1

Slave cleanup:

• production-prometheus-vm
  • /builds/verify/firefox-2.0.0.19, thunderbird-2.0.0.19
  • /builds/updates/firefox-2.0.0.19
  • /build/source/firefox-2.0.0.19, thunderbird-2.0.0.19
  • /data/cltbld/firefox-2.0.0.19
  • /builds/tags/FIREFOX_2_0_0_19_BUILD1, THUNDERBIRD_2_0_0_19_BUILD1
• bm-xserve05
  • /builds/verify/firefox-2.0.0.19, /builds/tinderbox/Fx-Mozilla1.8-FS/Depend*
• production-pacifica-vm
  • /builds/verify/firefox-2.0.0.19, /builds/symbols/firefox-2.0.0.19
• production-1.8-master
  • removed /builds/buildbot/Automation/twistd.log.???, twistd.log.??

Bootstrap tag: RELEASE_AUTOMATION_M11 (unchanged from Fx2.0.0.17 & 18 & 19)

Setup before starting:

• Updated /builds/buildbot/Automation/buildbot-configs on production-1.8-master. (No change to deploy)
  • master.cfg is "Locally Modified" to contain passwords. Identical to repository version otherwise.
  • Turned off the nightly builders on production-1.8-master to make sure they don't interfere with the release. (We need to figure out how to avoid this in the future).
    • commented out "c['schedulers'].append(depend_scheduler)"
  • updated mozilla1.8 tinderbox to say "no nightlies right now"
• land change to mozilla/tools/release/configs/fx-moz18-bootstrap.cfg, and move RELEASE_AUTOMATION_M11 tag to new revision (cvs tag -F RELEASE_AUTOMATION_M11 fx-moz18-bootstrap.cfg)
• verify tinderbox checkout on automation tag
  • prometheus-vm, bm-xserve05: cd /builds/tinderbox/mozilla/tools/tinderbox; cvs up -CPd -r RELEASE_AUTOMATION_M11
  • production-pacifica-vm: cd /cygdrive/c/builds/tinderbox/mozilla/tools/tinderbox; cvs up -CPd -r RELEASE_AUTOMATION_M11
• ensure that machines have enough resources
  • production-prometheus-vm - 30G in /
  • production-1.8-master - 30G in /builds, 19G in /data
  • production-pacifica-vm - ~31G in c:/
  • bm-xserve05 - 20G in /

Issued sendchange:

buildbot sendchange --username=bhearsum --master=localhost:9989 -m"Firefox 2.0.0.20 build 1" release

Tag

• No problems

Source

• No problems
• Verified only version bump changes between Fx2.0.0.19 build2 and this build in the source tarballs

Build

Automated, no problems. Checked that symbols were unpacked OK on talkback server.

Repack

Automated, no problems

Sign

• Signing doc

L10nVerify

Automated, no problems in log

Generate Updates

Automated, no problems

Publish Updates to Test Channels (betatest & releasetest)

Automated, no problems

DONE TO HERE

Push updates to beta channel

Push beta and release together ?

Sign Installers

Done manually using these installer-signing-instructions here

• complete stage-merged:

# on stage
cd /data/cltbld/firefox-2.0.0.20/
rsync -av batch1/mar/ stage-merged/
rsync -av batch1/stage-signed/ stage-merged/

• Create MD5 and SHA1 checksum files

# on stage
cd /data/cltbld/firefox-2.0.0.20/stage-merged/
~/bin/checksum-files .

• Fix permissions & ownership (on the two SUM files, and the detached sigs)

chown -R cltbld:firefox .
chmod 644 *SUMS

Update Bouncer

• Manually added entries to download.mozilla.org
• Note for next release: Do not remove the Check Now bit on the Firefox-2.0.0.19 Products until well after the change to the rsync module (to prevent the likes of bug 464566)

Push to mirrors

• push the stage-merged directory to the releases area:

# on stage
rsync -av /data/cltbld/firefox-2.0.0.20/stage-merged/ /home/ftp/pub/firefox/releases/2.0.0.20/

• edit the exclude file /pub/mozilla.org/zz/rsyncd-mozilla-current.exclude to add the new release (2.0.0.20) and remove the previous release (2.0.0.19).

Final Verification

• Verify that releasetest points to valid bouncer links:

# this can be run from anywhere
cvs co mozilla/testing/release
cd mozilla/testing/release/updates
cat moz18-firefox-*.cfg | grep -v major | sed 's/betatest/releasetest/' | grep -v 2.0a | grep -v 2.0b > update.cfg
./verify.sh -t update.cfg 2>&1 | tee quickVerify.log

• Look for any HTTP error codes besides 200 ("OK") and 302 ("Found"):

grep HTTP quickVerify.log | grep -v 200 | grep -v 302

• Before pushing final updates,verify that "release" and "releasetest" channel match:

# on aus2-staging
$ cd 20081217-Firefox-2.0.0.20
time find -type d -iregex '.*release.*' | perl -nle '$a = $_; $a =~ s/release/releasetest/; system("diff -r -u $_ ../20081217-Firefox-2.0.0.20-test/$a");'

Publish Updates to Release Channel

# on aus2-staging as cltbld
$ time ~/bin/backupsnip 20081217-Firefox-2.0.0.20

$ time ~/bin/pushsnip 20081217-Firefox-2.0.0.20

Release

• On stage.m.o, do the following:
  • Update "latest" symlinks

$ cd /pub/mozilla.org/firefox/releases/
$ rm latest-2.0 && ln -s 2.0.0.20 latest-2.0