Releases/Thunderbird 2.0.0.17:BuildNotes: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 124: Line 124:


====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/thunderbird-2.0.0.17/
rsync -av batch1/mar/ stage-merged/
rsync -av batch1/stage-signed/ stage-merged/
* Create MD5 and SHA1 checksum files
# on stage
cd /data/cltbld/thunderbird-2.0.0.17/stage-merged/
~/bin/checksum-files .
* Fix permissions & ownership (on the two SUM files, and the detached sigs)
chown -R cltbld:thunderbird .
chmod 644 *SUMS


====Update Bouncer====
====Update Bouncer====
* Manually added entries to download.mozilla.org


====Add release to rsync module====
==== Push to mirrors ====
* push the stage-merged directory to the releases area:
# on stage (as cltbld)
rsync -av /data/cltbld/thunderbird-2.0.0.17/stage-merged/ /home/ftp/pub/thunderbird/releases/2.0.0.17/


====Push to mirrors====
====Update symlink====
On stage.m.o, change symlink to point to new release:
  $ cd /pub/mozilla.org/thunderbird/releases
  # confirm where latest symlinks point to where before starting
  $ ls -la latest*
lrwxrwxrwx  1 cltbld thunderbird 8 May  1 07:04 latest -> 2.0.0.16
lrwxrwxrwx  1 root  thunderbird 8 Feb 26 09:27 latest-1.5 -> 1.5.0.14
lrwxrwxrwx  1 cltbld thunderbird 8 May  1 07:04 latest-2.0 -> 2.0.0.16
  $ rm latest    # (note no trailing slash)
  $ ln -s 2.0.0.17 latest
  $ rm latest-2.0  # (note no trailing slash)
  $ ln -s 2.0.0.17 latest-2.0
  # confirm latest symlinks point to newest release
  $ ls -la latest*
lrwxrwxrwx  1 cltbld thunderbird 8 Jul 23 19:09 latest -> 2.0.0.17
lrwxrwxrwx  1 root  thunderbird 8 Feb 26 09:27 latest-1.5 -> 1.5.0.14
lrwxrwxrwx  1 cltbld thunderbird 8 Jul 23 19:10 latest-2.0 -> 2.0.0.17
 
==== 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.16) with:
+ thunderbird/releases/2.0.0.17
+ thunderbird/releases/2.0.0.17/**


====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-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/20080915-Thunderbird-2.0.0.17
find -type d -iregex '.*release.*' | perl -nle '$a = $_; $a =~ s/release/releasetest/; system("diff -r -u $_ ../20080915-Thunderbird-2.0.0.17-test/$a");'
==== 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
  # backup snippets on release/live channel
  $ sudo su - cltbld
  $ cd /opt/aus2/snippets/staging
  $ time ~/bin/backupsnip 20080915-Thunderbird-2.0.0.17
real    ?
user    ?
sys    ?
* After QA finished testing the releasetest channel, enabled release channel:


====Publish Updates to Release Channel====
  # on aus2-staging
  # put snippets on release/live channel
  $ sudo su - cltbld
  $ cd /opt/aus2/snippets/staging
  $ time ~/bin/pushsnip 20080915-Thunderbird-2.0.0.17
real    ?
user    ?
sys    ?
Confirmed users
4,293

edits