Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

References to Firefox and Firefox ESR and their calendar(s) #412

Closed
grahamperrin opened this issue Jan 30, 2018 · 2 comments
Closed

References to Firefox and Firefox ESR and their calendar(s) #412

grahamperrin opened this issue Jan 30, 2018 · 2 comments

Comments

@grahamperrin
Copy link

From Waterfox 56 Release (2017-11-30):

… Waterfox will now remain at 56 for the time being, following the security releases of 59 ESR until it becomes End of Line (Q1 2019). …

https://wiki.mozilla.org/RapidRelease/Calendar#Future_branch_dates shows Firefox 59 – not Firefox ESR 59 – in Q1 2018

– 2019 is not yet tabled there.

@MrAlex94 I guess that you need a couple of corrections to the blog post.


Side note: where previously Mozilla's extended support for 52.x was scheduled to end with Firefox ESR 52.8, https://wiki.mozilla.org/index.php?title=RapidRelease/Calendar&diff=next&oldid=1184274#mw-diff-left-l39 there's now a 52.9. Allowing more time for users of Firefox ESR 52.x to transition to Firefox ESR 60.x.

@MrAlex94
Copy link
Collaborator

MrAlex94 commented Feb 2, 2018

Yes, each ESR was pushed back by 1 release. Will update :-)

@grahamperrin
Copy link
Author

grahamperrin commented Feb 15, 2018

Thanks … to clarify, is the plan for Waterfox ESR 56.x to follow security releases of Firefox ESR 52.x until Firefox ESR 52.9 becomes end of life?


Postscript: logically, I guess not. (We're already following security releases from versions of Firefox greater than 56.)

It's that "59 ESR" and its EOL "Q1 2019" that need clarification.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants