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.

Sign up for GitHub

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

Jump to bottom

doc: use _code name_ rather than _codename_ #36611

Merged
merged 1 commit into from Dec 27, 2020
Merged

doc: use _code name_ rather than _codename_ #36611

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Expand Up @@ -53,7 +53,7 @@ Looking for help? Check out the
* **LTS**: Releases that receive Long-term Support, with a focus on stability
and security. Every even-numbered major version will become an LTS release.
LTS releases receive 12 months of _Active LTS_ support and a further 18 months
of _Maintenance_. LTS release lines have alphabetically-ordered codenames,
of _Maintenance_. LTS release lines have alphabetically-ordered code names,
beginning with v4 Argon. There are no breaking changes or feature additions,
except in some special circumstances.
* **Nightly**: Code from the Current branch built every 24-hours when there are
Expand Down
7 changes: 3 additions & 4 deletions doc/api/process.md
View file
Open in desktop
Expand Up @@ -1782,12 +1782,11 @@ tarball.
* `lts` {string} a string label identifying the [LTS][] label for this release.
This property only exists for LTS releases and is `undefined` for all other
release types, including _Current_ releases.
Valid values include the LTS Release Codenames (including those
that are no longer supported). A non-exhaustive example of
these codenames includes:
Valid values include the LTS Release code names (including those
that are no longer supported).
* `'Dubnium'` for the 10.x LTS line beginning with 10.13.0.
* `'Erbium'` for the 12.x LTS line beginning with 12.13.0.
For other LTS Release Codenames, see [Node.js Changelog Archive](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_ARCHIVE.md)
For other LTS Release code names, see [Node.js Changelog Archive](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_ARCHIVE.md)

<!-- eslint-skip -->
```js
Expand Down
4 changes: 2 additions & 2 deletions doc/guides/releases.md
View file
Open in desktop
Expand Up @@ -497,7 +497,7 @@ $ git secure-tag <vx.y.z> <commit-sha> -sm "YYYY-MM-DD Node.js vx.y.z (<release-
```

`release-type` is either "Current" or "LTS". For LTS releases, you should also
include the release codename, for example:
include the release code name.

```text
2019-10-22 Node.js v10.17.0 'Dubnium' (LTS) Release
Expand Down Expand Up @@ -740,7 +740,7 @@ To mark a release line as LTS, the following changes must be made to
* The `NODE_MINOR_VERSION` macro must be incremented by one
* The `NODE_PATCH_VERSION` macro must be set to `0`
* The `NODE_VERSION_IS_LTS` macro must be set to `1`
* The `NODE_VERSION_LTS_CODENAME` macro must be set to the codename selected
* The `NODE_VERSION_LTS_CODENAME` macro must be set to the code name selected
for the LTS release.

For example:
Expand Down