Releases/Firefox 13.0b7/BuildNotes
Contents
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 - description
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
- Update l10n changesets for desktop, mobile : No changes.
- Instructions on how to get them
- dashboard
- Landed configs: default production
- 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/
Reset reserved_slaves to 0
Going to Beta
Run backupsnip
backupsnip Firefox-13.0b7-build1
Push to beta
Wait for "go" from release managers
For Firefox:
- Publish (and record run time here):
pushsnip Firefox-13.0b7-build1 cat Firefox-13.0b7-build1.time real 285.03 user 1.70 sys 5.44
Wait for confirmation from QA that each of the above releases is okay, then close the tracking ticket.
Release Day
Push XULRunner to Mirrors
Update XULRunner wiki page
For major releases or chemspills, update the links on:
Also for older releases:
- https://developer.mozilla.org/en/XULRunner_1.9.2_Release_Notes
- https://developer.mozilla.org/en/Gecko_SDK
Check Throttling
See http://update-watch.localgho.st/release/ for example AUS links
Some links to check:
- Automatic (idle time check) update links:
- Manual update links:
Push to Release Channel (for beta releases and release releases)
Once there is enough uptake and we get "go" from release driver.