Releases/Thunderbird 13.0/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:

  • bug 760807 - Program Compatibility Assistant shown on Windows 7 when setting as default mail client
  • bug 760624 - Changed Hover.com password results in Thunderbird saying that there is a network problem

Other problems/annoyances:

  • forced release_sanity.py to run. See bug 763769
  • Need updated documentation on rebuilding a platform?
    • Before rebuilding build1 win32, I had to manually remove win32/ updates/win32, win32_info.txt from stage.
    • Because updates has already been generated by the first build1, we had to revert the patcher bumps in CVS and Mercurial (because the build IDs changed?).
  • bug 762152 - MD5 and SHA1 Hashes Invalid on FTP Mirrors for Thunderbird 13.0

Build Engineers

{jhopkins} - Tracking bug: bug 744598

Signed-off Revision(s)

Build 1: comm-release: https://hg.mozilla.org/releases/comm-release/rev/b43356d5b161 mozilla-release: http://hg.mozilla.org/releases/mozilla-release/rev/2b643ea8edf9

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
THUNDERBIRD_13_0_RELEASE THUNDERBIRD_13_0_BUILD1 https://hg.mozilla.org/build/buildbot-configs/rev/0ef8b61fb6f1 https://hg.mozilla.org/build/buildbotcustom/rev/bb42182b9b96 https://hg.mozilla.org/build/tools/rev/78d117e9fbe4

Notes

Build 1

Preparing to start Automation

detailed instructions

  • No clobber possible as this is the first Thunderbird release build on Firefox infra.
  • Did not reserve any slaves.
  • For 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, or tbirdbld and use thunderbird in path
cd /pub/mozilla.org/thunderbird/nightly/
mkdir ../candidates/$version-candidates
ln -s ../candidates/$version-candidates $version-candidates
  • Update l10n changesets for desktop, mobile
  • Land automation configs (are you or buildduty going to reconfig? great, merge. otherwise double-land only your configs)
  • Tagged buildbot-configs, buildbotcustom, & tools with build & release tags.
  • update and reconfigure the master

XXX: add notes on how to update the master 

# on buildbot-master34
cd /builds/buildbot/build1/master
source ../bin/activate
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u jhopkins -V 13.0 --branch comm-release --build-number 1 \
    --release-config release-thunderbird-comm-release.py --release-config --products thunderbird  \
    --dryrun localhost:9001
  • release_sanity failed on mozconfig differences but passed otherwise. Forced sendchange with -b flag.
12-06-01 09:21:55,854 : INFO : Comparing thunderbird mozconfigs to nightly mozconfigs...
2012-06-01 09:21:59,713 : ERROR : found in mail/config/mozconfigs/macosx-universal/release but not in mail/config/mozconfigs/macosx-universal/nightly: mk_add_options CLIENT_PY_ARGS="--hg-options='--verbose --time' --hgtool=../tools/buildfarm/utils/hgtool.py --skip-chatzilla --skip-comm --skip-inspector --skip-venkman --tinderbox-print --comm-rev=${COMM_REV} --mozilla-rev=${MOZILLA_REV}"
2012-06-01 09:21:59,713 : WARNING : mk_add_options CLIENT_PY_ARGS="--hg-options='--verbose --time' --hgtool=../tools/buildfarm/utils/hgtool.py --skip-chatzilla --skip-comm --skip-inspector --skip-venkman --tinderbox-print" not in macosx64 ['ac_add_options --enable-update-channel=nightly', 'ac_add_options --with-macbundlename-prefix=Firefox', 'ac_add_options --enable-codesighs', 'mk_add_options MOZ_MAKE_FLAGS="-j4"', 'ac_add_options --enable-signmar', 'ac_add_options --enable-js-diagnostics', 'ac_add_options --disable-install-strip']!
    • 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. 

Thunderbird,thunderbird,thunderbird,13.0,13.0

E-mail mirrors@mozilla.org

Not necessary for rapid release betas or ESR builds, as the files only go as far as the 'internal mirrors'.

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: Thunderbird 13.0 coming to mirrors on {DATE}
Body:
We're planning on pushing our Thunderbird 13.0 release to mirrors 24 hours before {DATE}.
# If this is a chemspill, please mention that in the email as it will mean pinging 
# for CDN to be enabled when the push to internal mirrors happens

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.

Edit rsync exclude files

After getting svn setup (auth req'd) edit files/rsync/rsyncd-mozilla-releases.exclude so that it excludes the current release, get review and deploy. This prevents external mirrors from picking up the new release prematurely.

For rapid release betas and ESR builds, this is not necessary as there's already an exclude that matches them.

Checksums

  • Checksums files were from build1 spin 1. Had to rebuild checksums builder and push the checksums files to /releases/
cd /pub/mozilla.org/thunderbird/candidates/13.0-candidates/build1
rsync -avn *SUMS* ../../../releases/13.0/

Updates

Run backupsnip

$ backupsnip Thunderbird-13.0

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

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/Thunderbird_13.0/BuildNotes&oldid=450508"