-
Notifications
You must be signed in to change notification settings - Fork 578
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
Clarify that releases in maintenance are still LTS #257
Comments
This has occasionally caused some confusion, yet it also seems, from my
reading, that _Active_ and _Maintenance_ are equally mentioned as stages of
an LTS release.
Therefore, it seems, in my opinion, that it could be more of a messaging
problem. Maybe we just aren't consistently communicating that 'maintenance'
is a later stage of LTS.
…On Sep 28, 2017 7:04 PM, "Matteo Collina" ***@***.***> wrote:
In the README we talk about *active* LTS vs maintenance. I think we
should call both of them LTS, one active and one in maintenance. I think
this was the spirit of the document, but it could be read in the wrong way,
e.g. node 4 is not LTS anymore.
We are still supporting node 4 until April 2018.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#257>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGY_5rD_9wl37j844AbawUDIVxdA8znSks5snDQkgaJpZM4PoCo6>
.
|
Are these the lines you find unclear? For me they seem to be clearly talking about Active vs Maintenance LTS modes, but please do raise a PR if you think it could be more unambiguous (I find it hard to read these docs from the point of view of a newcomer to Node). |
I agree both that the intent is that a release is LTS throughout the 30 months and that the text above seems ok. BUt as @gibfahn if you can propose something that migth be clearer to people not quite as close to the process that would be great. |
I actually really like @jasnell's tweet - https://mobile.twitter.com/jasnell/status/829353751748042752 It clearly states the stage transition - It also clearly states what people should expect as a result of the transition - Perhaps one item that could help would be to update the schedule diagram. Either remove I'll see if I can't reach out to people and see what else could help improve the messaging around LTS stages. |
+1, seems like a good idea. |
Also changes `Active` and `Maintenance` to `Active LTS` and `Maintenance LTS`. Fixes: nodejs#257
Also changes `Active` and `Maintenance` to `Active LTS` and `Maintenance LTS`. Fixes: nodejs#257 Refs: nodejs/node#16630
Also changes `Active` and `Maintenance` to `Active LTS` and `Maintenance LTS`. Fixes: nodejs#257 Refs: nodejs/node#16630
Also changes `Active` and `Maintenance` to `Active LTS` and `Maintenance LTS`. Fixes: #257 Refs: nodejs/node#16630
Also changes `Active` and `Maintenance` to `Active LTS` and `Maintenance LTS`. Fixes: nodejs#257 Refs: nodejs/node#16630
In the README we talk about active LTS vs maintenance. I think we should call both of them LTS, one active and one in maintenance. I think this was the spirit of the document, but it could be read in the wrong way, e.g. node 4 is not LTS anymore.
We are still supporting node 4 until April 2018.
The text was updated successfully, but these errors were encountered: