Closed Bug 913452 Opened 11 years ago Closed 11 years ago

Switch 'Thunderbird-Release' on TBPL to use {mozilla,comm}-esr24 branches rather than {mozilla,comm}-release

Categories

(Tree Management Graveyard :: TBPL, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rail, Assigned: rail)

References

Details

Attachments

(2 files, 1 obsolete file)

+++ This bug was initially created as a clone of Bug #808017 +++
mozilla-esr24 was just added by bug 913297
Summary: update TBPL with {mozilla,comm}-esr24 branch → update TBPL with comm-esr24 branch
No longer blocks: mozilla-esr24
Hmm, I'm not even sure if we need this for Thunderbird, since there will be no TB 24ESR release (even though TB 24 will be built off comm-esr24 branch)
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
Actually we need to update Thunderbird-Release to point to esr24 since we switched releng automation to use that branch.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Attachment #801118 - Flags: review?(emorley)
Summary: update TBPL with comm-esr24 branch → Swtich 'Thunderbird-Release' on TBPL to use {mozilla,comm}-esr24 branches rather than {mozilla,comm}-release
Attachment #801118 - Flags: review?(emorley) → review+
Depends on: 913951
In production :-)
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → FIXED
buildbotBranch should point to comm-release... Patch incoming.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Attached patch buildbotBranch: "comm-release" (obsolete) — Splinter Review
Attachment #801548 - Flags: review?(emorley)
Comment on attachment 801548 [details] [diff] [review] buildbotBranch: "comm-release" Surely this should be changed buildbot-side instead? We're using the esr24 repos but buildbot is treating it as -release ? I'm confused! :-)
Summary: Swtich 'Thunderbird-Release' on TBPL to use {mozilla,comm}-esr24 branches rather than {mozilla,comm}-release → Switch 'Thunderbird-Release' on TBPL to use {mozilla,comm}-esr24 branches rather than {mozilla,comm}-release
Heh, yeah, it's confusing. It's all based on the fact that TB 24.0 *release* (comm-release buildbot branch) uses the *releases/comm-esr24* repo. It's possible to change the buildbot part, but to me it sounds weird to have release builds named comm-esr24. Mark, do you have any preferences?
Flags: needinfo?(mbanner)
I'm generally happy with what works for everyone. Using comm-esr24 for buildbot would potentially be easier to remember, but I don't really have a preference. The last year's release builds I've only really seen from comm-esr17 anyway.
Flags: needinfo?(mbanner)
Comment on attachment 801548 [details] [diff] [review] buildbotBranch: "comm-release" No need for this
Attachment #801548 - Attachment is obsolete: true
Attachment #801548 - Flags: review?(emorley)
In the parent bug we're killing comm-release in favour of comm-esr24. Let's do the same here!
Attachment #802350 - Flags: review?(emorley)
Comment on attachment 802350 [details] [diff] [review] kill Thunderbird-Release, add Thunderbird-Esr24 I'd maybe swap the ordering of es24 and esr17, since the rest of the Thunderbird repos go from new to old, but not too fussed either way :-)
Attachment #802350 - Flags: review?(emorley) → review+
Comment on attachment 802350 [details] [diff] [review] kill Thunderbird-Release, add Thunderbird-Esr24 When I changed the order, the patch turned into a one-liner :) http://hg.mozilla.org/webtools/tbpl/rev/60ce1f27d055
Depends on: 914665
Second patch in production :-)
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → FIXED
Product: Webtools → Tree Management
Product: Tree Management → Tree Management Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: