Releases/Thunderbird 2.0.0.23/BuildNotes: Difference between revisions

m
no edit summary
mNo edit summary
 
(5 intermediate revisions by one other user not shown)
Line 86: Line 86:
* Buildbot waterfall is [http://production-1.8-master.build.mozilla.org:8910/waterfall here] (MPT-VPN); this is a separate instance from the Firefox master, with production-prometheus-vm and bm-xserve05 running a slave for each master
* Buildbot waterfall is [http://production-1.8-master.build.mozilla.org:8910/waterfall here] (MPT-VPN); this is a separate instance from the Firefox master, with production-prometheus-vm and bm-xserve05 running a slave for each master


Login to productioion-1.8-master as cltbld and start automation run:
Login to production-1.8-master as cltbld and start automation run:
  buildbot sendchange --username=bhearsum --master=localhost:9990 -m"Thunderbird 2.0.0.23 build 1" release
  buildbot sendchange --username=bhearsum --master=localhost:9990 -m"Thunderbird 2.0.0.23 build 1" release


Line 203: Line 203:


====Update bouncer====
====Update bouncer====
Done


==== Push to mirrors ====
==== Push to mirrors ====
# on stage (as cltbld)
rsync -av /data/cltbld/thunderbird-2.0.0.23/stage-merged/ /home/ftp/pub/thunderbird/releases/2.0.0.23/


====Update rsync module====
====Update rsync module====
On stage.mozilla.org, add the new release to the smaller, faster, rsync module:
# on stage (as cltbld)
cd /pub/mozilla.org/zz/
vi rsyncd-mozilla-current.exclude
and replace the previous latest release (Tb2.0.0.22) with:
+ thunderbird/releases/2.0.0.23
+ thunderbird/releases/2.0.0.23/**


====Final verification====
====Final verification====
* Verify that releasetest points to valid bouncer links:
hg clone http://hg.mozilla.org/build/tools
cd tools/release/updates
cat moz18-thunderbird-*.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 /opt/aus2/snippets/staging/20090813-Thunderbird-2.0.0.23
find -type d -iregex '.*release.*' | perl -nle '$a = $_; $a =~ s/release/releasetest/; system("diff -r -u $_ ../20090813-Thunderbird-2.0.0.23-test/$a");'


====Publish updates to release channel====
====Publish updates to release channel====
~/bin/backupsnip 20090813-Thunderbird-2.0.0.23


====Update symlink====
====Update symlink====
# cltbld @stage
cd /home/ftp/pub/thunderbird/releases
rm latest-2.0
rm latest
ln -s 2.0.0.23 latest-2.0
ln -s latest-2.0 latest # futureproofed!
Confirmed users
4,293

edits