Closed Bug 1460752 Opened 2 years ago Closed 2 years ago

Update ESR config for dropping ESR52 when shipping 60.2.0esr

Categories

(Release Engineering :: Applications: Shipit (backend), enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: nthomas, Assigned: jcristau)

References

Details

Attachments

(1 file)

50 bytes, text/x-github-pull-request
jlorenzo
: review+
Details | Review
At 60.2.0esr we expect to discontinue ESR52, and should update https://github.com/mozilla-releng/ship-it/blob/master/kickoff/config.py after shipping. The new values should be

CURRENT_ESR = "60"
ESR_NEXT = ""

so that https://product-details.mozilla.org/1.0/firefox_versions.json ends up
containing
  "FIREFOX_ESR": "60.2.0esr",
  "FIREFOX_ESR_NEXT": "",

This will result in https://www.mozilla.org/en-US/firefox/organizations/all/ only showing ESR62 downloads. There are various cron jobs which will add lag to the propagation of the config change.
Attached file GitHub Pull Request
Assignee: nobody → jlorenzo
Attachment #9006546 - Flags: review+
Assignee: jlorenzo → jcristau
Status: NEW → ASSIGNED
$ curl -s https://product-details.mozilla.org/1.0/firefox_versions.json | jq '[.FIREFOX_ESR, .FIREFOX_ESR_NEXT]'
[
  "60.2.0esr",
  ""
]
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.