nodejs / nodejs/package-maintenance
Communicating that only the latest version of a major release line is supported
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 423
- Forks
- 147
- PR merge metrics
- No merged PRs in 30d
Description
This came up in discussions in https://github.com/nodejs/ci-config-travis/pull/6.
When people say they support e.g. Node 14.x, the usually (is that true?) mean that they only support the latest version in the 14.x line. At this time neither semver, nor PACKAGE-SUPPORT allows to define that as such?
Should we clarify that in the PACKAGE-SUPPORT doc?
Ideally, one would be able to communicate that via engines as well, but moving the semver standard might be trickier (if possible at all).
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 docs/PACKAGE-SUPPORT.md and the discussion in nodejs/ci-config-travis#6 first. Determine whether the documentation should define support for only the latest version in a major line, and distinguish that clarification from the separate semver and engines questions. Done means the support policy is clearly documented or the unresolved scope is recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100