canmove, Confirmed users
2,850
edits
Releases/Firefox 2.0.0.18:BuildNotes: Difference between revisions
Jump to navigation
Jump to search
Releases/Firefox 2.0.0.18:BuildNotes (view source)
Revision as of 00:07, 13 November 2008
, 13 November 2008→Final Verification
ChrisCooper (talk | contribs) |
ChrisCooper (talk | contribs) |
||
| Line 175: | Line 175: | ||
====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-firefox-*.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: | * Before pushing final updates,verify that "release" and "releasetest" channel match: | ||
# on aus2-staging | # on aus2-staging | ||
| Line 184: | Line 194: | ||
sys 0m13.461s | sys 0m13.461s | ||
Encountered 404s when trying to retrieve files from two mirrors: | |||
* mozilla.c3sl.ufpr.br | |||
* mozilla-mirror.naist.jp | |||
justdave indicated that this was a known issue with sentry adding mirrors before they have all the files. I was able to access all the 404 files on subsequent attempts. | |||
==== Publish Updates to Release Channel ==== | ==== Publish Updates to Release Channel ==== | ||