Releases/Firefox 12.0b4/BuildNotes

From MozillaWiki
Jump to: navigation, search

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 742129 - hg.m.o web access down (server side 500 errors) 3-1/2 hour delay in start

Build Engineers

{hwine} - Tracking bug: bug 735388

Signed-off Revision(s)

Build 1: e4ed83ba6eb9

L10N changesets

Instructions on how to get them

Tags

Build # Branch, Tags Changeset
1 MOBILE120_2012040320_RELBRANCH FENNEC_12_0b4_BUILD1 FENNEC_12_0b4_RELEASE 375c1e5fbbc3
GECKO120_2012040320_RELBRANCH FIREFOX_12_0b4_BUILD1 FIREFOX_12_0b4_RELEASE 9bfe6330d055

Build data

Firefox

Build # Type Build ID Build machine Time to build
1 Linux 20120403211507 mv-moz2-linux-ix-slave11 1 hrs, 4 mins, 8 secs
Linux64 linux64-ix-slave05 1 hrs, 12 mins, 50 secs
Mac moz2-darwin10-slave17 3 hrs, 33 mins, 12 secs
Windows mw32-ix-slave12 3 hrs, 22 mins, 32 secs

Fennec

Build # Type Build ID Build machine Time to build
1 android-xul 20120403204709 mv-moz2-linux-ix-slave19 49 mins, 54 secs

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 done
  • start automation done
  • reconfigure other masters not needed

E-mail Metrics

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

For 12.0b4 it would be done

Firefox,firefox,firefox,12.0b4,12.0
Fennec,firefox-mobile,fennec,12.0b4,12.0

Edit rsync exclude files

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

Tag

no problems

Bouncer Submitter

no problems

Source

no problem

Start autosign

[not applicable]

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

Build

no problems

Firefox

no problems

Firefox repacks

no problems

Fennec

no problems

Fennec repacks

no problems

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

No problems

Source

No problems

Build

No problems

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

No problems

Partner Repack

n/a for beta

Firefox Signing

No problems

Android Signing

Instructions in MobileSigning. No problems.

L10N verify

No problems


Checksums

No problems

Updates

No problems

Update verify

No problems

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

Check permissions / AV scan

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

No problems reported

Push to internal mirrors

This is done by automation for rapid release betas.

No problems

Going to Beta

Run backupsnip

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

Not done for 12.0b4 due to timing

Push to beta

No problems

Final verification

No problems - final verification received for win32, linux, linux64, & macos64

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)

done, no problems

Android Market

IMPORTANT - Make sure to follow instructions!

  • download multi apk (e.g. multi/fennec-12.0b4.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), so use FF ;)
    • 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"

No problems