MozillaWiki

Releases/Firefox 13.0b6/BuildNotes

< Releases
Revision as of 14:04, 29 May 2012 by Armenzg (talk | contribs) (→‎Bugs hit)

Notes About Releasing

Bugs hit

Enter any bugs pre-existing or newly discovered and filed during the release:

  • no L10n milestone. I took no L10n changes
  • change l10n-stage-sj.mozilla.org for l10n.mozilla.org in documentation
  • I had to lock few extra darwin10 slaves since there were 4 attached but only 2 ssheable to start the mac builds (xulrunner was picked up first)
  • One of the mac repacks failed around Mon May 28 23:26:41 2012
remoteFailed: [Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionLost'>: Connection to the other side was lost in a non-clean fashion.

Build Engineers

armenzg - Tracking bug: bug 744595

Signed-off Revision(s)

Build 1: 046e86aee0c1

L10N changesets

Instructions on how to get them

  • Firefox: no milestone. I took no L10n changes

Tags

Manually tag the automation code, then record the generated tags below. (details) XXX: Verify the branch name

Build # Branch, Tags Changeset
GECKO130_#_RELBRANCH, FIREFOX_13_0b6_BUILD1 FIREFOX_13_0b6_RELEASE 046e86aee0c1

Build data

Firefox

XXX: Fill this data

Build # Type Build ID Build machine Time to build
1 Linux linux-ix-slave28
Linux64 linux64-ix-slave21
Mac
Windows w32-ix-slave37

Notes

Build 1

Preparing to start Automation

  • Set clobbers for the appropriate masters.
  • Reserve slaves (you need ~5 each of linux, linux64, win32 (w32), and macosx64 (moz2-darwin10)). Doing this 2-3 hours in advance should speed things up. e.g.:
[cltbld@buildbot-master13 master]$ echo 8 > /builds/buildbot/build1/master/reserved_slaves
  • For Firefox 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/13.0b6-candidates
ln -s ../candidates/13.0b6-candidates 13.0b6-candidates
  • Update l10n changesets for desktop
  • Land automation 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_13_0b6_RELEASE FIREFOX_13_0b6_BUILD1
  • update and reconfigure the master
cd /builds/buildbot/build1/master
source ../bin/activate
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u armenzg -V 13.0b6 --branch mozilla-beta --build-number 1 \
    --release-config release-firefox-mozilla-beta.py --products firefox  \
    --dryrun localhost:9001
  • start automation ← monitor progress on buildbot (e.g. beta)
    • the same command as above but without the "--dryrun"
    • I had to run with -b to skip checking for the L10n dashboard

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. 

Firefox,firefox,firefox,13.0b6,13.0

DONE TO HERE

Tag

No problems.

Bouncer Submitter

No problems.

Source

No problems.

Build

Firefox

No problems.

Firefox 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

No problems.

Source

No problems.

Build

No problems.

Android Signing

Instructions in MobileSigning

Now run on signing1.

Checksums

Updates

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

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.allizom.org/index.php?title=Releases/Firefox_13.0b6/BuildNotes&oldid=435040"