Releases/Firefox 13.0b7/BuildNotes

From MozillaWiki
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

{catlee} - Tracking bug: bug 760219

Signed-off Revision(s)

Build 1: b8b0ed817c31

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 GECKO130_2012053115_RELBRANCH, FIREFOX_13_0b7_BUILD1 FIREFOX_13_0b7_RELEASE b8b0ed817c31

Build data

Firefox

Build # Type Build ID Build machine Time to build
1 Linux 20120531155942 linux-ix-slave14 1 hrs, 7 mins, 8 secs
Linux64 linux64-ix-slave21 1 hrs, 5 mins, 50 secs
Mac moz2-darwin10-slave42 3 hrs, 21 mins, 10 secs
Windows mw32-ix-slave13 3 hrs, 30 mins, 34 secs


Notes

Build 1

Preparing to start Automation

  • Set clobbers for release-mozilla-beta on all masters
  • Set reserved slaves on bm13:
[cltbld@buildbot-master13 master]$ pwd
/builds/buildbot/build1/master
[cltbld@buildbot-master13 master]$ cat reserved_slaves
5
  • Create candidates link:
# ffxbld@stage
cd /pub/mozilla.org/firefox/nightly/
mkdir ../candidates/13.0b7-candidates
ln -s ../candidates/13.0b7-candidates 13.0b7-candidates
  • Tag buildbot-configs, buildbotcustom, & tools with build & release tags. (details)
hg tag -f FIREFOX_13_0b7_RELEASE FIREFOX_13_0b7_BUILD1
  • update and reconfigure the master
cd /builds/buildbot/build1/master
source ../bin/activate
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u catlee -V 13.0b7 --branch mozilla-beta --build-number 1 \
    --release-config release-firefox-mozilla-beta.py --products firefox --dryrun localhost:9001
  • start automation
    • the same command as above but without the "--dryrun"

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.0b7,13.0

Tag -> Ready for release

All automated; no problems \o/

DONE TO HERE

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.

Release Day

Push the files (for beta releases and release releases)

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.

Retrieved from "https://wiki.mozilla.org/index.php?title=Releases/Firefox_13.0b7/BuildNotes&oldid=436557"