Releases/Firefox 13.0.1/BuildNotes

From MozillaWiki
Jump to: navigation, 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:

  • I started this release thinking that buildbot-master13 was the master to be used
    • this means that reserved_slaves was 0 for this master until just before starting it
  • L10n checks failed:
2012-06-14 11:20:39,654 : INFO : Checking for existence l10n changeset ku af6fed359593 in repo ...
2012-06-14 11:20:39,776 : INFO : Checking for existence l10n changeset sl 9762be720183 in repo ...
2012-06-14 11:20:40,253 : INFO : Comparing l10n changesets on dashboard to on-disk l10n-changesets_mozilla-release ...
2012-06-14 11:20:40,474 : ERROR : cannot find l10n dashboard at
2012-06-14 11:20:40,475 : ERROR : Error verifying l10n dashboard changesets
    • skipping checks and talking with Axel about solution
  • while tagging was happening I decided to make sure we had enough slaves
    • I went and attached 5 mw32 slaves to the master
    • I am worried about cross-colo connections

Build Engineers

{armenzg} - Tracking bug: bug 764179

Signed-off Revision(s)

Build 1: 5bd841d76b3a

L10N changesets

  • Nothing for a .1 release


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

Build # Branch, Tags Changeset
1 GECKO1301_2012061411_RELBRANCH, FIREFOX_13_0_1_BUILD1 FIREFOX_13_0_1_RELEASE f48d675ffa9f

Build data


Build # Type Build ID Build machine Time to build
1 Linux linux-ix-slave39
Linux64 linux64-ix-slave06
Mac moz2-darwin10-slave53
Windows mw32-ix-slave04


Build 1

Set reserved slaves

  • Reserved slaves
[cltbld@buildbot-master12 master]$ pwd
[cltbld@buildbot-master12 master]$ cat reserved_slaves

Preparing to start Automation

detailed instructions

  • Set clobbers for the appropriate masters. Doing this 24-48 hours in advance should speedup the build.
  • For build1 only, create symlinks:
# ffxbld@stage
cd /pub/
mkdir ../candidates/13.0.1-candidates
ln -s ../candidates/13.0.1-candidates 13.0.1-candidates
  • Land automation configs
  • Tag buildbot-configs, buildbotcustom, & tools with build & release tags.
  • update and reconfigure the master
cd /builds/buildbot/build1
source bin/activate
make update && make checkconfig && make reconfig
cd master
PYTHONPATH=. python ../tools/buildbot-helpers/ -u armenzg -V 13.0.1 --branch mozilla-release --build-number 1 \
    --release-config --products firefox  \
    --dryrun localhost:9001
  • failed L10n checks (see bug hit section)
    • no other errors
    • run previous command with -b to skip
  • the same command as above but without the "--dryrun"
  • start automation ← monitor progress on buildbot (e.g. release)

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.



They want to know approximately what time push to external mirrors will occur. Ideally this is a 24hr notice to them, with the estimated time.

Subject: Firefox 13.0.1 coming to mirrors on 15-June-2012
We're planning on pushing our Firefox 13.0.1 release to mirrors a little before 5pm PDT on 15-June-2012.

If you believe these releases or these dates will cause any problems,
please notify release at If you have any problems with mirror
status/weights/etc, please notify mirror-submissions at


No problem.



No problem.

Firefox repacks

No problem.

  • I had to add a bunch of slaves


No problem.


No problem.


No problem.

Push to Mirrors

No problem.

Partner Repack


No problems.


No problems.


No problems.

Update verify

No problems.

Reset reserved slaves


Check permissions / AV scan

No problems.

Push to internal mirrors

  • landed rsync exclude
  • stage shows the change
  • pushed the builder w/o r-d request since chemspilling

Final verification

Record receipt of "completed_final_verification" emails (1 per platform) XXX: TODO Not yet done this section

Run backupsnip

[ffxbld@dp-ausstage01 ~]$ cd /opt/aus2/snippets/staging
[ffxbld@dp-ausstage01 staging]$ ~/bin/backupsnip Firefox-13.0.1-build1

Snippets without WN page

cd /opt/aus2/snippets/staging
rsync -a Firefox-13.0.1-build1-test/ Firefox-13.0.1-build1-test-silent/
rsync -a Firefox-13.0.1-build1/ Firefox-13.0.1-build1-silent/

for f in `find Firefox-13.0.1-build1-test-silent/Firefox/13.0/ -type f`; do 
  echo "actions=silent" >> $f
for f in `find Firefox-13.0.1-build1-silent/Firefox/13.0/ -type f`; do 
  echo "actions=silent" >> $f

~/bin/backupsnip Firefox-13.0.1-build1-test-silent
~/bin/pusnip Firefox-13.0.1-build1-test-silent

Push to external mirrors

  • Remove previously added rsync exclusion from
  • Replace old version with the current one in

Enabling CDN

  • We have set the mirror first to a rating of 10 and then to 50,000

Update XULRunner wiki page

For major releases or chemspills, update the links on:

Also for older releases:

Check Throttling

See for example AUS links

XXX: TODO: What do I do with this section?

Some links to check:

Push to Release Channel

[ffxbld@dp-ausstage01 ~]$ cd /opt/aus2/snippets/staging
[ffxbld@dp-ausstage01 staging]$ ~/bin/pushsnip Firefox-13.0.1-build1-silent

Ask IT to update AUS for unthrottling

Update symlinks

Once we're signed off on the release channel.

# ffxbld@stage
cd /pub/
rm latest && ln -s 13.0.1 latest

Reduced CDN

  • armenzg reduced the CDN from 50k to 35k since we were over 70K already
  • nthomas found the European mirrors didn't have the update/win32 or win32/ directories, because the main distribution point there ( was getting very slow transfer from pv-mirror01, bug 765441. We had only 70K uptake with the CDN on, and couldn't turn it off in that state. IT adjusted the geo-ip so that requests to releases-rsync from Europe went to (the North American primary) instead of openap. Uptake increased to 100K and the CDN was turned off

Update browser choice website

bug 765400