nodejs / nodejs/package-maintenance
A practical approach is to only support the LTS version
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 423
- Forks
- 147
- PR merge metrics
- No merged PRs in 30d
Description
If the aim is to make sure that the enterprise can adopt and choose to subsequently support node then the LTS path makes the most sense. Enterprise upgrade less often and stick to the LTS versions.
We have to also be practical in that the weight of maintenance would eventually not be sustainable for anything other than the current LTS.
Originally posted by @ghinks in https://github.com/_render_node/MDU6SXNzdWUzOTIyNzk4MTA=/issues/unread_timeline#issuecomment-448401317
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the issue discussion and its linked original comment to understand the proposal to support only the Node.js LTS version. Identify whether the maintainers have reached a decision and what concrete maintenance policy should result; the work is done when that policy and its scope are agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100