Closed Bug 1452948 Opened 6 years ago Closed 6 years ago

Set ESR_NEXT to 60 in ship-it config

Categories

(Release Engineering :: Applications: Shipit, enhancement)

Product:
Release Engineering
Component:
Applications: Shipit
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: jlorenzo, Unassigned)

References

Details

Firefox ESR 60.0 goes to build on April 30th. Like in bug 1341491, we want to set [1] to 60, after we officially shipped this new ESR.

[1] https://github.com/mozilla-releng/ship-it/blob/98d08b2653c7f171e21e9fd018484c8f3388037c/kickoff/config.py#L8
:rail is this a pre-ship or post-ship thing (before 60.0esr or after)
Flags: needinfo?(rail)
This is post-ship, when we have 60 available.
Flags: needinfo?(rail)
It looks like the code in jsonexport.py would be OK if ESR_NEXT was defined in the config but no shipped releases yet. The upside of defining early is that product-details would define FIREFOX_ESR_NEXT the first cron after we mark 60.0esr shipped. One less thing to do on release day re verifying bug 1408868.
RelMan took care of this in https://github.com/mozilla-releng/ship-it/pull/221. We probably should have made this a task in releasewarrior to track it.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Component: Applications: ShipIt (backend) → Applications: ShipIt
You need to log in before you can comment on or make changes to this bug.