port bug 1481121 - bz2 mar from M-C

RESOLVED FIXED in Thunderbird 63.0

Status

enhancement
RESOLVED FIXED
Last year
Last year

People

(Reporter: rjl, Assigned: rjl)

Tracking

Trunk
Thunderbird 63.0
Other
Other

Thunderbird Tracking Flags

(thunderbird_esr60+)

Details

Attachments

(5 attachments, 1 obsolete attachment)

Bug 1484264 includes support for bz2 mar files. Configuration needs to be ported to C-C.
What about bug 1481121? That needs to be ported as well according to Tom on IRC.
I grabbed the wrong bug number in comment 0. This bug is to port bug 1481121.
Summary: port bz2 mar from M-C → port bug 1481121 - bz2 mar from M-C
Pushed by mozilla@jorgk.com:
https://hg.mozilla.org/comm-central/rev/3e42d56b666f
Build bz2 mar's on comm-esr60; r=tomprince
https://hg.mozilla.org/comm-central/rev/ca4c5bb8343e
Use existing release-artifact metadata in beetmover_repackage; r=tomprince
https://hg.mozilla.org/comm-central/rev/3195c4b5aafb
generate bz2 bouncer entries; r=tomprince
https://hg.mozilla.org/comm-central/rev/0ec2bb1aa466
Do update verification back to ESR52 on comm-esr60; r=tomprince
https://hg.mozilla.org/comm-central/rev/ca01c880da9b
Add support for generating bz2 balrog blob; r=tomprince
Status: NEW → RESOLVED
Closed: Last year
Resolution: --- → FIXED
Target Milestone: --- → Thunderbird 63.0
Pushed by mozilla@jorgk.com:
https://hg.mozilla.org/comm-central/rev/3a6f4e8ba186
Follow-up: fix yaml complaints by removing empty lines near EOF. r=me
I'm already tracking this in my mind especially when I see
https://hg.mozilla.org/releases/mozilla-esr60/pushloghtml?changeset=6e9112ccfe52

So we uplift/backport all the stuff here plus more? What else?
As for see "what else", see for example here: Bug 1460777 comment #40.

So after we update our release branch THUNDERBIRD_60_VERBRANCH to mozilla-esr60 60.2, we'll need to push a whole bunch of stuff to comm-esr60. Better get ready now.
Assignee: nobody → rob
Weren't you going to attach the other patches, so Tom can review them "post landing"?

Also, (comm-esr60|try): if that's comm-central specific, shouldn't it be try-comm-central?
Attachment #9005901 - Attachment is obsolete: true
What do the D4860 etc numbers mean?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment on attachment 9006008 [details]
Bug 1487286: generate bz2 bouncer entries; r?tomprince

Tom Prince [:tomprince] has approved the revision.
Attachment #9006008 - Flags: review+
Comment on attachment 9006009 [details]
Bug 1487286: Do update verification back to ESR52 on comm-esr60; r?tomprince

Tom Prince [:tomprince] has approved the revision.
Attachment #9006009 - Flags: review+
Comment on attachment 9006007 [details]
Bug 1487286: Use existing release-artifact metadata in beetmover_repackage; r?tomprince

Tom Prince [:tomprince] has approved the revision.
Attachment #9006007 - Flags: review+
Comment on attachment 9006010 [details]
Bug 1487286: Add support for generating bz2 balrog blob; r?tomprince

Tom Prince [:tomprince] has approved the revision.
Attachment #9006010 - Flags: review+
Comment on attachment 9006006 [details]
Bug 1487286: Build bz2 mar's on comm-esr60; r?tomprince

Tom Prince [:tomprince] has approved the revision.
Attachment #9006006 - Flags: review+
Status: REOPENED → RESOLVED
Closed: Last yearLast year
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.