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

Where is the official node.js LTS schedule? #66

Closed
majgis opened this issue Jan 6, 2016 · 5 comments
Closed

Where is the official node.js LTS schedule? #66

majgis opened this issue Jan 6, 2016 · 5 comments

Comments

@majgis
Copy link
Contributor

majgis commented Jan 6, 2016

It is not clear to me what the LTS schedule is for v0.12

On this page, https://github.com/nodejs/LTS, the chart doesn't match the table, and the table is under a section that says "hypothetically".

I expected to find this information on the main nodejs.org site but I did not find it. Where is the gospel truth?

@majgis majgis changed the title What is node.js LTS schedule? Where is the official node.js LTS schedule? Jan 6, 2016
@ChALkeR
Copy link
Member

ChALkeR commented Jan 8, 2016

/cc @jasnell and @rvagg

@rvagg
Copy link
Member

rvagg commented Jan 18, 2016

It's only "hypothetical" because it uses actual version numbers and this was done before we had any of those numbers. We need to update it to remove "hypothetical" because we now know how 4.x turned out.

The dot-points are the authoritative source of the policy with the chart attempting to display that graphically.

We should leave this open as a TODO to fix up the README. I've had some ideas about how to clear it up to try and remove some of the confusion.

@ChALkeR
Copy link
Member

ChALkeR commented Jan 18, 2016

@rvagg The confusing part of it is that the table states that 0.12 LTS End is 2017-04-01, while the chart has 2016-12. Which one is correct? Also note that #36 states that 0.12 LTS End is 2016-12-31.

@rvagg
Copy link
Member

rvagg commented Jan 18, 2016

argh, yeah, the chart is correct, we pulled 0.12 to the end of 2016 to line up with the corresponding OpenSSL EOL. 0.12 is EOL on 2016-12-31.

I'll fix it asap, not today cause 💤

@MylesBorins
Copy link
Member

The schedule is now public. Closing

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

4 participants