Skip to content
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

Add an lts/supported.yml and lts/strict/supported.yml #7

Open
dominykas opened this issue Jul 14, 2020 · 0 comments
Open

Add an lts/supported.yml and lts/strict/supported.yml #7

dominykas opened this issue Jul 14, 2020 · 0 comments

Comments

@dominykas
Copy link
Member

This came out of a discussion during nodejs/package-maintenance#379 meeting.

We've agreed in pkgjs that we recommend to bump semver major when dropping support for a specific node version, so that's why the initial proposal in #5 does not automatically remove the versions that people test in.

That said, part of the intent of this repository is to reduce the maintenance burden and so changing the gte-N import could be considered a minor hassle. We might want to offer a config which you simply import, and it automatically drops the node versions that are no longer maintained (possibly with a delay?).

I know this could be a contentious discussion, so I'm splitting this out of #5.

@dominykas dominykas changed the title Add an lts/maintained.yml and lts/strict/maintained.yml Add an lts/supported.yml and lts/strict/supported.yml Aug 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant