1661673 - make esr78 not next-esr

Status: RESOLVED FIXED

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

Description

[Mihai Tabara [:mtabara]⌚️GMT]

Currently ESR78 is still marked as next-esr within automation and a bunch of other places. We should fix that.

Comment 1

[Mihai Tabara [:mtabara]⌚️GMT]

Chatted on Matrix with Julien. A few things in mind:

• Ship-it
• bouncer-aliases
• balrog
• potentially others

Some are in-tree, some external services that RelEng handles.

Comment 2

[Mihai Tabara [:mtabara]⌚️GMT]

Attachment: Bug 1661673 - make esr78 not next-esr.r=#releng

Comment 3

[Mihai Tabara [:mtabara]⌚️GMT]

Attachment: Bug 1661673 - remove esr68 references.r=#releng

Depends on D88591

Comment 4

[Mihai Tabara [:mtabara]⌚️GMT]

Attachment: Bug 1661673 - switch cron-bouncer to esr78. r=#releng

Depends on D88618

Comment 5

[Mihai Tabara [:mtabara]⌚️GMT]

Comment on attachment 9172670 [details]
Bug 1661673 - make esr78 not next-esr.r=#releng

Beta/Release Uplift Approval Request

• User impact if declined: This patch should land during 81 cycle in esr78 so that 78.3.0 is correctly shipped to Snap and Bouncer.
• Is this code covered by automated tests?: Yes
• Has the fix been verified in Nightly?: Yes
• Needs manual test from QE?: Yes
• If yes, steps to reproduce:
• List of other uplifts needed: None
• Risk to taking this patch: Low
• Why is the change risky/not risky? (and alternatives if risky):
• String changes made/needed:

ESR Uplift Approval Request

• If this is not a sec:{high,crit} bug, please state case for ESR consideration: This patch should land during 81 cycle in esr78 so that 78.3.0 is correctly shipped to Snap and Bouncer.
• User impact if declined:
• Fix Landed on Version:
• Risk to taking this patch: Low
• Why is the change risky/not risky? (and alternatives if risky):
• String or UUID changes made by this patch:

Comment 6

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/a3dc62b6fcf0
make esr78 not next-esr.r=releng-reviewers,aki DONTBUILD

Comment 7

[Mihai Tabara [:mtabara]⌚️GMT]

Comment on attachment 9172700 [details]
Bug 1661673 - remove esr68 references.r=#releng

Beta/Release Uplift Approval Request

• User impact if declined: This cleans-up ESR68 from our codebase. Can land after https://phabricator.services.mozilla.com/D88591 and anytime during 81 cycle. To be uplifted to ESR78 too.
• Is this code covered by automated tests?: Yes
• Has the fix been verified in Nightly?: Yes
• Needs manual test from QE?: Yes
• If yes, steps to reproduce:
• List of other uplifts needed: None
• Risk to taking this patch: Low
• Why is the change risky/not risky? (and alternatives if risky):
• String changes made/needed:

ESR Uplift Approval Request

• If this is not a sec:{high,crit} bug, please state case for ESR consideration: This cleans-up ESR68 from our codebase. Can land after https://phabricator.services.mozilla.com/D88591 and anytime during 81 cycle. To be uplifted to ESR78 too.
• User impact if declined:
• Fix Landed on Version:
• Risk to taking this patch: Low
• Why is the change risky/not risky? (and alternatives if risky):
• String or UUID changes made by this patch:

Comment 8

[Mihai Tabara [:mtabara]⌚️GMT]

Removed the flags from mozilla-release as they will ride the trains anyway, beta suffices I suppose.

Comment 9

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/3272eb7cf779
remove esr68 references.r=releng-reviewers,aki DONTBUILD

Comment 10

[Alexandru Michis [:malexandru]]

https://hg.mozilla.org/mozilla-central/rev/a3dc62b6fcf0
https://hg.mozilla.org/mozilla-central/rev/3272eb7cf779

Comment 11

[Ryan VanderMeulen [:RyanVM]]

Comment on attachment 9172670 [details]
Bug 1661673 - make esr78 not next-esr.r=#releng

Approved for 81.0b7 and 78.3esr.

Comment 12

[Ryan VanderMeulen [:RyanVM]]

https://hg.mozilla.org/releases/mozilla-beta/rev/ac3bcd0175ef
https://hg.mozilla.org/releases/mozilla-beta/rev/6d5ede21b0f8

Comment 13

[Mihai Tabara [:mtabara]⌚️GMT]

Comment on attachment 9172670 [details]
Bug 1661673 - make esr78 not next-esr.r=#releng

To confirm, this is an automation change, doesn't need QA verification, I might've selected the wrong options initially.

Comment 14

[Mihai Tabara [:mtabara]⌚️GMT]

Comment on attachment 9172700 [details]
Bug 1661673 - remove esr68 references.r=#releng

To confirm, this is an automation change, doesn't need QA verification, I might've selected the wrong options initially.

Comment 15

[Mihai Tabara [:mtabara]⌚️GMT]

Comment on attachment 9172711 [details]
Bug 1661673 - switch cron-bouncer to esr78. r=#releng

This is to land once 78.3.0 is out the door.

Comment 16

[Ryan VanderMeulen [:RyanVM]]

https://hg.mozilla.org/releases/mozilla-esr78/rev/9e8441749e04
https://hg.mozilla.org/releases/mozilla-esr78/rev/95637d01c815

Comment 17

[Mihai Tabara [:mtabara]⌚️GMT]

Attachment: [shipit] switch ESR_NEXT for product-details to point to esr78

Comment 18

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/e7b9f2f61418
switch cron-bouncer to esr78. r=releng-reviewers,aki DONTBUILD

Comment 19

[Mihai Tabara [:mtabara]⌚️GMT]

Comment on attachment 9172711 [details]
Bug 1661673 - switch cron-bouncer to esr78. r=#releng

ESR Uplift Approval Request

• If this is not a sec:{high,crit} bug, please state case for ESR consideration: We can let this patch ride trains to beta/release but we need to graft it to esr78 so that we start checking against the FIREFOX_ESR, not FIREFOX_ESR_NEXT.
• User impact if declined:
• Fix Landed on Version:
• Risk to taking this patch: Low
• Why is the change risky/not risky? (and alternatives if risky):
• String or UUID changes made by this patch:

Comment 20

[Atila Butkovits]

https://hg.mozilla.org/mozilla-central/rev/e7b9f2f61418

Comment 21

[Mihai Tabara [:mtabara]⌚️GMT]

Comment on attachment 9172711 [details]
Bug 1661673 - switch cron-bouncer to esr78. r=#releng

Pushed to esr78 - https://hg.mozilla.org/releases/mozilla-esr78/rev/7fd61f43f6dc7108d9c7025824b6cd8389ab533a