Releases/Firefox 3.0.6/BuildNotes: Difference between revisions

Jump to navigation Jump to search
 
Line 204: Line 204:
  $ find -type d -iregex '.*release.*' | perl -nle '$a = $_; $a =~ s/release/releasetest/; system("diff -r -u $_ ../20090120-Firefox-3.0.6-test/$a");'
  $ find -type d -iregex '.*release.*' | perl -nle '$a = $_; $a =~ s/release/releasetest/; system("diff -r -u $_ ../20090120-Firefox-3.0.6-test/$a");'
  $
  $
==== Publish Updates to Release Channel ====
While waiting for the formal "go," ran:
-bash-3.2$ time ~/bin/backupsnip 20090120-Firefox-3.0.6
Running /bin/tar cfvj /opt/aus2/snippets/backup/20090203-1-pre-20090120-Firefox-3.0.6.tar.bz2 .
   
real 46m45.374s
user 0m38.342s
sys 1m6.426s
After formal go, ran:
$ time ~/bin/pushsnip 20090120-Firefox-3.0.6
real 0m53.148s
user 0m0.108s
sys 0m4.112s
====Release====
* fix latest symlink
# cltbld@stage
cd /home/ftp/pub/firefox/releases
rm latest-3.0 && ln -s 3.0.6 latest-3.0
After release, there were issues with several mirrors. nthomas had to [https://intranet.mozilla.org/Build:Updates disable all updates] while he and IT investigated.
From Sam:
<i>For those curious, the issue we had that caused us to pull updates was that a db server was mistakenly(?) taken out of rotation for bouncer, which was causing partial updates to fail. IT is investigating why this happened. Leaving updates on the release channel for users would've meant all (or maybe just most) users receiving full updates -- a problem for users (large download) and a problem for mirrors (lots more bandwidth). We'll talk more about this at the post-mortem that I'll schedule tomorrow for either later this week or early next.</i>
canmove, Confirmed users
2,850

edits

Navigation menu