-
Notifications
You must be signed in to change notification settings - Fork 145
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
supported vs maintained #353
Comments
@wesleytodd not sure you think we should change the terminology in PACKAGE-SUPPORT.md or in nv ? |
I will open a PR to pkgjs 👍 |
The PACKAGE-SUPPORT document is out of draft (and uses |
The decision in nodejs/Release#359 and nodejs/Release#517 uses |
From original issue: pkgjs/nv#7
As noted in the README, there isn't a canonical reference yet, but raising an apparent terminology variation in the current draft documents. (This may have been resolved in a discussion I didn't find.)
nv
supports an alias formaintained
, but https://github.com/nodejs/package-maintenance/blob/master/docs/drafts/PACKAGE-SUPPORT.md#node-name-space lists a target alias ofsupported
cc @shadowspawn
@nodejs/package-maintenance Anyone want to take a look at addressing this?
I also think we should consider moving what is documented in this issue into a document of it's own then reference it from the package support proposal. I say this because I think we should move faster on the standardized grammar than the support work (which has been stalled lately). Thoughts?
The text was updated successfully, but these errors were encountered: