Change support to Maintenance LTS branches

[martinheidegger]

Node 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?

[johnjbarton]

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.

[martinheidegger]

I understand that the timing is unfortunate for Node v6. I tried to make my point generally about the Maintenance LTS status. Node 8 is not an active LTS anymore and with your policy it seems appropriate to drop 8 support.

…

On Thu, 21 Feb 2019 at 00:27, johnjbarton ***@***.***> wrote: 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. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#3275 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA3yynvcmp38Mm1gO-KwKtHEnwZ9Xg2mks5vPWlGgaJpZM4bFUoA> .

[johnjbarton]

v8 is LTS Maintenance until 2020. It seems reasonable to support it until close to that date. Is there a problem with that?

[martinheidegger]

works on all active LTS versions

from the docs.

[johnjbarton]

Yes, you are correct, our docs are out of date for a month. Have you tried v3.x on node 6?