Releases/Thunderbird 2.0.0.24/BuildNotes: Difference between revisions

→‎Build 1: Final prep
(→‎Build 1: Final prep)
Line 209: Line 209:
  chmod 644 *SUMS
  chmod 644 *SUMS


====Update bouncer====
====Update Bouncer====
Done. Left out Solaris because they have something unusual for 2.0.0.23 and I want to hear directly what should be configured.
Done. Left out Solaris because they have something unusual for 2.0.0.23 and I want to hear directly what should be configured.


'''DONE TO HERE'''
<font color=red>'''DONE TO HERE'''</font>


<i>
==== Push to mirrors ====
==== Push to mirrors ====
<i>
  # on stage (as cltbld)
  # on stage (as cltbld)
  rsync -av /data/cltbld/thunderbird-2.0.0.24/stage-merged/ /home/ftp/pub/thunderbird/releases/2.0.0.24/
  rsync -av /data/cltbld/thunderbird-2.0.0.24/stage-merged/ /home/ftp/pub/thunderbird/releases/2.0.0.24/
Line 221: Line 221:


====Update rsync module====
====Update rsync module====
Thunderbird 2.0.0.x is no longer in the mozilla-current rsync module. Nothing to do here.
<i>
====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-{win32,mac,linux}.cfg | 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


====Final verification====
* Before pushing final updates,verify that "release" and "releasetest" channel match:
# on aus2-staging
cd /opt/aus2/snippets/staging/20100301-Thunderbird-2.0.0.24
find -type d -iregex '.*release.*' | perl -nle '$a = $_; $a =~ s/release/releasetest/; system("diff -r -u $_ ../20100301-Thunderbird-2.0.0.24-test/$a");'


====Publish updates to release channel====
====Publish updates to release channel====
* '''In case you need to cancel/abort updates, the quickest way to do this is [https://intranet.mozilla.org/Build:Updates here]'''
* While waiting for QA to finish testing, do a backup:
# on aus2-staging verify we have correct tools
sudo su - cltbld
cd ~/bin
cvs update -dP
~/bin/backupsnip 20100301-Thunderbird-2.0.0.24
* After QA finished testing the releasetest channel and go from release driver, enable release channel:
# on aus2-staging
sudo su - cltbld
~/bin/pushsnip 20100301-Thunderbird-2.0.0.24


====Update symlink====
====Update symlink====
# cltbld@stage
cd /pub/mozilla.org/thunderbird/releases
rm latest-2.0
ln -s 2.0.0.24 latest-2.0
</i>
Confirmed users
4,293

edits