Thunderbird 2.0.0.12:BuildNotes: Difference between revisions

Jump to navigation Jump to search
Final steps
mNo edit summary
(Final steps)
 
Line 223: Line 223:
  chown -R cltbld:thunderbird .
  chown -R cltbld:thunderbird .
  chmod 644 *SUMS
  chmod 644 *SUMS
===Release===
* get the last formal "go" from QA/Dev/website/IT/release-drivers
* push the stage-merged directory to the releases area (had to create target dir as root first):
# on stage
rsync -av /data/cltbld/thunderbird-2.0.0.12/stage-merged/ /home/ftp/pub/thunderbird/releases/2.0.0.12/
* After pushing live, move forward the "latest" and "latest-2.0" symlinks.
  cd /home/ftp/pub/thunderbird/releases/
  rm latest
  ln -s 2.0.0.12 latest
  rm latest-2.0
  ln -s 2.0.0.12 latest-2.0
* Update stage:/etc/rsyncd-mozilla-current.exclude - not critical that this happens immediately.
===Update Bouncer===
* Add entries to download.mozilla.org
===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-thunderbird-*.cfg | sed 's/betatest/releasetest/' > 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/20080219-Thunderbird-2.0.0.12
find -type d -iregex '.*release.*' | perl -nle '$a = $_; $a =~ s/release/releasetest/; system("diff -r -u $_ ../20080219-Thunderbird-2.0.0.12-test/$a");'
===Enable update channel===
* Wait for QA to finish testing update snippets on releasetest channel, then enable update snippets on release channel
  # on aus2-staging
  # put snippets on release/live channel
  $ screen
  $ sudo su - cltbld
  $ cd /opt/aus2/snippets/staging
  $ ~/bin/pushsnip 20080219-Thunderbird-2.0.0.12
Confirmed users
4,293

edits

Navigation menu