Releases/Firefox 14.0b8/BuildNotes

From MozillaWiki
< Releases
Revision as of 01:14, 20 June 2012 by NThomas (talk | contribs) (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...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to 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:

Build Engineers

nthomas - Tracking bug: bug 758790

Signed-off Revision(s)

Build 1: 7945471fc07f

L10N changesets

Instructions on how to get them

aki created these milestones.

Tags

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

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

Did you ship the L10n milestone ???

Yes

Set reserved slaves

  • Reserve slaves (you need ~6 each of linux, linux64, win32 (w32), and macosx64 (bld-r5-lion)). Doing this 2-3 hours in advance should speed things up. e.g.:
[cltbld@buildbot-master13 master]$ pwd
/builds/buildbot/build1/master
[cltbld@buildbot-master13 master]$ cat reserved_slaves
6

DONE TO HERE

Preparing to start Automation

detailed instructions

  • Go and make sure that there are L10n milestones for your release. Otherwise create them
  • Set clobbers for the appropriate masters. Doing this 24-48 hours in advance should speedup the build.
  • 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
  • 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. (details)
    • Sample command for Firefox 10.0 beta 5 build 1:
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}
  • update and reconfigure the master

XXX: add notes on how to update the master 

cd /builds/buildbot/build1/master
source ../bin/activate
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u armenzg -V 13.0b1 --branch mozilla-beta --build-number 1 \
    --release-config release-firefox-mozilla-beta.py --release-config release-fennec-mozilla-beta.py --products firefox,fennec  \
    --dryrun localhost:9001
  • start automation ← monitor progress on buildbot (e.g. beta)
    • the same command as above but without the "--dryrun"
  • 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". 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 #metrics.

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 look like this: 

Firefox,firefox,firefox,10.0.3,10.0
Firefox,firefox,firefox,10.0.3esr,10.0

Tag

Bouncer Submitter

Source

Build

Firefox

Firefox repacks

Fennec

Fennec repacks

Unittests / Talos

details

  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

Push to Mirrors

Android Signing

Instructions in Signing: Android Signing

Now run on signing1.

Checksums

Updates

Update verify

Reset reserved slaves

Needs to be reset to 0.

Check permissions / AV scan

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

Push to internal mirrors

Final verification

Record receipt of "completed_final_verification" emails (1 per platform)

Going to Beta

Run backupsnip

NOTE: Remember to do this at least 2 hours ahead of the expected "go to beta" email. details

Remember to ssh to aus3-staging using your short LDAP name and then run sudo su - ffxbld once on. If you intend to use screen, initiate your screen session while you are still yourself.

Push to beta channel

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

Push the files
Play Store

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). You can identify the two build types by
    • Native Fennec (phones) has Supported screens: small-large
    • XUL Fennec (tablets) has Supported screens: xlarge
  • 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.allizom.org/index.php?title=Releases/Firefox_14.0b8/BuildNotes&oldid=443397"