Confirm
4,293
edits
Changes
→Build 2
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.18 Products until well after the change to the rsync module (to prevent the likes of {{bug|464566}})''
'''DONE TO HERE'''
==== Push to mirrors ====
* push the stage-merged directory to the releases area:
# on stage
rsync -av /data/cltbld/firefox-2.0.0.19/stage-merged/ /home/ftp/pub/firefox/releases/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 20081204-Firefox-2.0.0.19
time find -type d -iregex '.*release.*' | perl -nle '$a = $_; $a =~ s/release/releasetest/; system("diff -r -u $_ ../20081204-Firefox-2.0.0.19-test/$a");'
==== Publish Updates to Release Channel ====
backupsnip was run as part of the Firefox 3.0.4 release process: [[Releases/Firefox_3.0.4:BuildNotes|3.0.4 build notes]]
# on aus2-staging
$ time ~/bin/pushsnip 20081204-Firefox-2.0.0.19
====Release====
* On stage.m.o, do the following:
** Update "latest" symlinks
$ cd /pub/mozilla.org/firefox/releases/
$ mv latest-2.0 latest-2.0.old
$ ln -s 2.0.0.19 latest-2.0
$ rm latest-2.0.old
