4 ms·

"We are proud to announce the release of Node.js v4.2.0 "Argon", the first release covered under the new Long Term Support plan! As an LTS release, support for

by ausjke 11y ago

"We are proud to announce the release of Node.js v4.2.0 "Argon", the first release covered under the new Long Term Support plan! As an LTS release, support for v4.x will continue for a period of 30 months from today." I'm a bit lost here, so 4.2.0 is the _first_ LTS, v4.x will be supported by 30 months, what about 4.0.0 then? isn't 4.0.0 also v4.x? but it's not LTS? Shoud we replace v4.x above with v4.2.x instead?

deleted 11y ago
[deleted]
tracker1 11y ago
I'm pretty sure they do mean 4.2.x will be supported for 30 months... wouldn't expect to see updates to 4.0.x or 4.1.x in that vein.
- netcraft 11y ago
  Here is more information: https://github.com/nodejs/LTS/ https://github.com/nodejs/LTS/ Specifically: > Note that while it is possible that critical security and bug fixes may lead to semver-major changes landing within an LTS stream, such situations will be rare and will land as semver-minor bumps
watson 11y ago
As far as I remember this is how it works: Starting from 4.x, every 2nd major version of Node will be LTS (4.x, 6.x etc). But we should expect a few of the early versions of each of these major versions to not be LTS - hence 4.0.x and 4.1.x didn't count as LTS when they were initially released. But Node is now using Semantic Versioning [1], which mean that there will not be any breaking changes between each 4.x release. So 4.2.x is backwards compatible with 4.1.x and 4.0.x. And 4.3.x will be backwards compatible to 4.2.x etc. So in essence the entire 4.x branch will therefore be LTS counting from today. So even if we in 29 months release 4.22.0, this will not extend the 30 months. [1] http://semver.org http://semver.org
- nevi-me 11y ago
  What happens 9 months down the line when v8 stable reaches 48.x? I thought that under semver Node would most likely be a semver-major whenever v8 is the same. If my assumption is correct, how will we handle 6.x and 8.x a potential 18 months from now? Will the LTS maintainers have to worry about 3 LTS versions? I've been following most discussions on Github and TC meetings, but haven't come across this case yet.
  - lugg 11y ago
    From article, > As an LTS release, support for v4.x will continue for a period of 30 months from today. They will likely semver major node into 5/6 etc, but that doesn't change the fact that 4.x will continue with 2 and a half years of LTS. Not sure if that completely answers your question, and I could be wrong.

by ausjke 11y ago

deleted 11y ago

[deleted]

tracker1 11y ago

I'm pretty sure they do mean 4.2.x will be supported for 30 months... wouldn't expect to see updates to 4.0.x or 4.1.x in that vein.

netcraft 11y ago
Here is more information: https://github.com/nodejs/LTS/ https://github.com/nodejs/LTS/ Specifically: > Note that while it is possible that critical security and bug fixes may lead to semver-major changes landing within an LTS stream, such situations will be rare and will land as semver-minor bumps

watson 11y ago

As far as I remember this is how it works: Starting from 4.x, every 2nd major version of Node will be LTS (4.x, 6.x etc). But we should expect a few of the early versions of each of these major versions to not be LTS - hence 4.0.x and 4.1.x didn't count as LTS when they were initially released. But Node is now using Semantic Versioning [1], which mean that there will not be any breaking changes between each 4.x release. So 4.2.x is backwards compatible with 4.1.x and 4.0.x. And 4.3.x will be backwards compatible to 4.2.x etc. So in essence the entire 4.x branch will therefore be LTS counting from today. So even if we in 29 months release 4.22.0, this will not extend the 30 months. [1] http://semver.org http://semver.org

nevi-me 11y ago
What happens 9 months down the line when v8 stable reaches 48.x? I thought that under semver Node would most likely be a semver-major whenever v8 is the same. If my assumption is correct, how will we handle 6.x and 8.x a potential 18 months from now? Will the LTS maintainers have to worry about 3 LTS versions? I've been following most discussions on Github and TC meetings, but haven't come across this case yet.
- lugg 11y ago
  From article, > As an LTS release, support for v4.x will continue for a period of 30 months from today. They will likely semver major node into 5/6 etc, but that doesn't change the fact that 4.x will continue with 2 and a half years of LTS. Not sure if that completely answers your question, and I could be wrong.