-
Notifications
You must be signed in to change notification settings - Fork 568
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
What is the difference between Current and Active? #430
Comments
Does this help? https://github.com/nodejs/node#release-types |
Current is actively updated on a weekly or bi-weekly basis. It will be Semver-Minor or Semver-Patch depending on the backlog on master. Active LTS has a monthly release cadence and will only contain changes that have already gone out in a Current release. For production services I do not advise ever using Current. |
"Current" represents the current release line that receives all non-breaking changes that land in Node's master branch. The things that land in an active LTS or maintenance line are covered in https://github.com/nodejs/Release#release-plan.
That version has been end of life for a while. Companies should generally stick to even numbered versions. I'd recommend moving to 10 now, and 12 once it goes LTS. |
@BethGriggs Only partially. It doesn't say anything about |
Closing as i've gotten my answer. Thanks all. |
I'm curious what the difference between the Current and Active statuses of a Node.js version are.
My team is currently on version 9 and trying to determine whether to move to 10, 11, or 12 but i'm not sure what the statuses actually mean and there is nothing documented on the README about them (at least that I skimmed through and found).
The text was updated successfully, but these errors were encountered: