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

Clarification of Ember 5.8 LTS Status #1103

Open
captn3m0 opened this issue Apr 24, 2024 · 0 comments
Open

Clarification of Ember 5.8 LTS Status #1103

captn3m0 opened this issue Apr 24, 2024 · 0 comments

Comments

@captn3m0
Copy link

Filing this on behalf of endoflife.date, where I was trying to update the dates for 5.8 release, and had some questions.

/lts marks the dates for 5.8 as:

Event Date
LTS Promotion April 15, 2024
Bug Fixes Until November 11, 2024
Security Fixes Until April 28, 2025

With the following caveats:

Before a version can be called an "LTS" release, it has to spend at least 6 weeks as a stable release, where it is used and tested by thousands of developers.

Once a release of Ember gets promoted to LTS, it receives bugfixes for 36 weeks and security updates for 54 weeks.

The dates mentioned in #1102 do not align with the policy:

  • 5.8.0 was tagged on 15th April 2024 with the official announcement made on 20th April 2024. It says:

    Today the Ember project is releasing version 5.8 of Ember.js and Ember CLI. This release of Ember.js is an LTS (Long Term Support) candidate.

  • The expected date for LTS Promotion should be 1st June (2024-04-20 +6w), which does not match the date used in Add 5.8 to LTS page #1102
  • The published date for Bug Fixes does not match the policy (2024-11-11'-36 weeks' = 2024-03-04). Expected Date as per the policy would be (2024-12-28)

Open Questions:

  1. Is 5.8 a LTS candidate or promoted to LTS already? Is there a reason for the "6 weeks as stable" part being ignored?
  2. What is the official release date for 5.8, used in the policy - the date of the git tag, or the announcement blog post?
  3. In case the published dates override the policy, perhaps the policy can be updated to include such a note?

Apologies if this sounds like hair-splitting, but I wanted to make sure we have the right dates.

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

1 participant