Releases/Firefox 3.5.14/BuildNotes: Difference between revisions

No edit summary
 
(34 intermediate revisions by 2 users not shown)
Line 24: Line 24:
|-
|-
| FIREFOX_3_5_14_BUILD1 FIREFOX_3_5_14_RELEASE
| FIREFOX_3_5_14_BUILD1 FIREFOX_3_5_14_RELEASE
| 9cabb92310de
| [http://hg.mozilla.org/releases/mozilla-1.9.1/rev/dc338f6c00de dc338f6c00de]
|-
|-
| rowspan="2" | 2
| 2
| GECKO19114_20100930_RELBRANCH
| FIREFOX_3_5_14_BUILD2 FIREFOX_3_5_14_RELEASE
| #
| [http://hg.mozilla.org/releases/mozilla-1.9.1/rev/06ad1b12aef9 06ad1b12aef9]
|-
|-
| FIREFOX_3_5_14_BUILD1 FIREFOX_3_5_14_RELEASE
| 3
| #
| FIREFOX_3_5_14_BUILD3 FIREFOX_3_5_14_RELEASE
| [http://hg.mozilla.org/releases/mozilla-1.9.1/rev/dc338f6c00de dc338f6c00de]
|-
| 4
| FIREFOX_3_5_14_BUILD4 FIREFOX_3_5_14_RELEASE
| [http://hg.mozilla.org/releases/mozilla-1.9.1/rev/dc338f6c00de dc338f6c00de]
|}
|}


Line 253: Line 258:
Win32: PASS
Win32: PASS
===Major Update Generation (-> 3.6.11build2)===
===Major Update Generation (-> 3.6.11build2)===
* hit force build on waterfall
* first run failed because of Mercurial upgrade which took away the ability to fallback to a default username and {{bug|601996}} fixed that
* second run failed in download step, had couple of false starts because the configs had already been bumped. I backed out 20fb3b32e1cc changeset from tools, clobbered major_update/* on the slave and restarted
* fifth run - failed on createNsnippets - {{bug|602037}} filed, patch landed, updated buildbotcustom on pm02, clobbered major_update on the slave, backed out the config bump in hg.m.o/build/tools and started again.
* sixth run generated MU, but turned red due to already bumped patcher config. {{bug|596568}} is already filed from 3.5.13. Red status can be ignored for this run.
====Verification====
All red due to:
* mn locale was removed in 3.6.x:
grep ^FAIL: *_stdio.html
# all output is mn releated
The following entries are expected and can be ignored:
<pre>
$ grep "^Only in" *_stdio.html |sort -u   
linux_stdio.html:Only in source/firefox/searchplugins: iskalnik-gov-si.xml
linux_stdio.html:Only in source/firefox/searchplugins: najdi-si.xml
linux_stdio.html:Only in source/firefox/searchplugins: yahoo.xml
mac_stdio.html:Only in source/Firefox.app/Contents/MacOS/searchplugins: iskalnik-gov-si.xml
mac_stdio.html:Only in source/Firefox.app/Contents/MacOS/searchplugins: najdi-si.xml
mac_stdio.html:Only in source/Firefox.app/Contents/MacOS/searchplugins: yahoo.xml
mac_stdio.html:Only in source/Firefox.app/Contents: Plug-Ins
win32_stdio.html:Only in source/bin: .autoreg
win32_stdio.html:Only in source/bin: removed-files
win32_stdio.html:Only in source/bin/searchplugins: iskalnik-gov-si.xml
win32_stdio.html:Only in source/bin/searchplugins: najdi-si.xml
win32_stdio.html:Only in source/bin/searchplugins: yahoo.xml
$ grep -E "^File.*differ" *_stdio.html |sort -u
win32_stdio.html:Files source/bin/freebl3.chk and target/bin/freebl3.chk differ
win32_stdio.html:Files source/bin/nssdbm3.chk and target/bin/nssdbm3.chk differ
win32_stdio.html:Files source/bin/softokn3.chk and target/bin/softokn3.chk differ
</pre>
===Major Update Generation (3.5.14 build3 -> 3.6.11build3)===
* landed [https://bugzilla.mozilla.org/attachment.cgi?id=482863 config bump]
for build3, updated configs-default on moz2-master, reconfig'd pm02
* hit force build on waterfall MU builder
====Verification====
====Verification====
All three failed with same issues (known, and acceptable) as [https://wiki.mozilla.org/Releases/Firefox_3.5.14/BuildNotes#Verification previous MU verification]


===Publish updates to beta channel===
===Publish updates to beta channel===
# cltbld@aus2-staging
cd /opt/aus2/snippets/staging/
time ~/bin/backupsnip 20101004-Firefox-3.5.14-beta
time ~/bin/pushsnip 20101004-Firefox-3.5.14-beta
===Update Bouncer===
===Update Bouncer===
Triggered the bouncer_submitter on pm02 - ran sucessfully, bouncer updated.
===Final checks before push===
===Final checks before push===
# ffxbld@stage
cd /pub/mozilla.org/firefox/nightly/3.5.14-candidates/build3/
find . ! -user ffxbld # (anything in contrib/ is ok)
find . ! -group firefox
find . -type f ! -perm 644
find . -mindepth 1 -type d ! -perm 755 ! -name 'contrib*'
find . -maxdepth 1 -type d ! -perm 2775  -name 'contrib*'
===Virus check===
===Virus check===
# cltbld@stage
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 updates to release channel (and MU to beta)===
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 312: Line 406:
   xrbld@stage.mozilla.org:/home/ftp/pub/${PRODUCT}/nightly/${VERSION}-candidates/build${BUILD}/
   xrbld@stage.mozilla.org:/home/ftp/pub/${PRODUCT}/nightly/${VERSION}-candidates/build${BUILD}/
</pre>
</pre>
====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====
== Build 4 ==
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 ==
<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>
* Used clobberer to clean up all previous releases from pm02:8010
* Used clobberer to clean up all previous releases from pm02:8010
Line 383: Line 493:
Reviewed stdout, win32_signing_build1.log.  
Reviewed stdout, win32_signing_build1.log.  


'''At this point it became apparent that build4 was the same as build3 and so we stopped build4'''
'''At this point it became apparent that build4 was the same as build3 and so we stopped build4''' (verified by diffing build3 & build4 application.ini - only diff was build id)
 
===L10N Verify===
===Generate updates and push betatest snippets===
===Update Verify===
===Major Update Generation (-> 3.6.11build2)===
====Verification====
 
===Publish updates to beta channel===
===Update Bouncer===
===Final checks before push===
===Virus check===
===Push to mirrors===
===Final verify===
===Push updates to release channel (and MU to beta)===
===Release===
Confirmed users
4,467

edits