Confirmed users
4,293
edits
Releases/Firefox 2.0.0.20/BuildNotes: Difference between revisions
Releases/Firefox 2.0.0.20/BuildNotes (view source)
Revision as of 04:58, 18 December 2008
, 18 December 2008no edit summary
No edit summary |
|||
| Line 112: | Line 112: | ||
====Publish Updates to Test Channels (betatest & releasetest)==== | ====Publish Updates to Test Channels (betatest & releasetest)==== | ||
Automated, no problems | Automated, no problems | ||
<font size="14" style="color: red">'''DONE TO HERE'''</font> | |||
==== Push updates to beta channel ==== | ==== Push updates to beta channel ==== | ||
Push beta and release together ? | |||
====Sign Installers==== | ====Sign Installers==== | ||
Done manually using these installer-signing-instructions [https://intranet.mozilla.org/Build:Unified_Release_Process#Sign_builds 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==== | ====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 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==== | ====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 ==== | ==== 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==== | ====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 | |||