Releases/Fennec 14.0b6/BuildNotes: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
(25 intermediate revisions by the same user 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|761502}} - mozilla-beta mozconfig whitelist updates


=Build Engineers=
=Build Engineers=
{name} - Tracking bug: {{bug|#}}
{aki} - Tracking bug: {{bug|758788}}


=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/e835d6524759 e835d6524759]


=L10N changesets=
=L10N changesets=
[https://wiki.mozilla.org/Release:Release_Automation_on_Mercurial:Documentation#L10N_Changesets Instructions] on how to get them
* Fennec: [https://l10n.mozilla.org/shipping/json-changesets?ms=fennec14_beta_b6&platforms=android&multi_android-multilocale_repo=mobile-browser&multi_android-multilocale_rev=default&multi_android-multilocale_path=locales%2Fmaemo-locales link to the json]
* Firefox: link to the l10n-changesets
* Fennec: link to the json


=Tags=
=Tags=
Line 25: Line 23:
| style="background:#efefef" | '''Changeset'''
| style="background:#efefef" | '''Changeset'''
|-
|-
| rowspan="2" |
| 1
| MOBILE80_#_RELBRANCH, FENNEC_VERSION_RELEASE, FENNEC_VERSION_BUILD1
| MOBILE140_2012060523_RELBRANCH, FENNEC_14_0b6_RELEASE, FENNEC_14_0b6_BUILD1
| [http://hg.mozilla.org/releases/mozilla-beta/rev/# #]
| [http://hg.mozilla.org/releases/mozilla-beta/rev/7054a9e24f11 7054a9e24f11]
|-
| GECKO80_#_RELBRANCH, FIREFOX_VERSION_BUILD1 FIREFOX_VERSION_RELEASE
| [http://hg.mozilla.org/releases/mozilla-beta/rev/# #]
|}
|}


=Build data=
=Build data=
== Firefox ==
{| class="fullwidth-table"
| style="background:#efefef" | '''Build #'''
| style="background:#efefef" | '''Type'''
| style="background:#efefef" | '''Build ID'''
| style="background:#efefef" | '''Build machine'''
| style="background:#efefef" | '''Time to build'''
|-
| rowspan="4" | 1
| Linux
| rowspan="4" |
|
|
|-
| Linux64
|
|
|-
| Mac
|
|
|-
| Windows
|
|
|}
== Fennec ==
== Fennec ==
{| class="fullwidth-table"
{| class="fullwidth-table"
Line 71: Line 39:
| rowspan="2" | 1  
| rowspan="2" | 1  
| android
| android
| rowspan="2" |  
| rowspan="2" | 20120605235323
|  
| linux-ix-slave37
|  
| 53 mins, 29 secs
|-
|-
| android-xul
| android-xul
|  
| linux-ix-slave19
|
| 51 mins, 18 secs
|}
|}


Line 87: Line 55:
===Preparing to start Automation===
===Preparing to start Automation===
<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 mozilla-beta
** [https://build.mozilla.org/clobberer/ clobberer]
* Reserved 5 slaves
* Reserve slaves (<small>you need ~5 each of linux, linux64, win32 (w32), and macosx64 (moz2-darwin10)</small>). Doing this 2-3 hours in advance should speed things up. e.g.:
* Updated l10n changesets for mobile
<pre>
* Double landed automation configs
[cltbld@buildbot-master13 master]$ pwd
* Tagged buildbot-configs, buildbotcustom, & tools with build & release tags.  
/builds/buildbot/build1/master
* updated and reconfigured the master
[cltbld@buildbot-master13 master]$ cat reserved_slaves
 
8
</pre>
* 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, or tbirdbld and use thunderbird in path
cd /pub/mozilla.org/firefox/nightly/
mkdir ../candidates/$version-candidates
ln -s ../candidates/$version-candidates $version-candidates
* 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)
* 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>
hg tag -f FIREFOX_10_0b5_RELEASE FIREFOX_10_0b5_BUILD1
hg tag -f FENNEC_10_0b5_RELEASE FENNEC_10_0b5_BUILD1
# bash shortcut: hg tag -f {FIREFOX,FENNEC}_10_0b5_{RELEASE,BUILD1}
</pre>
* update and reconfigure the master
XXX: add notes on how to update the master
<pre>
<pre>
cd /builds/buildbot/build1/master
cd /builds/buildbot/build1/master
source ../bin/activate
source ../bin/activate
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u armenzg -V 13.0b1 --branch mozilla-beta --build-number 1 \
PYTHONPATH=. ../bin/python ../tools/buildbot-helpers/release_sanity.py -u aki -V 14.0b6 --branch mozilla-beta --build-number 1 \
    --release-config release-firefox-mozilla-beta.py --release-config release-fennec-mozilla-beta.py --products firefox,fennec \
-c release-fennec-mozilla-beta.py --products fennec --dryrun localhost:9001
    --dryrun localhost:9001
</pre>
</pre>
* start automation ''&larr; monitor progress on buildbot (e.g. [http://buildbot-master13.build.mozilla.org:8001/waterfall?num_events=10&category=release-mozilla-beta- beta])''
** the same command as above but without the "--dryrun"
* 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>


=== E-mail Metrics ===
Got:
Use the address "metrics-alerts < AT > mozilla < PERIOD > org". <small><em>Note for first-time-releasers: your email will get held for moderator approval - that is expected. If it happens more than once, get help on <tt>#metrics</tt>.</em></small>


For 3.6.25 you would send
<pre>
Firefox,firefox,firefox,3.6.25,3.6
2012-06-05 23:41:12,568 : ERROR : found in mobile/android/config/mozconfigs/android/nightly but not in mobile/android/config/mozconfigs/android/release: ac_add_options --enable-warnings-as-errors
Firefox,firefox,firefox,3.6.26pre,3.6
2012-06-05 23:41:12,569 : ERROR : found in mobile/android/config/mozconfigs/android/nightly but not in mobile/android/config/mozconfigs/android/release: ac_add_options --with-ccache=/usr/bin/ccache
2012-06-05 23:41:14,876 : ERROR : found in mobile/xul/config/mozconfigs/android/nightly but not in mobile/xul/config/mozconfigs/android/release: ac_add_options --enable-warnings-as-errors
2012-06-05 23:41:14,877 : ERROR : Error verifying mozconfigs
</pre>


For non-3.6 releases, we need to include Fennec in the email if we build Fennec.
* start automation ''&larr; monitor progress on buildbot (e.g. [http://buildbot-master13.build.mozilla.org:8001/waterfall?num_events=10&category=release-mozilla-beta- beta])''
** the same command as above but without the "--dryrun" and with "-m" to skip the mozconfig check:


For 9.0b2 it would be
PYTHONPATH=. ../bin/python ../tools/buildbot-helpers/release_sanity.py -u aki -V 14.0b6 --branch mozilla-beta --build-number 1 \
Firefox,firefox,firefox,9.0b2,9.0
  -c release-fennec-mozilla-beta.py --products fennec -m localhost:9001
  Fennec,firefox-mobile,fennec,9.0b2,9.0


And for 9.0 final it's
=== E-mail Metrics ===
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 or ESR builds, as the files only go as far as the 'internal mirrors'.
 
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>
Subject: Firefox {VERSION1} [and {VERSION2}] coming to mirrors on {DATE}
Body:
We're planning on pushing our Firefox {VERSION1} [and {VERSION2}] release(s) to mirrors 24 hours before {DATE}.
# 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>
 
=== Edit rsync exclude files ===
After getting [https://intranet.mozilla.org/Build:Setup_sysadmins_access svn setup] (auth req'd) edit files/rsync/rsyncd-mozilla-releases.exclude so that it excludes the current release, get review and deploy. This prevents external mirrors from picking up the new release prematurely.
Since Thunderbird doesn't inject index.html files into the file hierarchy, adding "- thunderbird/releases/13.0/**" (adjust for version) to the top of the file is all that's needed.


For rapid release betas and ESR builds, this is not necessary as there's already an exclude that matches them.
I did this in the Firefox 14.0b6 run.


=== Tag ===
=== Tag ===


=== Bouncer Submitter ===
First go failed b/c I failed to tag tools.
 


Fixed, re-ran the sendchange. No problems.
=== Source ===
=== Source ===
 
No problems.


=== Build ===
=== Build ===
==== Firefox ====
===== Firefox repacks =====
==== Fennec ====
==== Fennec ====
No problems.


===== Fennec repacks =====
===== Fennec repacks =====
 
No problems.
=== Unittests / Talos ===
<small>[[Release:Release_Automation_on_Mercurial:Documentation#Talos_.26_Unittests|details]]</small>
# Look to see that they ran
# Document any oranges (per platform) for unittests - if possible, try to confirm it's known/random
# Make sure there's no red/failures that we need to have a dev look at
 
=== XULRunner ===
 
====Source====
 
====Build====
 
==== Push to Mirrors ====
=== Partner Repack ===
==== Firefox ====
==== Fennec ====


=== Android Signing ===
=== Android Signing ===
Line 206: Line 107:


Now run on signing1.
Now run on signing1.
=== L10N verify ===
=== Checksums ===
=== Updates ===


==== Update verify ====
Did this via


=== Major Update ===
python26 mozharness/scripts/sign_android.py --cfg signing/android_mozilla-beta.py --platform android --platform android-xul
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.
to get both platforms; I should write a patch.


==== Major Update verify ====
Later: [http://hg.mozilla.org/build/mozharness/rev/570e1203a021 landed a fix].


=== Reset reserved slaves ===
=== Reset reserved slaves ===


=== Check permissions / AV scan ===
Done.
It is supposed to be triggered automatically after updates are done.
File a bug if it doesn't. <small>[[Release:Release_Automation_on_Mercurial:Documentation#Antivirus_check|details]]</small>
 
=== Push to internal mirrors ===
This is done by automation for rapid release betas. '''Note''': if you have to reconfig the release buildbot master in during the release, the uptake monitoring will fail ({{bug|629648}}). That means you'll need to manually send the "ready for releasetest" emails when you believe things are "good enough". Refer to a prior release for email details.
 
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 ===
Record receipt of "completed_final_verification" emails (1 per platform)


=== Going to Beta ===
=== Going to Beta ===
<font color='orange'>NOTE: Skip to "Before Release Day" for '''beta''' releases</font>
<font color='orange'>NOTE: Skip to "Before Release Day" for '''beta''' releases</font>


==== 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>
Remember to ssh to aus3-staging using your short LDAP name and then run <code>sudo su - ffxbld</code> once on.  If you intend to use screen, initiate your screen session while you are still yourself.
==== 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:
* publish on Google Play (nee Android Marketplace), using [[#Publish_Fennec_to_the_Android_Market|instructions below]]
* 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.
=== Before Release Day ===
<!-- not for beta -->
Assuming this is not a chemspill.
==== Run backupsnip for release snippets ====
Do this the night before release day as it can take up to two hours.
=== Push index file to mirrors ===
=== Push to external mirrors ===
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 rsync exclusion from stage.mozilla.org:/pub/mozilla.org/zz/rsyncd-mozilla-releases.exclude
* 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]
=== Release Day ===
==== Publish Fennec to the Play Store (for beta releases and release releases) ====
==== Publish Fennec to the Play Store (for beta releases and release releases) ====
=====Push the files (for beta releases and release releases)=====
=====Push the files (for beta releases and release releases)=====
Line 285: Line 129:
=====Play Store (for beta releases and release releases)=====
=====Play Store (for beta releases and release releases)=====
'''IMPORTANT -''' Make sure to follow instructions!
'''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])
* download both multi apks.  These have the same name so save them to separate directories.
** (If you're not building or pushing XUL fennec, you can skip the android-xul download/push)
** (e.g. [http://ftp.mozilla.org/pub/mozilla.org/mobile/candidates/14.0b6-candidates/build1/android/multi/fennec-14.0b6.multi.android-arm.apk android/multi/fennec-14.0b6.multi.android-arm.apk])
** (e.g. [http://ftp.mozilla.org/pub/mozilla.org/mobile/candidates/14.0b6-candidates/build1/android-xul/multi/fennec-14.0b6.multi.android-arm.apk android-xul/multi/fennec-14.0b6.multi.android-arm.apk])
* visit https://market.android.com/publish
* visit https://market.android.com/publish
* choose "Firefox Beta" or "Firefox"
* choose "Firefox Beta" or "Firefox"
* select the "APK Files" tab and choose "Upload APK"
* select the "APK Files" tab and choose "Upload APK"
** choose the multi apk that you downloaded and hit "upload"
** choose the android multi apk that you downloaded and hit "upload"
*** NOTE: the progress bar does not seem to show progress (at least on Google Chrome)
*** 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)
** when it finishes uploading, verify VersionCode is the build date (almost anyway, the market reports an hour later than our buildID)
** hit "Save"  
** hit "Save"
* activate new apk (You should see an Error message since both apk's are active)
* If you're also uploading XUL Fennec, repeat the same steps for the android-xul multilocale apk
* deactivate old apk (You should not see the Error message anymore)
* activate new android apk (You should see an Error message since both apk's are active)
* deactivate old android apk (You should not see the Error message anymore)
* If you're also activating XUL Fennec, repeat those steps for the android-xul multilocale apk.
* hit "Save"
* 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/
* 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"
** and hit "Save"
==== Update XULRunner wiki page ====
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  ====
See http://people.mozilla.com/~nthomas/update-watch/release/ for example AUS links
Some links to check:
* 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) ====
Once there is enough uptake and we get "go" from release driver.
==== Update symlinks ====
Once we're signed off on the release channel.
===== Remove index.html files =====
If you created them earlier to hide the release.
==== Update browser choice website ====

Latest revision as of 19:25, 11 June 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 761502 - mozilla-beta mozconfig whitelist updates

Build Engineers

{aki} - Tracking bug: bug 758788

Signed-off Revision(s)

Build 1: e835d6524759

L10N changesets

Tags

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

Build # Branch, Tags Changeset
1 MOBILE140_2012060523_RELBRANCH, FENNEC_14_0b6_RELEASE, FENNEC_14_0b6_BUILD1 7054a9e24f11

Build data

Fennec

Build # Type Build ID Build machine Time to build
1 android 20120605235323 linux-ix-slave37 53 mins, 29 secs
android-xul linux-ix-slave19 51 mins, 18 secs

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 mozilla-beta
  • Reserved 5 slaves
  • Updated l10n changesets for mobile
  • Double landed automation configs
  • Tagged buildbot-configs, buildbotcustom, & tools with build & release tags.
  • updated and reconfigured the master
cd /builds/buildbot/build1/master
source ../bin/activate
PYTHONPATH=. ../bin/python ../tools/buildbot-helpers/release_sanity.py -u aki -V 14.0b6 --branch mozilla-beta --build-number 1 \
-c release-fennec-mozilla-beta.py --products fennec --dryrun localhost:9001

Got: 

2012-06-05 23:41:12,568 : ERROR : found in mobile/android/config/mozconfigs/android/nightly but not in mobile/android/config/mozconfigs/android/release: ac_add_options --enable-warnings-as-errors
2012-06-05 23:41:12,569 : ERROR : found in mobile/android/config/mozconfigs/android/nightly but not in mobile/android/config/mozconfigs/android/release: ac_add_options --with-ccache=/usr/bin/ccache
2012-06-05 23:41:14,876 : ERROR : found in mobile/xul/config/mozconfigs/android/nightly but not in mobile/xul/config/mozconfigs/android/release: ac_add_options --enable-warnings-as-errors
2012-06-05 23:41:14,877 : ERROR : Error verifying mozconfigs
  • start automation ← monitor progress on buildbot (e.g. beta)
    • the same command as above but without the "--dryrun" and with "-m" to skip the mozconfig check:
PYTHONPATH=. ../bin/python ../tools/buildbot-helpers/release_sanity.py -u aki -V 14.0b6 --branch mozilla-beta --build-number 1 \
-c release-fennec-mozilla-beta.py --products fennec -m localhost:9001

E-mail Metrics

I did this in the Firefox 14.0b6 run.

Tag

First go failed b/c I failed to tag tools.

Fixed, re-ran the sendchange. No problems.

Source

No problems.

Build

Fennec

No problems.

Fennec repacks

No problems.

Android Signing

Instructions in MobileSigning

Now run on signing1.

Did this via 

python26 mozharness/scripts/sign_android.py --cfg signing/android_mozilla-beta.py --platform android --platform android-xul

to get both platforms; I should write a patch.

Later: landed a fix.

Reset reserved slaves

Done.

Going to Beta

NOTE: Skip to "Before Release Day" for beta releases

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

Push the files (for beta releases and release releases)
Play Store (for beta releases and release releases)

IMPORTANT - Make sure to follow instructions!

  • download both multi apks. These have the same name so save them to separate directories.
  • visit https://market.android.com/publish
  • choose "Firefox Beta" or "Firefox"
  • select the "APK Files" tab and choose "Upload APK"
    • choose the android 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"
  • If you're also uploading XUL Fennec, repeat the same steps for the android-xul multilocale apk
  • activate new android apk (You should see an Error message since both apk's are active)
  • deactivate old android apk (You should not see the Error message anymore)
  • If you're also activating XUL Fennec, repeat those steps for the android-xul multilocale apk.
  • 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"
Retrieved from "https://wiki.mozilla.org/index.php?title=Releases/Fennec_14.0b6/BuildNotes&oldid=440030"