Releases/Firefox 13.0b1/BuildNotes: Difference between revisions

 
(22 intermediate revisions by 3 users not shown)
Line 4: Line 4:
= Bugs hit =
= Bugs hit =
Enter any bugs pre-existing or newly discovered and filed during the release:
Enter any bugs pre-existing or newly discovered and filed during the release:
* {{bug|}} - description
* {{bug|747481}} pushsnip for test snippets didn't work properly because of file ownership on aus2-staging.  test snippets were pushed but the non-test snippets weren't transfered.  The following command was used to transfer the non-test snippets:
*
cd /builds/slave/rel-m-beta-updates/build/temp/firefox/12.0b6-13.0b1
rsync -av -e 'ssh -oIdentityFile=~/.ssh/auspush' aus2/ ffxbld@aus3-staging.mozilla.org:/opt/aus2/snippets/staging/Firefox-13.0b1-build1
 
Update and final verify needed to be triggered manually


=Build Engineers=
=Build Engineers=
Line 11: Line 14:


=Signed-off Revision(s)=
=Signed-off Revision(s)=
Build 1: [http://hg.mozilla.org/releases/mozilla-beta/rev/# #]
Build 1: [http://hg.mozilla.org/releases/mozilla-beta/rev/e60ca2e387a8 e60ca2e387a8]


=L10N changesets=
=L10N changesets=
Line 27: Line 30:
|-
|-
| rowspan="2" |  
| rowspan="2" |  
| MOBILE80_#_RELBRANCH, FENNEC_VERSION_RELEASE, FENNEC_VERSION_BUILD1
| MOBILE130_2012042512_RELBRANCH FENNEC_13_0b1_BUILD1 FENNEC_13_0b1_RELEASE
| [http://hg.mozilla.org/releases/mozilla-beta/rev/# #]
| [http://hg.mozilla.org/releases/mozilla-beta/rev/e8c31168413b e8c31168413b]
|-  
|-  
| GECKO80_#_RELBRANCH, FIREFOX_VERSION_BUILD1 FIREFOX_VERSION_RELEASE
| GECKO130_2012042512_RELBRANCH FIREFOX_13_0b1_BUILD1 FIREFOX_13_0b1_RELEASE 
| [http://hg.mozilla.org/releases/mozilla-beta/rev/# #]
| [http://hg.mozilla.org/releases/mozilla-beta/rev/f16e48c88ac3 f16e48c88ac3]
|}
|}


Line 45: Line 48:
| rowspan="4" | 1  
| rowspan="4" | 1  
| Linux
| Linux
| rowspan="4" |  
| rowspan="4" | 20120425123149
|  
| mv-moz2-linux-ix-slave04
|  
| 1 hrs, 4 mins, 8 secs
|-
|-
| Linux64
| Linux64
|  
| linux64-ix-slave07
|  
| 1 hrs, 2 mins, 19 secs
|-
|-
| Mac
| Mac
|  
| moz2-darwin10-slave43
|  
| 3 hrs, 19 mins, 29 secs
|-
|-
| Windows  
| Windows  
|  
| mw32-ix-slave10
|  
| 3 hrs, 27 mins, 39 secs
|}
|}


Line 71: Line 74:
|-
|-
| rowspan="2" | 1  
| rowspan="2" | 1  
| android
| android-xul
| rowspan="2" |  
| rowspan="2" | 20120425123100
|  
| mv-moz2-linux-ix-slave19 
|  
| 47 mins, 50 secs
|-
|-
| rowspan="2" | 2
| android-xul
| android-xul
|  
| rowspan="2" | 20120427095343
|
| mv-moz2-linux-ix-slave19
|  
|}
|}


Line 89: Line 94:
<small>[[Release:Release_Automation_on_Mercurial:Documentation#Starting_the_automation|detailed instructions]]</small>
<small>[[Release:Release_Automation_on_Mercurial:Documentation#Starting_the_automation|detailed instructions]]</small>
* Set clobbers for the appropriate masters. Doing this 24-48 hours in advance should speedup the build.
* Set clobbers for the appropriate masters. Doing this 24-48 hours in advance should speedup the build.
** [http://build.mozilla.org/clobberer clobberer]
** set any master, mozilla-beta, any builder on apr-24 at 5:52pm
* Reserve slaves, e.g.:
* Reserve slaves, e.g.:
<pre>
<pre>
Line 103: Line 108:
  ln -s ../candidates/$version-candidates $version-candidates
  ln -s ../candidates/$version-candidates $version-candidates
* Update l10n changesets for desktop, mobile
* Update l10n changesets for desktop, mobile
** [https://wiki.mozilla.org/Release:Release_Automation_on_Mercurial:Documentation#L10N_Changesets Instructions] on how to get them
** [https://l10n-stage-sj.mozilla.org/shipping/milestones dashboard]
* Land automation configs (are you or buildduty going to reconfig? great, merge. otherwise double-land only your configs)
* Land automation configs (are you or buildduty going to reconfig? great, merge. otherwise double-land only your configs)
* Tag buildbot-configs, buildbotcustom, & tools with build & release tags. <small>''([[Release:Release_Automation_on_Mercurial:Documentation#Starting_the_automation|details]])''</small>
* Tag buildbot-configs, buildbotcustom, & tools with build & release tags. <small>''([[Release:Release_Automation_on_Mercurial:Documentation#Starting_the_automation|details]])''</small>
** Sample command for Firefox 10.0 beta 5 build 1:
** Sample command for Firefox 10.0 beta 5 build 1:
<pre>
<pre>
hg tag -f FIREFOX_10_0b5_RELEASE FIREFOX_10_0b5_BUILD1
bash shortcut: hg tag -f {FIREFOX,FENNEC}_13_0b1_{RELEASE,BUILD1}
hg tag -f FENNEC_10_0b5_RELEASE FENNEC_10_0b5_BUILD1
# bash shortcut: hg tag -f {FIREFOX,FENNEC}_10_0b5_{RELEASE,BUILD1}
</pre>
</pre>
* update and reconfigure the master
* update and reconfigure the master
* start automation ''&larr; monitor progress on buildbot (e.g. [http://buildbot-master08.build.mozilla.org:8001/waterfall?num_events=10&category=release-mozilla-beta- beta])''
* start automation ''&larr; monitor progress on buildbot (e.g. [http://buildbot-master08.build.mozilla.org:8001/waterfall?num_events=10&category=release-mozilla-beta- beta])''
* reconfigure other masters (or ask the buildduty person to do this) <em>if you have done a merge (and not double-land) to production</em>
<pre>
# Combined release
cd /builds/buildbot/build1/master
source ../bin/activate
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u jhford -V 13.0b1 --branch mozilla-beta --build-number 1 \
    --release-config release-firefox-mozilla-beta.py --release-config release-fennec-mozilla-beta.py --products firefox,fennec  \
    --dryrun localhost:9001
</pre>


=== E-mail Metrics ===
Use the address "metrics-alerts < AT > mozilla < PERIOD > org"
For 3.6.25 you would send
Firefox,firefox,firefox,3.6.25,3.6
Firefox,firefox,firefox,3.6.26pre,3.6
For non-3.6 releases, we need to include Fennec in the email if we build Fennec.
For 9.0b2 it would be
Firefox,firefox,firefox,9.0b2,9.0
Fennec,firefox-mobile,fennec,9.0b2,9.0
And for 9.0 final it's
Firefox,firefox,firefox,9.0,9.0
Fennec,firefox-mobile,fennec,9.0,9.0
ESRs look like this:
Firefox,firefox,firefox,10.0.3,10.0
Firefox,firefox,firefox,10.0.3esr,10.0
=== E-mail mirrors@mozilla.org ===
Not necessary for rapid release betas, files only go as far as the 'internal mirrors'.
Coordinate yourself with the person creating the ESR and the latest release which normally go out at the same time.
They want to know approximately what time push to external mirrors will occur.  Ideally this is a 24hr notice to them, with the estimated time.
<pre>
<pre>
Subject: Firefox {VERSION1} [and {VERSION2}] coming to mirrors on {DATE}
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u jhford -V 13.0b1 --branch mozilla-beta \
Body:
--build-number 1 --release-config release-firefox-mozilla-beta.py --release-config release-fennec-mozilla-beta.py \
We're planning on pushing our Firefox {VERSION1} [and {VERSION2}] release(s) to mirrors 24 hours before {DATE}.
--products firefox,fennec localhost:9001
# If this is a chemspill, please mention that in the email as it will mean pinging
# for CDN to be enabled when the push to internal mirrors happens
 
If you believe these releases or these dates will cause any problems,
please notify release at mozilla.com. If you have any problems with mirror
status/weights/etc, please notify mirror-submissions at mozilla.org.
</pre>
</pre>


=== Edit rsync exclude files ===
=== E-mail Metrics ===
Edit /pub/mozilla.org/zz/rsyncd-mozilla-releases.exclude on stage so that it excludes the current release. This prevents external mirrors from picking up the new release prematurely.
Use the address "metrics-alerts < AT > mozilla < PERIOD > org"


For rapid release betas, this is not necessary as there's already an exclude that matches beta releases.
Firefox,firefox,firefox,13.0b1,13.0
Fennec,firefox-mobile,fennec,13.0b1,13.0


=== Tag ===
=== Tag ===
no problems


=== Bouncer Submitter ===
=== Bouncer Submitter ===
 
no problems


=== Source ===
=== Source ===
 
no problems


=== Build ===
=== Build ===
==== Firefox ====
==== Firefox ====
 
no problems
===== Firefox repacks =====
===== Firefox repacks =====
 
linux, linux64 finished and good
==== Fennec ====
==== Fennec ====


Line 187: Line 164:


====Source====
====Source====
no problems


====Build====
====Build====
 
no problems
=== Partner Repack ===
==== Firefox ====
==== Fennec ====


=== Android Signing ===
=== Android Signing ===
Line 199: Line 174:
Now run on signing1.
Now run on signing1.
=== L10N verify ===
=== L10N verify ===
 
no problems


=== Checksums ===
=== Checksums ===
 
no problems
=== Updates ===
=== Updates ===
 
Failed gracefully during pushsnip.  test updates were pushed but non-test snippets weren't uploaded.  See issues hit above to see how this was worked around
==== Update verify ====
==== Update verify ====
triggered manually, no problems


=== Major Update ===
=== Reset reserved slaves ===
Major update generation is not kicked off automatically. You should only create them once the final builds for the "latest" build are ready.
For instance, the 3.6.26 builds got created a week before the 10.0 release but the "final" 10.0 builds were not created after few days.


Follow instructions from the [[Release:Release_Automation_on_Mercurial:Documentation#Major_Update_.28Firefox_only.29|Major update]] documentation.
[cltbld@buildbot-master08 master]$ echo 0 > reserved_slaves_bm08-build1
 
==== Major Update verify ====
 
=== Reset reserved slaves ===


=== Check permissions / AV scan ===
=== Check permissions / AV scan ===
Line 223: Line 193:
=== Push to internal mirrors ===
=== Push to internal mirrors ===
This is done by automation for rapid release betas.
This is done by automation for rapid release betas.
For other releases, this should be done manually at this point, after check permissions / AV scan have completed.
* Make sure the rsync excludes have been updated ([[Releases/BuildNotesTemplate#Edit_rsync_exclude_files]])
* Force build the push to mirrors builder. Make sure at least 15 minutes have elapsed since editing the rysnc module to give it time to sync out.
[https://intranet.mozilla.org/ReleaseEngineering/Release/Primer#Mirrors_.28internal_.26_external.29 Mirrors Policy]


=== Final verification ===
=== Final verification ===
Record receipt of "completed_final_verification" emails (1 per platform)
Needed to be triggered manually


success on linux64,win32,linux,macosx64
=== Going to Beta ===
=== Going to Beta ===
<font color='orange'>NOTE: Skip to "Before Release Day" for '''beta''' releases</font>


==== Run backupsnip ====
==== Run backupsnip ====
NOTE: Remember to do this at least '''2 hours''' ahead of the expected "go to beta" email. <small>''[[Release:Release_Automation_on_Mercurial:Documentation#Prepare_for_Beta_Release_.28Firefox_only.29|details]]''</small>
 
# jford@aus3-staging
sudo su - ffxbld
~/bin/backupsnip Firefox-13.0b1-build1


==== Push to beta ====
==== Push to beta ====
Wait for "go" from release managers<br />
For Firefox:
* Publish (and record run time here): <small>''[[Release:Release_Automation_on_Mercurial:Documentation#Beta_Release_.28Firefox_only.29|details]]''</small>
* on completion, email r-d that VERSION updates are live on the beta channel


For Android:
# ffxbld@aus3-staging
* publish on Google Play (nee Android Marketplace), using [[#Publish_Fennec_to_the_Android_Market|instructions below]]
~/bin/pushsnip Firefox-13.0b1-build1
* on completions, email r-d that VERSION is live on Google Play


Wait for confirmation from QA that each of the above releases is okay, then close the tracking ticket.
=== Release Day ===
==== Publish Fennec to the Play Store (for beta releases and release releases) ====
=====Push the files (for beta releases and release releases)=====
* Updated push_fennec.sh and ran it as ffxbld@stage


=== Before Release Day ===
=====Play Store (for beta releases and release releases)=====
<!-- not for beta -->
* Pushed to the Google Play store.
Assuming this is not a chemspill.


==== Run backupsnip for release snippets ====
Firefox Beta disappeared from the Google Play store for phones. After some investigation, it was discovered that it was only compiled for large+xlarge screens. {{bug|749623}}. After consultation with Alex and Mark Finkle, we decided to respin to fix this.
Do this the night before release day as it can take up to two hours.


=== Push index file to mirrors ===
====Push XULRunner to Mirrors ====


=== Push to external mirrors ===
==== Update XULRunner wiki page ====
If this is a chemspill you will want to ping justdave (or other sysadmin) in #release-drivers and ask them to enable CDN.


* Remove previously added blacklisting entry from stage.mozilla.org:/pub/mozilla.org/zz/rsyncd-mozilla-releases.exclude
==== Check Throttling  ====
* Replace old version with the current one in stage.mozilla.org:/pub/mozilla.org/zz/rsyncd-mozilla-current.exclude


See [https://intranet.mozilla.org/RelEngWiki/index.php/Managing_Rsync_Modules details]
==== Push to Release Channel (for beta releases and release releases) ====
 
==Build 2==
A build 2 for '''mobile only''' was requested because of {{bug|749623}}
===Diff mozconfigs===
===Preparing to start Automation===
<small>[[Release:Release_Automation_on_Mercurial:Documentation#Starting_the_automation|detailed instructions]]</small>
* Set clobbers for the appropriate masters. Doing this 24-48 hours in advance should speedup the build.
** set any master, mozilla-beta, any builder on apr-27 at 9:19am
* Land automation configs (are you or buildduty going to reconfig? great, merge. otherwise double-land only your configs)
* Tag buildbot-configs, buildbotcustom, & tools with build & release tags. <small>''([[Release:Release_Automation_on_Mercurial:Documentation#Starting_the_automation|details]])''</small>
** Sample command for Firefox 10.0 beta 5 build 1:
<pre>
bash shortcut: hg tag -f FENNEC_13_0b1_{RELEASE,BUILD2}
</pre>
* update and reconfigure the master
* start automation ''&larr; monitor progress on buildbot (e.g. [http://buildbot-master08.build.mozilla.org:8001/waterfall?num_events=10&category=release-mozilla-beta- beta])''
<pre>
# Combined release
cd /builds/buildbot/build1/master
source ../bin/activate
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u jhford -V 13.0b1 --branch mozilla-beta --build-number 2 \
    --release-config release-fennec-mozilla-beta.py --products fennec  \
    --dryrun localhost:9001
</pre>
 
Then ran:
<pre>PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u jhford -V 13.0b1 --branch mozilla-beta --build-number 2 --release-config release-fennec-mozilla-beta.py --products fennec  localhost:9001</pre>
 
=== Tag ===


=== Release Day ===
==== Publish Fennec to the Play Store (for beta releases and release releases) ====
=====Push the files (for beta releases and release releases)=====
* Use [http://hg.mozilla.org/build/braindump/file/tip/releases-related/push_fennec.sh this script] and run it as ffxbld@stage (please push you changes prior to using it, and grab latest on stage via <tt>curl -O http://hg.mozilla.org/build/braindump/raw-file/tip/releases-related/push_fennec.sh</tt>)


=====Play Store (for beta releases and release releases)=====
=== Bouncer Submitter ===
'''IMPORTANT -''' Make sure to follow instructions!
* download multi apk (e.g. [http://ftp.mozilla.org/pub/mozilla.org/mobile/candidates/10.0b6-candidates/build1/android/multi/fennec-10.0b6.multi.android-arm.apk multi/fennec-10.0b6.multi.android-arm.apk])
* visit https://market.android.com/publish
* choose "Firefox Beta" or "Firefox"
* select the "APK Files" tab and choose "Upload APK"
** choose the multi apk that you downloaded and hit "upload"
*** NOTE: the progress bar does not seem to show progress (at least on Google Chrome)
** when it finishes uploading, verify VersionCode is the build date (almost anyway, the market reports an hour later than our buildID)
** hit "Save"
* activate new apk (You should see an Error message since both apk's are active)
* deactivate old apk (You should not see the Error message anymore)
* hit "Save"
* If this is a beta 1, go to "Product Details" tab -> Recent Changes, change the url to  http://www.mozilla.com/en-US/mobile/{VERSION}beta/releasenotes/
** and hit "Save"


====Push XULRunner to Mirrors ====


==== Update XULRunner wiki page ====
=== Source ===
For major releases or chemspills, update the links on:
* https://developer.mozilla.org/en/XULRunner
* https://developer.mozilla.org/en/Gecko_SDK


Also for older releases:
* https://developer.mozilla.org/en/XULRunner_1.9.2_Release_Notes
* https://developer.mozilla.org/en/Gecko_SDK


==== Check Throttling  ====
=== Build ===
See http://update-watch.localgho.st/release/ for example AUS links
==== Fennec ====


Some links to check:
===== Fennec repacks =====
* Automatic (idle time check) update links:
** 10.0.2 en-US [https://aus3.mozilla.org/update/1/Firefox/10.0.2/20120215223356/WINNT_x86-msvc/en-US/release/update.xml win32] [https://aus2.mozilla.org/update/1/Firefox/10.0.2/20120215223356/Linux_x86-gcc3/en-US/release/update.xml linux] [https://aus2.mozilla.org/update/1/Firefox/10.0.2/20120215223356/Darwin_x86_64-gcc3-u-i386-x86_64/en-US/release/update.xml mac] [https://aus2.mozilla.org/update/1/Firefox/10.0.2/20120215223356/Linux_x86_64-gcc3/en-US/release/update.xml linux64]
** 9.0 en-US [https://aus2.mozilla.org/update/1/Firefox/9.0/20111216140209/WINNT_x86-msvc/en-US/release/update.xml win32] [https://aus2.mozilla.org/update/1/Firefox/9.0/20111216140209/Linux_x86-gcc3/en-US/release/update.xml linux] [https://aus2.mozilla.org/update/1/Firefox/9.0/20111216140209/Darwin_x86_64-gcc3-u-i386-x86_64/en-US/release/update.xml mac] [https://aus2.mozilla.org/update/1/Firefox/9.0/20111216140209/Linux_x86_64-gcc3/en-US/release/update.xml linux64]
** 10.0.2esr en-US [https://aus2.mozilla.org/update/1/Firefox/10.0.2/20120216092139/WINNT_x86-msvc/en-US/esr/update.xml win32] [https://aus2.mozilla.org/update/1/Firefox/10.0.2/20120216092139/Linux_x86-gcc3/en-US/esr/update.xml linux] [https://aus2.mozilla.org/update/1/Firefox/10.0.2/20120216092139/Darwin_x86_64-gcc3-u-i386-x86_64/en-US/esr/update.xml mac] [https://aus2.mozilla.org/update/1/Firefox/10.0.2/20120216092139/Linux_x86_64-gcc3/en-US/esr/update.xml linux64]
** 10.0esr en-US [https://aus2.mozilla.org/update/1/Firefox/10.0/20120130064731/WINNT_x86-msvc/en-US/esr/update.xml win32] [https://aus2.mozilla.org/update/1/Firefox/10.0/20120130064731/Linux_x86-gcc3/en-US/esr/update.xml linux] [https://aus2.mozilla.org/update/1/Firefox/10.0/20120130064731/Darwin_x86_64-gcc3-u-i386-x86_64/en-US/esr/update.xml mac] [https://aus2.mozilla.org/update/1/Firefox/10.0/20120130064731/Linux_x86_64-gcc3/en-US/esr/update.xml linux64]
** 3.6.27 en-US [https://aus2.mozilla.org/update/1/Firefox/3.6.27/20120216013254/WINNT_x86-msvc/en-US/release/update.xml win32] [https://aus2.mozilla.org/update/1/Firefox/3.6.27/20120216013254/Linux_x86-gcc3/en-US/release/update.xml linux] [https://aus2.mozilla.org/update/1/Firefox/3.6.27/20120216013254/Darwin_x86-gcc3-u-ppc-i386/en-US/release/update.xml mac]
* Manual update links:
** 10.0.2 en-US [https://aus3.mozilla.org/update/1/Firefox/10.0.2/20120215223356/WINNT_x86-msvc/en-US/release/update.xml?force=1 win32] [https://aus2.mozilla.org/update/1/Firefox/10.0.2/20120215223356/Linux_x86-gcc3/en-US/release/update.xml?force=1 linux] [https://aus2.mozilla.org/update/1/Firefox/10.0.2/20120215223356/Darwin_x86_64-gcc3-u-i386-x86_64/en-US/release/update.xml?force=1 mac] [https://aus2.mozilla.org/update/1/Firefox/10.0.2/20120215223356/Linux_x86_64-gcc3/en-US/release/update.xml?force=1 linux64]
** 9.0 en-US [https://aus2.mozilla.org/update/1/Firefox/9.0/20111216140209/WINNT_x86-msvc/en-US/release/update.xml?force=1 win32] [https://aus2.mozilla.org/update/1/Firefox/9.0/20111216140209/Linux_x86-gcc3/en-US/release/update.xml?force=1 linux] [https://aus2.mozilla.org/update/1/Firefox/9.0/20111216140209/Darwin_x86_64-gcc3-u-i386-x86_64/en-US/release/update.xml?force=1 mac] [https://aus2.mozilla.org/update/1/Firefox/9.0/20111216140209/Linux_x86_64-gcc3/en-US/release/update.xml?force=1 linux64]
** 10.0.2esr en-US [https://aus2.mozilla.org/update/1/Firefox/10.0.2/20120216092139/WINNT_x86-msvc/en-US/esr/update.xml?force=1 win32] [https://aus2.mozilla.org/update/1/Firefox/10.0.2/20120216092139/Linux_x86-gcc3/en-US/esr/update.xml?force=1 linux] [https://aus2.mozilla.org/update/1/Firefox/10.0.2/20120216092139/Darwin_x86_64-gcc3-u-i386-x86_64/en-US/esr/update.xml?force=1 mac] [https://aus2.mozilla.org/update/1/Firefox/10.0.2/20120216092139/Linux_x86_64-gcc3/en-US/esr/update.xml?force=1 linux64]
** 10.0esr en-US [https://aus2.mozilla.org/update/1/Firefox/10.0/20120130064731/WINNT_x86-msvc/en-US/esr/update.xml?force=1 win32] [https://aus2.mozilla.org/update/1/Firefox/10.0/20120130064731/Linux_x86-gcc3/en-US/esr/update.xml?force=1 linux] [https://aus2.mozilla.org/update/1/Firefox/10.0/20120130064731/Darwin_x86_64-gcc3-u-i386-x86_64/en-US/esr/update.xml?force=1 mac] [https://aus2.mozilla.org/update/1/Firefox/10.0/20120130064731/Linux_x86_64-gcc3/en-US/esr/update.xml?force=1 linux64]
** 3.6.27 en-US [https://aus2.mozilla.org/update/1/Firefox/3.6.27/20120216013254/WINNT_x86-msvc/en-US/release/update.xml?force=1 win32] [https://aus2.mozilla.org/update/1/Firefox/3.6.27/20120216013254/Linux_x86-gcc3/en-US/release/update.xml?force=1 linux] [https://aus2.mozilla.org/update/1/Firefox/3.6.27/20120216013254/Darwin_x86-gcc3-u-ppc-i386/en-US/release/update.xml?force=1 mac]


==== Push to Release Channel (for beta releases and release releases) ====
=== Android Signing ===
Once there is enough uptake and we get "go" from release driver.
Instructions in [https://intranet.mozilla.org/Build:MobileSigning MobileSigning]


==== Update symlinks ====
Now run on signing1.
Once we're signed off on the release channel.
==== Publish Fennec to the Play Store (for beta releases and release releases) ====
===== Remove index.html files =====
=====Push the files (for beta releases and release releases)=====
If you created them earlier to hide the release.
* Updated push_fennec.sh and ran it as ffxbld@stage


==== Update browser choice website ====
=====Play Store (for beta releases and release releases)=====
* Push to google play

Latest revision as of 17:55, 27 April 2012

Notes About Releasing

Please update the Notes Template and the Release:Primer for future releases (bug fixes, changes to automation) as needed

Bugs hit

Enter any bugs pre-existing or newly discovered and filed during the release:

  • bug 747481 pushsnip for test snippets didn't work properly because of file ownership on aus2-staging. test snippets were pushed but the non-test snippets weren't transfered. The following command was used to transfer the non-test snippets:
cd /builds/slave/rel-m-beta-updates/build/temp/firefox/12.0b6-13.0b1
rsync -av -e 'ssh -oIdentityFile=~/.ssh/auspush' aus2/ ffxbld@aus3-staging.mozilla.org:/opt/aus2/snippets/staging/Firefox-13.0b1-build1

Update and final verify needed to be triggered manually

Build Engineers

{jhford} - Tracking bug: bug 744590

Signed-off Revision(s)

Build 1: e60ca2e387a8

L10N changesets

Instructions on how to get them

Tags

Manually tag the automation code, then record the generated tags below. (details)

Build # Branch, Tags Changeset
MOBILE130_2012042512_RELBRANCH FENNEC_13_0b1_BUILD1 FENNEC_13_0b1_RELEASE e8c31168413b
GECKO130_2012042512_RELBRANCH FIREFOX_13_0b1_BUILD1 FIREFOX_13_0b1_RELEASE f16e48c88ac3

Build data

Firefox

Build # Type Build ID Build machine Time to build
1 Linux 20120425123149 mv-moz2-linux-ix-slave04 1 hrs, 4 mins, 8 secs
Linux64 linux64-ix-slave07 1 hrs, 2 mins, 19 secs
Mac moz2-darwin10-slave43 3 hrs, 19 mins, 29 secs
Windows mw32-ix-slave10 3 hrs, 27 mins, 39 secs

Fennec

Build # Type Build ID Build machine Time to build
1 android-xul 20120425123100 mv-moz2-linux-ix-slave19 47 mins, 50 secs
2 android-xul 20120427095343 mv-moz2-linux-ix-slave19

Notes

Build 1

Diff mozconfigs

If this is a *.0 beta -> release. May also need to update the whitelist of nightly vs release differences for release sanity.

Preparing to start Automation

detailed instructions

  • Set clobbers for the appropriate masters. Doing this 24-48 hours in advance should speedup the build.
    • set any master, mozilla-beta, any builder on apr-24 at 5:52pm
  • Reserve slaves, e.g.:
[cltbld@buildbot-master08 master]$ pwd
/builds/buildbot/build1/master
[cltbld@buildbot-master08 master]$ cat reserved_slaves_bm08-build1 
8
  • For build1 only, create a symlink for your $version (eg 11.0b4, 10.0.2esr, 10.0.2, 3.6.27) (until bug 725839 is resolved)
# ffxbld@stage
cd /pub/mozilla.org/firefox/nightly/
mkdir ../candidates/$version-candidates
ln -s ../candidates/$version-candidates $version-candidates
  • Update l10n changesets for desktop, mobile
  • Land automation configs (are you or buildduty going to reconfig? great, merge. otherwise double-land only your configs)
  • Tag buildbot-configs, buildbotcustom, & tools with build & release tags. (details)
    • Sample command for Firefox 10.0 beta 5 build 1:
bash shortcut: hg tag -f {FIREFOX,FENNEC}_13_0b1_{RELEASE,BUILD1}
  • update and reconfigure the master
  • start automation ← monitor progress on buildbot (e.g. beta)
# Combined release
cd /builds/buildbot/build1/master
source ../bin/activate
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u jhford -V 13.0b1 --branch mozilla-beta --build-number 1 \
    --release-config release-firefox-mozilla-beta.py --release-config release-fennec-mozilla-beta.py --products firefox,fennec  \
    --dryrun localhost:9001
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u jhford -V 13.0b1 --branch mozilla-beta \
--build-number 1 --release-config release-firefox-mozilla-beta.py --release-config release-fennec-mozilla-beta.py \
--products firefox,fennec localhost:9001

E-mail Metrics

Use the address "metrics-alerts < AT > mozilla < PERIOD > org"

Firefox,firefox,firefox,13.0b1,13.0
Fennec,firefox-mobile,fennec,13.0b1,13.0

Tag

no problems

Bouncer Submitter

no problems

Source

no problems

Build

Firefox

no problems

Firefox repacks

linux, linux64 finished and good

Fennec

Fennec repacks

Unittests / Talos

details

  1. Look to see that they ran
  2. Document any oranges (per platform) for unittests - if possible, try to confirm it's known/random
  3. Make sure there's no red/failures that we need to have a dev look at

XULRunner

Source

no problems

Build

no problems

Android Signing

Instructions in MobileSigning

Now run on signing1.

L10N verify

no problems

Checksums

no problems

Updates

Failed gracefully during pushsnip. test updates were pushed but non-test snippets weren't uploaded. See issues hit above to see how this was worked around

Update verify

triggered manually, no problems

Reset reserved slaves

[cltbld@buildbot-master08 master]$ echo 0 > reserved_slaves_bm08-build1

Check permissions / AV scan

It is supposed to be triggered automatically after updates are done. File a bug if it doesn't. details

Push to internal mirrors

This is done by automation for rapid release betas.

Final verification

Needed to be triggered manually

success on linux64,win32,linux,macosx64

Going to Beta

Run backupsnip

# jford@aus3-staging
sudo su - ffxbld
~/bin/backupsnip Firefox-13.0b1-build1

Push to beta

# ffxbld@aus3-staging
~/bin/pushsnip Firefox-13.0b1-build1

Release Day

Publish Fennec to the Play Store (for beta releases and release releases)

Push the files (for beta releases and release releases)
  • Updated push_fennec.sh and ran it as ffxbld@stage
Play Store (for beta releases and release releases)
  • Pushed to the Google Play store.

Firefox Beta disappeared from the Google Play store for phones. After some investigation, it was discovered that it was only compiled for large+xlarge screens. bug 749623. After consultation with Alex and Mark Finkle, we decided to respin to fix this.

Push XULRunner to Mirrors

Update XULRunner wiki page

Check Throttling

Push to Release Channel (for beta releases and release releases)

Build 2

A build 2 for mobile only was requested because of bug 749623

Diff mozconfigs

Preparing to start Automation

detailed instructions

  • Set clobbers for the appropriate masters. Doing this 24-48 hours in advance should speedup the build.
    • set any master, mozilla-beta, any builder on apr-27 at 9:19am
  • Land automation configs (are you or buildduty going to reconfig? great, merge. otherwise double-land only your configs)
  • Tag buildbot-configs, buildbotcustom, & tools with build & release tags. (details)
    • Sample command for Firefox 10.0 beta 5 build 1:
bash shortcut: hg tag -f FENNEC_13_0b1_{RELEASE,BUILD2}
  • update and reconfigure the master
  • start automation ← monitor progress on buildbot (e.g. beta)
# Combined release
cd /builds/buildbot/build1/master
source ../bin/activate
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u jhford -V 13.0b1 --branch mozilla-beta --build-number 2 \
    --release-config release-fennec-mozilla-beta.py --products fennec  \
    --dryrun localhost:9001

Then ran:

PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u jhford -V 13.0b1 --branch mozilla-beta --build-number 2 --release-config release-fennec-mozilla-beta.py --products fennec  localhost:9001

Tag

Bouncer Submitter

Source

Build

Fennec

Fennec repacks

Android Signing

Instructions in MobileSigning

Now run on signing1.

Publish Fennec to the Play Store (for beta releases and release releases)

Push the files (for beta releases and release releases)
  • Updated push_fennec.sh and ran it as ffxbld@stage
Play Store (for beta releases and release releases)
  • Push to google play