Releases/Firefox 10.0.2esr/BuildNotes: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "=Notes About Releasing= Please update the [https://wiki.mozilla.org/index.php?title=Releases/BuildNotesTemplate Notes Template] and the [https://intranet.mozilla.org/Build:Releas...")
 
No edit summary
Line 13: Line 13:
Build 1: [http://hg.mozilla.org/releases/mozilla-esr10/rev/cc9013d9ffc1 cc9013d9ffc1]
Build 1: [http://hg.mozilla.org/releases/mozilla-esr10/rev/cc9013d9ffc1 cc9013d9ffc1]


<font color="red">'''DONE TO HERE'''</font>


=L10N changesets=
=L10N changesets=
[https://wiki.mozilla.org/Release:Release_Automation_on_Mercurial:Documentation#L10N_Changesets Instructions] on how to get them
No milestones, or changes since 10.0.1esr
* Firefox: link to the l10n-changesets
* Fennec: link to the json


=Tags=
=Tags=
Line 26: Line 23:
| style="background:#efefef" | '''Changeset'''
| style="background:#efefef" | '''Changeset'''
|-
|-
| rowspan="2" |  
| rowspan="1" |  
| MOBILE80_#_RELBRANCH, FENNEC_VERSION_RELEASE, FENNEC_VERSION_BUILD1
| GECKO1001_2012020805_RELBRANCH, FIREFOX_10_0_2esr_BUILD1 FIREFOX_10_0_2esr_RELEASE
| [http://hg.mozilla.org/releases/mozilla-beta/rev/# #]
| [http://hg.mozilla.org/releases/mozilla-esr10/rev/# #]
|-
| GECKO80_#_RELBRANCH, FIREFOX_VERSION_BUILD1 FIREFOX_VERSION_RELEASE
| [http://hg.mozilla.org/releases/mozilla-beta/rev/# #]
|}
|}


Line 63: Line 57:


== Fennec ==
== Fennec ==
{| class="fullwidth-table"
N/A
| 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="2" | 1
| android
| rowspan="2" |
|
|
|-
| android-xul
| 
| 
|}


=Notes=
=Notes=
==Build 1==
==Build 1==
===Syncing repos===
(eg: mozilla-beta -> mozilla-release for new Firefox releases)
====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===
===Preparing to start Automation===
* Set clobbers for the appropriate masters. Doing this 24-48 hours in advance should speedup the build.
* set a clobber for "any master", "mozilla-esr10", "any builder" cat
* Reserve slaves
* Reserve slaves already done by 11.0b3
* Update l10n changesets for desktop, mobile
* <strike>Update l10n changesets for desktop, mobile</strike> No changes for a chemspill
* Land automation configs (are you or buildduty going to reconfig? great, merge. otherwise double-land only your configs)
* Land [http://hg.mozilla.org/build/buildbot-configs/rev/24ab6a6fbf3c automation configs]
* Tag buildbot-configs, buildbotcustom, & tools with build & release tags
* Tag buildbot-configs, buildbotcustom, & tools with build & release tags
* update and reconfigure the master
* update and reconfigure the master
* start automation
* ran release_sanity.py dry-run:
* 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>
cd /builds/buildbot/build1/master
source ../bin/activate
PYTHONPATH=. ../bin/python ../tools/buildbot-helpers/release_sanity.py -u nthomas -V 10.0.2esr --branch mozilla-esr10 --build-number 1 -c release-firefox-mozilla-esr10.py --dryrun --products firefox localhost:9001
</pre>
** Complained about the same mozconfig things as 10.0.1. See [[Releases/Firefox_10.0.1/BuildNotes#Preparing_to_start_Automation|the details and explanations]]
** No l10n dashboard entry
*** Ignorable
<font color="red">'''DONE TO HERE'''</font>
** With errors accounted for, started release with --bypass-check:
PYTHONPATH=. ../bin/python ../tools/buildbot-helpers/release_sanity.py -u nthomas -V 10.0.2esr --branch mozilla-esr10 --build-number 1 -c release-firefox-mozilla-esr10.py --bypass-check --products firefox localhost:9001


=== E-mail Metrics ===
=== E-mail Metrics ===
Line 119: Line 103:


=== 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>


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

Revision as of 11:30, 16 February 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 727634

Signed-off Revision(s)

Build 1: cc9013d9ffc1


L10N changesets

No milestones, or changes since 10.0.1esr

Tags

Build # Branch, Tags Changeset
GECKO1001_2012020805_RELBRANCH, FIREFOX_10_0_2esr_BUILD1 FIREFOX_10_0_2esr_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 a clobber for "any master", "mozilla-esr10", "any builder" cat
  • Reserve slaves already done by 11.0b3
  • Update l10n changesets for desktop, mobile No changes for a chemspill
  • Land automation configs
  • Tag buildbot-configs, buildbotcustom, & tools with build & release tags
  • update and reconfigure the master
  • ran release_sanity.py dry-run:
cd /builds/buildbot/build1/master
source ../bin/activate
PYTHONPATH=. ../bin/python ../tools/buildbot-helpers/release_sanity.py -u nthomas -V 10.0.2esr --branch mozilla-esr10 --build-number 1 -c release-firefox-mozilla-esr10.py --dryrun --products firefox localhost:9001

DONE TO HERE

    • With errors accounted for, started release with --bypass-check:
PYTHONPATH=. ../bin/python ../tools/buildbot-helpers/release_sanity.py -u nthomas -V 10.0.2esr --branch mozilla-esr10 --build-number 1 -c release-firefox-mozilla-esr10.py --bypass-check --products firefox localhost:9001

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 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

N/A

Tag

Bouncer Submitter

Source

Start autosign

NOTE: use new signcode keys from d:/2011-keys

Instructions are in CombinedSigning

Build

Firefox

Firefox repacks

Fennec

Fennec repacks

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

NOTE: use new signcode keys from d:/2011-keys and QUIT SIGNCODE when you're done with keymaster

Follow instructions in XULRunner Signing (aut required).

Partner Repack

Firefox

Fennec

Firefox Signing

Android Signing

Instructions in MobileSigning

Now run on signing1.

Android Signature Verification

L10N verify

Checksums

Updates

Update verify

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. 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 Major update documentation.

Major Update verify

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

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

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 release snippets

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

Push files to internal mirrors

Done the day before release OR ASAP for chemspills: Mirrors Policy

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

Push the files
  • Use 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. 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

For major releases or chemspills, update the links on:

Also for older releases:

Push to Release Channel

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

Retrieved from "https://wiki.mozilla.org/index.php?title=Releases/Firefox_10.0.2esr/BuildNotes&oldid=398093"