Releases/Firefox 13.0.2/BuildNotes

Notes About Releasing

Please update the Notes Template and the Release:Primer for future releases (bug fixes, changes to automation) as needed

Build Engineers

{hwine,rail} - Tracking bug: bug 767612

Signed-off Revision(s)

Build 1: d1af5c5c14be

L10N changesets

• Nothing for a .2 release

Tags

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

Build #	Branch, Tags	Changeset
1	GECKO1302_2012062310_RELBRANCH FIREFOX_13_0_2_BUILD1 FIREFOX_13_0_2_RELEASE	62023e1a4c37

Build data

Firefox

Build #	Type	Build ID	Build machine	Time to build
1	Linux
	Linux64
	Mac
	Windows

Notes

Build 1

Set reserved slaves

• Reserved slaves

[cltbld@buildbot-master12 ~]$ echo "8" > /builds/buildbot/build1/master/reserved_slaves #rail
[cltbld@buildbot-master12 master]$ pwd
/builds/buildbot/build1/master
[cltbld@buildbot-master12 master]$ cat reserved_slaves
8

Preparing to start Automation

detailed instructions

• Set clobbers for the appropriate masters. Doing this 24-48 hours in advance should speedup the build.
  • clobberer
• For build1 only, create symlinks:
• Created candidates directory:

 # ffxbld@stage, 
 version=13.0.2
 cd /pub/mozilla.org/firefox/nightly/
 mkdir ../candidates/$version-candidates
 ln -s ../candidates/$version-candidates $version-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/release_sanity.py -u hwine  \
    -V 13.0.2 --branch mozilla-release --build-number 1 \
    --release-config release-firefox-mozilla-release.py --products firefox  \
    --l10n-dashboard-version=13 \
    --dryrun localhost:9001

• As expected, above complained about missing mn & sw locales, so final run included -l switch to skip checks

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

Firefox,firefox,firefox,13.0.2,13.0

done

E-mail mirrors@mozilla.org

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.2 coming to mirrors on 24-June-2012
Body:
We're planning on pushing our Firefox 13.0.2 release to mirrors a little before 5pm PDT on 24-June-2012.

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

Source

done

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.2-build1-test/ Firefox-13.0.2-build1-test-silent/
rsync -a Firefox-13.0.2-build1/ Firefox-13.0.2-build1-silent/

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

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

Push to external mirrors

• Remove previously added rsync exclusion 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

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:

• https://developer.mozilla.org/en/XULRunner
• https://developer.mozilla.org/en/Gecko_SDK

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://people.mozilla.com/~nthomas/update-watch/release/ for example AUS links

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

Some links to check:

• Automatic (idle time check) update links:
  • 10.0.2 en-US win32 linux mac linux64
  • 9.0 en-US win32 linux mac linux64
  • 10.0.2esr en-US win32 linux mac linux64
  • 10.0esr en-US win32 linux mac linux64
  • 3.6.27 en-US win32 linux mac
• Manual update links:
  • 10.0.2 en-US win32 linux mac linux64
  • 9.0 en-US win32 linux mac linux64
  • 10.0.2esr en-US win32 linux mac linux64
  • 10.0esr en-US win32 linux mac linux64
  • 3.6.27 en-US win32 linux mac

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

• bug 765370

Update symlinks

Once we're signed off on the release channel.

# ffxbld@stage
cd /pub/mozilla.org/firefox/releases
rm latest && ln -s 13.0.2 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 (mozilla.openap.net) 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 anynymirror101.mirrors.tds.net (the North American primary) instead of openap. Uptake increased to 100K and the CDN was turned off

Update browser choice website

bug