Closed
Bug 1720158
Opened 3 years ago
Closed 3 years ago
Disable release-bouncer-aliases on comm-esr78 once Thunderbird 91.0 is released
Categories
(Thunderbird :: Build Config, task)
Tracking
(thunderbird_esr78 fixed, thunderbird_esr91 unaffected)
RESOLVED
FIXED
Thunderbird 78.0
Tracking | Status | |
---|---|---|
thunderbird_esr78 | --- | fixed |
thunderbird_esr91 | --- | unaffected |
People
(Reporter: rjl, Assigned: rjl)
References
Details
Attachments
(1 file)
(deleted),
patch
|
justdave
:
review+
rjl
:
approval-comm-esr78+
|
Details | Diff | Splinter Review |
See bug 1669147
Assignee | ||
Comment 1•3 years ago
|
||
[Approval Request Comment]
The bouncer aliases are not used by much internally, but third parties do rely on them pointing to the latest version. Once Thunderbird 91.0 is out, the latest aliases should point to a 91.x release. Disabling the alias update on comm-esr78 will ensure that is the case.
This needs to land directly to comm-esr78 after 78.13.0.
The same change was made in comm-esr68. See bug 1669147 comment 4.
Assignee: nobody → rob
Status: NEW → ASSIGNED
Attachment #9234484 -
Flags: review?(justdave)
Attachment #9234484 -
Flags: approval-comm-esr78?
Comment 2•3 years ago
|
||
Comment on attachment 9234484 [details] [diff] [review]
bug1720158_aliases.patch
Review of attachment 9234484 [details] [diff] [review]:
-----------------------------------------------------------------
Looks good. Same thing we did last time.
Attachment #9234484 -
Flags: review?(justdave) → review+
Assignee | ||
Comment 3•3 years ago
|
||
Comment on attachment 9234484 [details] [diff] [review]
bug1720158_aliases.patch
[Triage Comment]
Approved for post 78.13.0.
Attachment #9234484 -
Flags: approval-comm-esr78? → approval-comm-esr78+
Assignee | ||
Comment 4•3 years ago
|
||
Post 78.13.0:
https://hg.mozilla.org/releases/comm-esr78/rev/aa47fc0c93c1b0cf228458800cb3b4d4f716f0ac
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
status-thunderbird_esr78:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Thunderbird 78.0
Updated•3 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•