Skip to content

Commit 29a6c7c

Browse files
Myles Borinsjasnell
Myles Borins
authored and
jasnell
committed
doc: change references to Stable to Current
With v6 we plan to rename the Stable release line to Current. This commit updates all references to Stable in the codebase. It will have to land along side updates to other repos within the org. Refs: nodejs/nodejs.org#669 PR-URL: #6318 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Сковорода Никита Андреевич <[email protected]> Reviewed-By: Evan Lucas <[email protected]>
1 parent a026cd0 commit 29a6c7c

2 files changed

Lines changed: 13 additions & 13 deletions

File tree

‎README.md‎

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -21,27 +21,27 @@ If you need help using or installing Node.js, please use the
2121

2222
The Node.js project maintains multiple types of releases:
2323

24-
* **Stable**: Released from active development branches of this repository,
24+
* **Current**: Released from active development branches of this repository,
2525
versioned by [SemVer](http://semver.org/) and signed by a member of the
2626
[Release Team](#release-team).
27-
Code for Stable releases is organized in this repository by major version
27+
Code for Current releases is organized in this repository by major version
2828
number, For example: [v4.x](https://github.com/nodejs/node/tree/v4.x).
29-
The major version number of Stable releases will increment every 6 months
29+
The major version number of Current releases will increment every 6 months
3030
allowing for breaking changes to be introduced. This happens in April and
31-
October every year. Stable release lines beginning in October each year have
32-
a maximum support life of 8 months. Stable release lines beginning in April
31+
October every year. Current release lines beginning in October each year have
32+
a maximum support life of 8 months. Current release lines beginning in April
3333
each year will convert to LTS (see below) after 6 months and receive further
3434
support for 30 months.
3535
* **LTS**: Releases that receive Long-term Support, with a focus on stability
36-
and security. Every second Stable release line (major version) will become an
36+
and security. Every second Current release line (major version) will become an
3737
LTS line and receive 18 months of _Active LTS_ support and a further 12
3838
months of _Maintenance_. LTS release lines are given alphabetically
3939
ordered codenames, beginning with v4 Argon. LTS releases are less frequent
4040
and will attempt to maintain consistent major and minor version numbers,
4141
only incrementing patch version numbers. There are no breaking changes or
4242
feature additions, except in some special circumstances. More information
4343
can be found in the [LTS README](https://github.com/nodejs/LTS/).
44-
* **Nightly**: Versions of code in this repository on the current Stable
44+
* **Nightly**: Versions of code in this repository on the current Current
4545
branch, automatically built every 24-hours where changes exist. Use with
4646
caution.
4747

@@ -50,10 +50,10 @@ The Node.js project maintains multiple types of releases:
5050
Binaries, installers, and source tarballs are available at
5151
<https://nodejs.org>.
5252

53-
**Stable** and **LTS** releases are available at
53+
**Current** and **LTS** releases are available at
5454
<https://nodejs.org/download/release/>, listed under their version strings.
5555
The [latest](https://nodejs.org/download/release/latest/) directory is an
56-
alias for the latest Stable release. The latest LTS release from an LTS
56+
alias for the latest Current release. The latest LTS release from an LTS
5757
line is available in the form: latest-_codename_. For example:
5858
<https://nodejs.org/download/release/latest-argon>
5959

@@ -68,7 +68,7 @@ documentation of the latest stable version.
6868

6969
### Verifying Binaries
7070

71-
Stable, LTS and Nightly download directories all contain a *SHASUM256.txt*
71+
Current, LTS and Nightly download directories all contain a *SHASUM256.txt*
7272
file that lists the SHA checksums for each file available for
7373
download.
7474

@@ -88,7 +88,7 @@ $ grep node-vx.y.z.tar.gz SHASUMS256.txt | sha256sum -c -
8888
_(Where "node-vx.y.z.tar.gz" is the name of the file you have
8989
downloaded)_
9090

91-
Additionally, Stable and LTS releases (not Nightlies) have GPG signed
91+
Additionally, Current and LTS releases (not Nightlies) have GPG signed
9292
copies of SHASUM256.txt files available as SHASUM256.txt.asc. You can use
9393
`gpg` to verify that the file has not been tampered with.
9494

‎doc/releases.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -127,7 +127,7 @@ See https://github.com/nodejs/node/labels/confirmed-bug for complete and current
127127
* Include the full list of commits since the last release here. Do not include "Working on X.Y.Z+1" commits.
128128
```
129129

130-
The release type should be either Stable, LTS, or Maintenance, depending on the type of release being produced.
130+
The release type should be either Current, LTS, or Maintenance, depending on the type of release being produced.
131131

132132
### 4. Create Release Commit
133133

@@ -187,7 +187,7 @@ Jenkins collects the artifacts from the builds, allowing you to download and ins
187187

188188
Once you have produced builds that you're happy with, create a new tag. By waiting until this stage to create tags, you can discard a proposed release if something goes wrong or additional commits are required. Once you have created a tag and pushed it to GitHub, you ***should not*** delete and re-tag. If you make a mistake after tagging then you'll have to version-bump and start again and count that tag/version as lost.
189189

190-
Tag summaries have a predictable format, look at a recent tag to see, `git tag -v v5.3.0`. The message should look something like `2015-12-16 Node.js v5.3.0 (Stable) Release`.
190+
Tag summaries have a predictable format, look at a recent tag to see, `git tag -v v6.0.0`. The message should look something like `2016-04-26 Node.js v6.0.0 (Current) Release`.
191191

192192
Create a tag using the following command:
193193

0 commit comments

Comments
 (0)