Confirmed users
4,467
edits
Releases/Firefox 3.5.14/BuildNotes: Difference between revisions
Releases/Firefox 3.5.14/BuildNotes (view source)
Revision as of 18:45, 21 October 2010
, 21 October 2010→Push XULRunner to mirrors
| (17 intermediate revisions by 2 users not shown) | |||
| Line 310: | Line 310: | ||
# ffxbld@stage | # ffxbld@stage | ||
cd /pub/mozilla.org/firefox/nightly/3.5.14-candidates/build3/ | cd /pub/mozilla.org/firefox/nightly/3.5.14-candidates/build3/ | ||
find . ! -user ffxbld (anything in contrib/ is ok) | find . ! -user ffxbld # (anything in contrib/ is ok) | ||
find . ! -group firefox | find . ! -group firefox | ||
find . -type f ! -perm 644 | find . -type f ! -perm 644 | ||
| Line 318: | Line 318: | ||
===Virus check=== | ===Virus check=== | ||
# cltbld@stage | # cltbld@stage | ||
clamdscan -r /mnt/netapp/stage/archive.mozilla.org/pub/firefox/nightly/3.5.14-candidates/build3 | clamdscan -r /mnt/netapp/stage/archive.mozilla.org/pub/firefox/nightly/3.5.14-candidates/build3/ | ||
WARNING: Ignoring unsupported option --recursive (-r) | |||
/mnt/netapp/stage/archive.mozilla.org/pub/firefox/nightly/3.5.14-candidates/build3: OK | |||
..... | |||
----------- SCAN SUMMARY ----------- | |||
Infected files: 0 | |||
Time: 3829.341 sec (63 m 49 s) | |||
===Push to mirrors=== | ===Push to mirrors=== | ||
rsync -av --exclude="*reporter*" --exclude=*.log --exclude=*.txt --exclude=*unsigned* /pub/mozilla.org/firefox/nightly/3.5.14-candidates/build3/ /pub/mozilla.org/firefox/releases/3.5.14/ | |||
# cltbld@stage | |||
vim -n /pub/mozilla.org/zz/rsyncd-mozilla-current.exclude | |||
# replace 3.5.13 with 3.5.14 | |||
===Final verify=== | ===Final verify=== | ||
===Push | Used "force build" to start the final_verification builder on pm02. | ||
Final verify failed because www.mirrorservice.org wasn't picking up the win32 builds and that happened to be the mirror sentry was hitting over and over. After discussion in IRC with justdave it was decided that www.mirrorservice.org would catch up eventually and this isn't a huge concern. | |||
=== Push release channel snippets === | |||
# cltbld@aus2-staging | |||
cd /opt/aus2/snippets/staging | |||
~/bin/backupsnip 20101004-Firefox-3.5.14 | |||
~/bin/backupsnip 20101013-Firefox-3.5.14-3.6.11-MU | |||
On "Go" in release-drivers email: | |||
~/bin/pushsnip 20101004-Firefox-3.5.14 | |||
Since we waited on the MU due to late time on release day, the MU went out two days later: | |||
~/bin/pushsnip 20101013-Firefox-3.5.14-3.6.11-MU | |||
===Release=== | ===Release=== | ||
# ffxbld@stage | |||
cd /home/ftp/pub/firefox/releases/ | |||
rm latest-3.5 && ln -s 3.5.14 latest-3.5 | |||
Sent the following to metrics@mozilla.com | |||
Firefox,firefox,firefox,3.5.14,3.5 | |||
Firefox,firefox,firefox,3.5.15pre,3.5 | |||
===XULRunner=== | ===XULRunner=== | ||
| Line 376: | Line 408: | ||
====Push XULRunner to mirrors==== | ====Push XULRunner to mirrors==== | ||
# xrbld@stage | |||
rsync -av --exclude=*.txt --exclude=*unsigned* --exclude=*symbols.zip \ | |||
/pub/mozilla.org/xulrunner/nightly/1.9.1.14-candidates/build3/ \ | |||
/pub/mozilla.org/xulrunner/releases/1.9.1.14/ | |||
Edited cltbld@stage:/pub/mozilla.org/zz/rsyncd-mozilla-releases.exclude and added | |||
- xulrunner/releases/1.9.1.13 | |||
# you want to exclude the <b>previous</b> release, not the current as I initially did | |||
====Update XULRunner wiki==== | ====Update XULRunner wiki==== | ||
Update the links in these two wiki pages for the version change. NOTE: make sure to update all the links on the page!!! | |||
* [https://developer.mozilla.org/En/XULRunner_1.9.1_Release_Notes Release Notes] | |||
* [https://developer.mozilla.org/En/Gecko_SDK Gecko_SDK] | |||
== Ignore me - never completed - Build 4 == | == Ignore me - never completed - Build 4 == | ||
<p>Build4 happened because the release tag *still* wasn't on the right revision, and was only discovered very close to pushing to beta. The build2 tags happened on the default branch, but the build3 ones happened on the relbranch. For some unknown reason, Mercurial still believes that the release tag is the default branch one -- which is incorrect. To fix, I removed the _RELEASE tag from default and the relbranch manually before starting the automation. This was tested in my user repo, and worked fine. (- bhearsum). Other prep:</p> | <p>Build4 happened because the release tag *still* wasn't on the right revision, and was only discovered very close to pushing to beta. The build2 tags happened on the default branch, but the build3 ones happened on the relbranch. For some unknown reason, Mercurial still believes that the release tag is the default branch one -- which is incorrect. To fix, I removed the _RELEASE tag from default and the relbranch manually before starting the automation. This was tested in my user repo, and worked fine. (- bhearsum). Other prep:</p> | ||