-
Notifications
You must be signed in to change notification settings - Fork 575
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
doc: remove confusing wording regarding NAN #398
Conversation
Use "Active LTS" instead. Fixes: #147
We already use "active" as separate from "maintenance". |
@richardlau yes, and that's what it is about here. |
We would expect the abstraction layer to also support maintenance releases. |
Based on #359 maybe use "supported" instead? |
But the next sentence says a maximum of 2 LTS releases. If maintenance was included it would be 3. |
Hmm. You're right but I'd certainly be very surprised if I was using maintenance LTS and |
I think that this is a mistake... I do not believe that nan plans to remove support for a version of node that is supported by node /cc @nodejs/n-api |
I thought about it... My conclusion is that we can remove this section. NAN is out of the scope of the Release WG. |
/cc @nodejs/release |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
I've updated the title to better reflect the content. Landing |
Use "Active LTS" instead.
Fixes: #147