Releases/Firefox 11.0b7/BuildNotes: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 96: Line 96:
   -pfirefox -V 11.0b7 --branch mozilla-beta --build-number 1  \
   -pfirefox -V 11.0b7 --branch mozilla-beta --build-number 1  \
   -c release-firefox-mozilla-beta.py  localhost:9001
   -c release-firefox-mozilla-beta.py  localhost:9001
'''<font color='red'>DONE TO HERE</font>'''


=== E-mail Metrics ===
=== E-mail Metrics ===
Use the address "metrics-alerts < AT > mozilla < PERIOD > org"
Use the address "metrics-alerts < AT > mozilla < PERIOD > org"
 
  Firefox,firefox,firefox,11.0b7,11.0
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 have "esr" appended to their major branch, so a 10.0.1esr would look as follows:
Firefox,firefox,firefox,10.0.1esr,10.0esr


=== E-mail mirrors@mozilla.org ===
=== E-mail mirrors@mozilla.org ===
Not necessary for rapid release betas, files only go as far as the 'internal mirrors'.
N/A
 
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>
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 ===
=== Edit rsync exclude files ===
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.
N/A
 
For rapid release betas, this is not necessary as there's already an exclude that matches beta releases.


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


=== Bouncer Submitter ===
=== Bouncer Submitter ===


=== Source ===
=== Source ===


=== Start autosign ===
=== Start autosign ===
NOTE: use new signcode keys from d:/2011-keys
N/A
 
Instructions are in [https://intranet.mozilla.org/RelEngWiki/index.php/Signing#.22autosign.22.2C_used_for_Firefox_3.6.x.2C_10.0.x.2C_and_10.0.x_ESR Signing]


=== Build ===
=== Build ===
Line 161: Line 122:


==== Fennec ====
==== Fennec ====
 
N/A
===== Fennec repacks =====
===== Fennec repacks =====
N/A


=== Unittests / Talos ===
=== Unittests / Talos ===
Line 176: Line 138:


====Signing====
====Signing====
NOTE: use new signcode keys from d:/2011-keys and QUIT SIGNCODE when you're done with keymaster
N/A, done at build time.
 
Follow instructions in [https://intranet.mozilla.org/Build:CombinedSigning#XULRunner_Signing XULRunner Signing] (aut required).


=== Partner Repack ===
=== Partner Repack ===
==== Firefox ====
N/A
==== Fennec ====
 
=== Firefox Signing ===
=== Firefox Signing ===
 
N/A


=== Android Signing ===
=== Android Signing ===
Instructions in [https://intranet.mozilla.org/Build:MobileSigning MobileSigning]
N/A


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


=== Checksums ===
=== Checksums ===
Line 201: Line 157:


=== Major Update ===
=== Major Update ===
Major update generation is not kicked off automatically. You should only create them once the final builds for the "latest" build are ready.
N/A
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.
 
==== Major Update verify ====


=== Reset reserved slaves ===
=== Reset reserved slaves ===
This is also a good time to QUIT SIGNCODE on keymaster if you've still got it running.


=== Check permissions / AV scan ===
=== Check permissions / AV scan ===
Line 217: Line 167:
=== 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]


=== Going to Beta ===
=== Going to Beta ===
Line 233: Line 177:
Assuming this is not a chemspill.
Assuming this is not a chemspill.


==== Run backupsnip for release snippets ====
==== Run backupsnip for beta snippets ====
Do this the night before release day as it can take up to two hours.
Do this the night before release day as it can take up to two hours.


Line 246: Line 190:
=== Release Day ===
=== Release Day ===
==== Publish Fennec to the Android Market ====
==== Publish Fennec to the Android Market ====
=====Push the files=====
N/A
* 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)
 
=====Android Market=====
'''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 ====
====Push XULRunner to Mirrors ====
Line 277: Line 204:


==== Push to Release Channel ====
==== Push to Release Channel ====
Once there is enough uptake and we get "go" from release driver.
N/A


==== Update symlinks ====
==== Update symlinks ====
Once we're signed off on the release channel.
N/A
 
===== Remove index.html files =====
===== Remove index.html files =====
If you created them earlier to hide the release.
N/A


==== Update browser choice website ====
==== Update browser choice website ====
N/A

Revision as of 00:00, 9 March 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:

Build Engineers

nthomas - Tracking bug: bug 734260

Signed-off Revision(s)

Build 1: ff5f2055aba4

Only building Firefox this time.

L10N changesets

Instructions on how to get them

Tags

Build # Branch, Tags Changeset
1 MOBILE80_#_RELBRANCH, FENNEC_VERSION_RELEASE, FENNEC_VERSION_BUILD1 N/A
GECKO80_#_RELBRANCH, FIREFOX_10_0b7_BUILD1 FIREFOX_10_0b7_RELEASE #

Build data

Firefox

Build # Type Build ID Build machine Time to build
1 Linux
Linux64
Mac
Windows

Fennec

N/A

Notes

Build 1

Preparing to start Automation

  • Set clobbers for any master, mozilla-beta, and any builder
  • 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/11.0b7-candidates
ln -s ../candidates/11.0b7-candidates 11.0b7-candidates
  • hit 'Ship it' on 'Firefox 11 Beta Build 7' milestone and updated l10n changesets for desktop
  • Double landed automation configs
  • Tag buildbot-configs, buildbotcustom, & tools with build & release tags.
hg tag FIREFOX_11_0b7_RELEASE FIREFOX_11_0b7_BUILD1
  • update and reconfigure the master
  • start automation (NB: normally have Fennec in here too, see 11.0b6 notes)
cd /builds/buildbot/build1/master
source ../bin/activate
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u nthomas \
 -pfirefox -V 11.0b7 --branch mozilla-beta --build-number 1 \
 -c release-firefox-mozilla-beta.py   --dryrun localhost:9001

PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u nthomas \
 -pfirefox -V 11.0b7 --branch mozilla-beta --build-number 1  \
 -c release-firefox-mozilla-beta.py  localhost:9001

E-mail Metrics

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

Firefox,firefox,firefox,11.0b7,11.0

E-mail mirrors@mozilla.org

N/A

Edit rsync exclude files

N/A

Tag

Bouncer Submitter

Source

Start autosign

N/A

Build

Firefox

Firefox repacks

Fennec

N/A

Fennec repacks

N/A

Unittests / Talos

  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

Build

Signing

N/A, done at build time.

Partner Repack

N/A

Firefox Signing

N/A

Android Signing

N/A

L10N verify

Checksums

Updates

Update verify

Major Update

N/A

Reset reserved slaves

Check permissions / AV scan

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

Push to internal mirrors

This is done by automation for rapid release betas.

Going to Beta

Run backupsnip

NOTE: Remember to do this at least an hour ahead of the expected "go to beta" email.

Push to beta

Before Release Day

Assuming this is not a chemspill.

Run backupsnip for beta snippets

Do this the night before release day as it can take up to two hours.

Final verification

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

Release Day

Publish Fennec to the Android Market

N/A

Push XULRunner to Mirrors

Update XULRunner wiki page

For major releases or chemspills, update the links on:

Also for older releases:

Push to Release Channel

N/A

Update symlinks

N/A

Remove index.html files

N/A

Update browser choice website

N/A

Retrieved from "https://wiki.allizom.org/index.php?title=Releases/Firefox_11.0b7/BuildNotes&oldid=405620"