Releases/Firefox 13.0b3/BuildNotes

From MozillaWiki
< Releases
Revision as of 02:55, 9 May 2012 by Hwine (talk | contribs) (update timings)
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:

  • bug 753172 - needed to steal darwin10 slaves for the duration
  • bug 753053 - missing symlinks on build master for l10n configs

Build Engineers

{hwine} - Tracking bug: bug 744592

Signed-off Revision(s)

Build 1: aa323b98df36

L10N changesets

Instructions on how to get them

Tags

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

Build # Branch, Tags Changeset
1 MOBILE130_2012050817_RELBRANCH, FENNEC_13_0b3_RELEASE FENNEC_13_0b3_BUILD1 64ffbdd90ac0
GECKO130_2012050817_RELBRANCH, FIREFOX_13_0b3_RELEASE FIREFOX_13_0b3_BUILD1 4f3991db9f8b

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 20120508174549 n/a n/a
android-xul linux-ix-slave15 47 mins, 22 secs

Notes

Build 1

Preparing to start Automation

detailed instructions

  • Set clobbers for the appropriate masters. Doing this 24-48 hours in advance should speedup the build.
  • 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/$version-candidates
ln -s ../candidates/$version-candidates $version-candidates
  • Update l10n changesets for desktop, mobile
  • double-landed automation configs
  • Tag buildbot-configs, buildbotcustom, & tools with build & release tags. (details)
 hg tag -f {FIREFOX,FENNEC}_13_0b3_{RELEASE,BUILD1}
  • updated and reconfigure the master via fabric
cd /builds/buildbot/build1/master
source ../bin/activate
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py --dryrun \
    -u hwine -V 13.0b3 --branch mozilla-beta --build-number 1 \
    -c release-firefox-mozilla-beta.py -c release-fennec-mozilla-beta.py \
    --products firefox,fennec localhost:9001
  • start automation ← monitor progress on buildbot (e.g. beta)
    • the same command as above but without the "--dryrun"

E-mail Metrics

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

   Firefox,firefox,firefox,13.0b3,13.0
   Fennec,firefox-mobile,fennec,13.0b3,13.0

Tag

OK

Bouncer Submitter

OK

Source

OK

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

Partner Repack

Firefox

Fennec

Android Signing

Instructions in MobileSigning

Now run on signing1.

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

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

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.

Mirrors Policy

Final verification

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

Going to Beta

NOTE: Skip to "Before Release Day" for beta releases

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

Wait for "go" from release managers
For Firefox:

  • Publish (and record run time here): details
  • on completion, email r-d that VERSION updates are live on the beta channel

For Android:

  • publish on Google Play (nee Android Marketplace), using instructions below
  • on completions, email r-d that VERSION is live on Google Play

Wait for confirmation from QA that each of the above releases is okay, then close the tracking ticket.

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

  • Remove previously added blacklisting entry from stage.mozilla.org:/pub/mozilla.org/zz/rsyncd-mozilla-releases.exclude
  • Replace old version with the current one in stage.mozilla.org:/pub/mozilla.org/zz/rsyncd-mozilla-current.exclude

See details

Release Day

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

Push the files (for beta releases and release releases)
Play Store (for beta releases and release releases)

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:

Check Throttling

See http://update-watch.localgho.st/release/ for example AUS links

Some links to check:

Push to Release Channel (for beta releases and release releases)

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_13.0b3/BuildNotes&oldid=428886"