Update release dates in ESR release overview image

RESOLVED FIXED

Status

RESOLVED FIXED
3 years ago
2 years ago

People

(Reporter: bugzilla, Assigned: kohei)

Tracking

Production

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment)

(Reporter)

Description

3 years ago
ESR release overview image in the following pages contains old release dates.
https://www.mozilla.org/en-US/firefox/organizations/faq/
https://wiki.mozilla.org/Enterprise/Firefox/ExtendedSupport:Proposal

We've updated release schedule for 2016 and we also need update the image.
https://wiki.mozilla.org/RapidRelease/Calendar
https://blog.mozilla.org/futurereleases/2016/02/04/update-on-2016-firefox-release-schedule/

We also need define the release date of next ESR release (Firefox 52).
# Alex, do you have any information or plan for the next Firefox ESR schedule?
# enterprise users need the schedule info to secure their resources
(Reporter)

Updated

3 years ago
Flags: needinfo?(ashapiro)
Assignee: nobody → kohei.yoshino
Status: NEW → ASSIGNED
We need the dates for Firefox 52 (52 ESR launch) and 54 (ESR 45 end-of-life) to update the image.
Aware of this and we will give you the information very soon!

Comment 3

3 years ago
This hasn't been flagged as a comms issue.
Flags: needinfo?(ashapiro)
Friendly ping...
Flags: needinfo?(sledru)
We have now the 2017 dates:
https://wiki.mozilla.org/RapidRelease/Calendar
Sorry about the delay!
Flags: needinfo?(sledru)

Comment 7

2 years ago
Commits pushed to master at https://github.com/mozilla/bedrock

https://github.com/mozilla/bedrock/commit/22468bc27d2467d7eec2e0cadbb0aa50f2dd3fbc
Fix Bug 1254387 - Update release dates in ESR release overview image

https://github.com/mozilla/bedrock/commit/3c58b6a53da8cb8bb09d9f7f399acecbe32d143c
Merge pull request #4327 from kyoshino/bug-1254387-esr-overview

Fix Bug 1254387 - Update release dates in ESR release overview image

Updated

2 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.