Releases/Thunderbird 13.0b3/BuildNotes
< Releases
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
Build Engineers
rail - Tracking bug: bug 744605
Signed-off Revision(s)
Build 1:
- comm-beta:
- mozilla-beta:
L10N changesets
Instructions on how to get them
Tags
Manually tag the automation code, then record the generated tags below. (details)
buildbot-configs:
- THUNDERBIRD_13_0b3_BUILD1
- THUNDERBIRD_13_0b3_RELEASE
buildbotcustom:
- THUNDERBIRD_13_0b3_RELEASE
- THUNDERBIRD_13_0b3_BUILD1
tools:
- THUNDERBIRD_13_0b3_RELEASE
- THUNDERBIRD_13_0b3_BUILD1
Build data
Thunderbird
Build # | Type | Build ID | Build machine | Time to build |
1 | Linux | |||
Linux64 | ||||
Mac | ||||
Windows |
Notes
Build 1
Preparing to start Automation
- Set clobbers for the appropriate masters. Doing this 24-48 hours in advance should speedup the build.
- Reserve slaves
[cltbld@buildbot-master34 master]$ echo "10" > /builds/buildbot/build1/master/reserved_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)
# tbirdbld@stage cd /pub/mozilla.org/thunderbird/nightly/ mkdir ../candidates/13.0b3-candidates ln -s ../candidates/13.0b3-candidates 13.0b3-candidates
- Update l10n changesets for desktop, mobile
- Instructions on how to get them
- dashboard
- Land automation configs (are you or buildduty going to reconfig? great, merge. otherwise double-land only your configs)
- Tag buildbot-configs, buildbotcustom, & tools with build & release tags. (details)
- hg tag THUNDERBIRD_13_0b3_{RELEASE,BUILD1}
- update and reconfigure the master
# removed all local changes cd /builds/buildbot/build1 make update && make checkconfig && python buildbot-wrangler.py reconfig `pwd`/master
- start automation
cd /builds/buildbot/build1 source bin/activate buildbot sendchange --username=rail --master localhost:9001 --branch=releases/comm-beta \ --comments "THUNDERBIRD 13.0b3 BUILD 1" -p products:thunderbird \ -p script_repo_revision:THUNDERBIRD_13_0b3_BUILD1 release_build
- start automation ← monitor progress on buildbot (e.g. release-comm-beta)
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.0b3,13.0
Tag
Bouncer Submitter
Source
Build
Thunderbird
Thunderbird repacks
Thunderbird Signing
VERSION=13.0b3 BUILD=1 TAG=THUNDERBIRD_13_0b3_RELEASE REPO=releases/comm-beta PRODUCT=thunderbird APP_NAME=mail EMAIL=release@mozilla.com KEYDIR=d:/2011-keys RELCONFIG=fake STAGE_HOST=stage.mozilla.org STAGE_USERNAME=tbirdbld SSH_KEY=$HOME/.ssh/tbirdbld_dsa cd ${HOME}/hg-tools/ # if it exists, otherwise create a fresh clone hg pull && hg up -r ${TAG} mkdir -p ~/signing-work/${PRODUCT}-${VERSION}/lib/python cd ~/signing-work/${PRODUCT}-${VERSION} cp ~/hg-tools/release/signing/* . rsync -av ~/hg-tools/lib/python/ ./lib/python/ make tb-all PRODUCT=${PRODUCT} VERSION=${VERSION} \ BUILD=${BUILD} REPO=${REPO} EMAIL=${EMAIL} \ KEYDIR=${KEYDIR} RELCONFIG=${RELCONFIG} \ APP_NAME=$APP_NAME TAG=$TAG \ STAGE_USERNAME=$STAGE_USERNAME \ STAGE_HOST=$STAGE_HOST SSH_KEY=$SSH_KEY make postsign PRODUCT=${PRODUCT} VERSION=${VERSION} \ BUILD=${BUILD} REPO=${REPO} EMAIL=${EMAIL} \ KEYDIR=${KEYDIR} RELCONFIG=${RELCONFIG} \ APP_NAME=$APP_NAME TAG=$TAG \ STAGE_USERNAME=$STAGE_USERNAME \ STAGE_HOST=$STAGE_HOST SSH_KEY=$SSH_KEY