Change support to Maintenance LTS branches
See original GitHub issueNode v6 is not quite three years old. Most of the other frameworks I use still support it. Karma is the only outlier (noted in the node-tap
dependencies) that requires node 8. Would it be reasonable to change the support policy to LTS maintenance?
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Confusion regarding “Maintenance LTS” status #605 - GitHub
I've been reading through the history a bit of how “Maintenance” was changed to “Maintenance LTS.” There seems to be good reasoning behind ......
Read more >Essential Steps: Long Term Support for Node.js - Medium
Then, for an additional 12 months, the branch will go into maintenance — where only severe bugs and security problems will be addressed....
Read more >Differences between Long Term Support and Feature Release ...
Syslog-ng Store Box (SSB) has two release branches, Long Term Support (LTS) and Feature Release (FR). This article is intended to d 4278363....
Read more >Long-Term Support - Evolveum Docs
Support lifetime is applied to (minor/major) midPoint releases. Maintenance releases do not change support lifetime, and they have no ...
Read more >Long Term Support (LTS) and Short Term Support (STS ...
AOS 5.20 LTS is the 3rd Maintenance Release (MR) of AOS 5.19 release branch. Features and bug fixes that are in AOS 5.19,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Node v6 will exit LTS in less than 40 days. karma 3.x still supports node 6. We chose to move on to v8 so we could begin to leverage
async
. I think this is a reasonable tradeoff.Yes, you are correct, our docs are out of date for a month. Have you tried v3.x on node 6?