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 support target all detail #253

Merged
merged 7 commits into from
Oct 15, 2019
Merged
Changes from 6 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 16 additions & 14 deletions docs/drafts/PACKAGE-SUPPORT.md
Original file line number Diff line number Diff line change
Expand Up @@ -118,20 +118,22 @@ The standarized namespace identifiers are:

The standardized options for the node name space are as follows:

| Value | example | Description |
|---------------|------------|-------------|
| xxxxxx | | where xxxxxx is a [semver range](https://semver.io/) of Node.js versions supported.
| `abandoned` | | Not recommended for use. The package is deprecated or no longer maintained
| `none` | | Use at your own risk, no active support. May or may not work for a given Node.js version
| `all` | 8,10,11,12 | The package is maintained for versions of Node.js including both LTS and non-LTS releases. It may be necessary to accept semver-major level (ie. breaking) changes into that application in order to receive essential fixes. Documentation for the package will include the non-LTS releases for which the package is still maintained.
| `lts` | 8,10 | The package is maintained for the Node.js LTS releases (both in Active and Maintenence mode). Anyone creating an application using an LTS version of Node.js and using the latest major version of LTS adopting packages will not have to accept semver-major level (ie. breaking) changes into that application in order to receive essential fixes. Full details are available [here](https://github.com/nodejs/package-maintenance/issues/119)
| `active` | 10,12 | All releases not in maintenance
| `lts_active` | 10 | All releases both LTS and active
| `lts_latest` | 10 | The package is maintained only for the Latest Node.js version. You will be required to update to the latest LTS Node.js version in order to ensure you can use new versions/get security fixes
| `maintained` | 12,10,8 | Node.js versions which are not EOL
| `current` | 12 | The latest release from "all"

Based on the current active Node.js releases which are 8.x (Maintenance LTS), 10.x (Active LTS) and 12.x (Current).
| Value | Current | Active LTS | Maintenance LTS | EOL | Example | Description |
|---------------|---------|------------|-----------------|-----|------------|-------------|
| xxxxxx | | | | | | xxxxxx is a [semver range](https://semver.io/) of Node.js versions supported
| `abandoned` | | | | | | Not recommended for use. The package is deprecated or no longer maintained
| `none` | | | | | | Use at your own risk, no active support. May or may not work for a given Node.js version
| `all` | ✔ | ✔ | ✔ | ✔ | ...,8,9,10,11,12 | The package is maintained for versions of Node.js including both LTS and non-LTS releases regardless of whether they are EOL or not. It may be necessary to accept semver-major level (ie. breaking) changes into that application in order to receive essential fixes. Documentation for the package will include the non-LTS releases for which the package is still maintained (some maintainers support as far back as 0.6)
| `lts` | | ✔ | ✔ | | 8,10 | The package is maintained for the Node.js LTS releases (both in Active and Maintenence status). Anyone creating an application using an LTS version of Node.js and using the latest major version of LTS adopting packages will not have to accept semver-major level (ie. breaking) changes into that application in order to receive essential fixes. Full details are available [here](https://github.com/nodejs/package-maintenance/issues/119)
| `active` | ✔ | ✔ | | | 10,12 | All releases that are in active LTS
Eomm marked this conversation as resolved.
Show resolved Hide resolved
| `lts_active` | | ✔ | | | 10 | All releases both LTS and active. There may be more than one LTS release in active mainteance at a given point in time
Eomm marked this conversation as resolved.
Show resolved Hide resolved
| `lts_latest` | | ✔ | | | 10 | The package is maintained only for the Latest LTS Node.js version. You will be required to update to the latest LTS Node.js version in order to ensure you can use new versions/get security fixes
Eomm marked this conversation as resolved.
Show resolved Hide resolved
| `supported` | ✔ | ✔ | ✔ | | 12,10,8 | Node.js versions which are not EOL
| `current` | ✔ | | | | 12 | The latest release from "all"

The example above are based on the state of Node.js releases at the time of writing (2019-10-07)
which are: 8.x (Maintenance LTS), 10.x (Active LTS) and 12.x (Current).
Checkout the actual state in the [Release Schedule](https://github.com/nodejs/Release#release-schedule).

### Support `response`

Expand Down