Closed Bug 1457090 Opened 6 years ago Closed 6 years ago

tracking bug for esr60 patches that need to be grafted after mergeduty completes

Categories

(Release Engineering :: Release Automation: Other, enhancement)

Product:
Release Engineering
Component:
Release Automation: Other
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(firefox-esr6060+ fixed)

Status:
RESOLVED FIXED
Tracking Flags:
Tracking Status
firefox-esr60 60+ fixed

People

(Reporter: mtabara, Unassigned)

References

Details

We didn't manage to graft everything before mergeday. Now it's too late as the request to merge repos is bound to arrive in a few moments.

Let's use this bug to track all the patches that still need a graft to esr60 once the mergeduty is completed later on today.
Blocks: esr60
Once mergeduty is done, we need to graft the following two patches to release & esr60:

* https://hg.mozilla.org/mozilla-central/rev/db04d03e8418
* https://hg.mozilla.org/mozilla-central/rev/45bc926dad5c

Moreover, the first patch needs a taskcluster/ci/config.yml change as well, which lies within https://hg.mozilla.org/mozilla-central/rev/9c941daebe9f but that's riding the trains so we can't uplift it. Solution is to just manually add these changes, specifically https://hg.mozilla.org/mozilla-central/diff/9c941daebe9f/taskcluster/ci/config.yml to release & esr60 after mergeduty is done.
Blocks: 1453261
Blocks: 1453273
Blocks: 1453255
Once mergeduty is done, we need to land these to inbound, and then graft to central/beta/release and esr60:

* https://bug1453253.bmoattachments.org/attachment.cgi?id=8969275
* https://bug1453253.bmoattachments.org/attachment.cgi?id=8969327

More stuff from bug 1453253 is in comment 1.
Blocks: 1453253
(In reply to Mihai Tabara [:mtabara]⌚️GMT from comment #2)
> Once mergeduty is done, we need to land these to inbound, and then graft to
> central/beta/release and esr60:
> 
> * https://bug1453253.bmoattachments.org/attachment.cgi?id=8969275
> * https://bug1453253.bmoattachments.org/attachment.cgi?id=8969327
> 
> More stuff from bug 1453253 is in comment 1.

Some of these patches might need addressing some comments.
See Also: → 1453993
Pushed the latest patch to esr60.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
I have not grafted it around. We should wait for trees to reopen for that.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(In reply to Mihai Tabara [:mtabara]⌚️GMT from comment #1)
> Once mergeduty is done, we need to graft the following two patches to
> release & esr60:
> 
> * https://hg.mozilla.org/mozilla-central/rev/db04d03e8418
> * https://hg.mozilla.org/mozilla-central/rev/45bc926dad5c
> 
> Moreover, the first patch needs a taskcluster/ci/config.yml change as well,
> which lies within https://hg.mozilla.org/mozilla-central/rev/9c941daebe9f
> but that's riding the trains so we can't uplift it. Solution is to just
> manually add these changes, specifically
> https://hg.mozilla.org/mozilla-central/diff/9c941daebe9f/taskcluster/ci/
> config.yml to release & esr60 after mergeduty is done.

https://hg.mozilla.org/releases/mozilla-release/rev/28107b91f58a5f0a274f1508cb400337871ea875
https://hg.mozilla.org/releases/mozilla-esr60/rev/f8ab4e05a997625118dbb04a30ec0f4308a52a40
I think we landed everything we had to land at this point. 
Let's close this now and reopen in case the GTB goes wrong.
Status: REOPENED → RESOLVED
Closed: 6 years ago → 6 years ago
Resolution: --- → FIXED
Pushed by mozilla@hocat.ca:
https://hg.mozilla.org/integration/mozilla-inbound/rev/7c2fda6b8540
add esr60 fixes in automation. r=aki
https://hg.mozilla.org/integration/mozilla-inbound/rev/dbf2ddb7e30a
add missing esr60 config in release-generate-checksums.r=jlorenzo
You need to log in before you can comment on or make changes to this bug.