Releases/Thunderbird 17.0.3/BuildNotes
Contents
Build 1
Checklist
-
Submit to Ship It DESKTOP MOBILE RELEASE BETA ESR - Push to mirrors DESKTOP RELEASE
- Run pushsnip DESKTOP RELEASE BETA ESR
- Post-release tasks DESKTOP RELEASE BETA ESR
Notes
- Submitted to ship it.
- Coop reviewed and marked as ready.
Update the correct config
Because of bug 815302 we updated the wrong release config. To fix:
- bumped the config by hand in https://bugzilla.mozilla.org/attachment.cgi?id=714542&action=edit.
- landed and retagged with THUNDERBIRD_17_0_3_{RELEASE,BUILD1}
- ran release sanity:
# cltbld@buildbot-master36 cd /builds/buildbot/build_scheduler/master source ../bin/activate PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u bhearsum -V 17.0.3 --branch comm-esr17 --build-number 1 --release-config release-thunderbird-comm-release.py --skip-reconfig --bypass-l10n-dashboard-check --bypass-check localhost:9301
- reconfiged the build + scheduler masters by hand
- reran release sanity to start the release:
# cltbld@buildbot-master36 cd /builds/buildbot/build_scheduler/master source ../bin/activate PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u bhearsum -V 17.0.3 --branch comm-esr17 --build-number 1 --release-config release-thunderbird-comm-release.py --skip-reconfig --bypass-l10n-dashboard-check localhost:9301
Disable pymake
win32 build failed because it tried to use pymake, which isn't supported on Gecko 17 bug 841898. FIXME - why didn't this get caught in pre-release builds? Does Thunderbird-Release not build the same thing that we're going to release with?
Landed the patches from that bug, retagged buildbot-configs and buildbotcustom, reconfiged build masters, and then used "rebuild" to restart the win32 build.
Retrigger mac builds
Mac build failed because reconfig w/ directory shortening happened mid-build. Someone retriggered it (don't know who), and it succeeded.
Repacks subsequently failed because the en-US was retriggered with "force build" instead of "rebuild", which meant that "script_repo_revision" wasn't set. (FIXME: we should make sure it's always set). Used "force build" to start those builders with "script_repo_revision" set to THUNDERBIRD_17_0_3_RELEASE
Push snippets
As tbirdbld@aus3-staging
cd /opt/aus2/snippets/staging ~/bin/pushsnip Thunderbird-17.0.3-build1
Postrelease
Used "force build" to start postrelease builder.
