MozillaWiki

Releases/Firefox 12.0b4/BuildNotes

< Releases
Revision as of 01:07, 4 April 2012 by Hwine (talk | contribs) (→‎Preparing to start Automation)

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

{hwine} - Tracking bug: bug 735388

Signed-off Revision(s)

Build 1: #

L10N changesets

Instructions on how to get them

  • Firefox: link to the l10n-changesets
  • Fennec: link to the json

Tags

Build # Branch, Tags Changeset
MOBILE80_#_RELBRANCH, FENNEC_VERSION_RELEASE, FENNEC_VERSION_BUILD1 #
GECKO80_#_RELBRANCH, FIREFOX_VERSION_BUILD1 FIREFOX_VERSION_RELEASE #

Build data

Firefox

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

Fennec

Build # Type Build ID Build machine Time to build
1 android
android-xul

Notes

Build 1

Preparing to start Automation

  • clobbered Any Master, mozilla-beta, Any builder at 20120403 1502PT
  • Reserved 8 slaves
  • For build1 only:
[ffxbld@surf nightly]$ cd /pub/mozilla.org/firefox/nightly/
[ffxbld@surf nightly]$ mkdir ../candidates/12.0b4-candidates
[ffxbld@surf nightly]$ ln -s ../candidates/12.0b4-candidates .
[ffxbld@surf nightly]$ ls -l 12.0b4-candidates
lrwxrwxrwx 1 ffxbld firefox 31 Apr  3 15:26 12.0b4-candidates -> ../candidates/12.0b4-candidates
[ffxbld@surf nightly]$
  • Update l10n changesets for desktop, mobile done
  • Land automation configs double landed'
  • Tag buildbot-configs, buildbotcustom, & tools with build & release tags. done
  • update and reconfigure the master
  • start automation
  • reconfigure other masters (or ask the buildduty person to do this) if you have done a merge (and not double-land) to production

E-mail Metrics

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

For 9.0b2 it would be 

Firefox,firefox,firefox,9.0b2,9.0
Fennec,firefox-mobile,fennec,9.0b2,9.0

Edit rsync exclude files

For rapid release betas, this is not necessary as there's already an exclude that matches beta releases.

Tag

Bouncer Submitter

Source

Start autosign

[not applicable]

  1. NOTE: use new signcode keys from d:/2011-keys
  1. Instructions are in Signing

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

  1. NOTE: use new signcode keys from d:/2011-keys and QUIT SIGNCODE when you're done with keymaster
  1. Follow instructions in XULRunner Signing (aut required).

Partner Repack

Firefox

Fennec

Firefox Signing

Android Signing

Instructions in MobileSigning

Now run on signing1.

L10N verify

Checksums

Updates

Update verify

Major Update

[not applicable]

Major Update verify

[not applicable]

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.

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

Release Day

Publish Fennec to the Android Market

Push the files
  • Use this script and run it as ffxbld@stage (please push your 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"
Retrieved from "https://wiki.allizom.org/index.php?title=Releases/Firefox_12.0b4/BuildNotes&oldid=416007"