Skip to content

Commit 01ecbeb

Browse files
committed
docs: improve readability
1 parent 23ce3d1 commit 01ecbeb

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

apps/site/pages/en/blog/announcements/evolving-the-nodejs-release-schedule.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@ As of October 2026:
5151

5252
- **One major release per year** (April), with LTS promotion in October.
5353
- **Every release becomes LTS**. No more odd/even distinction - Node.js 27 will become LTS.
54-
- **Alpha channel replaces odd-numbered releases** for early testing.
54+
- **Alpha channel for early testing** with semver-major changes allowed.
5555
- **Version numbers align with the year of the first Current release and transition to LTS**: 27.0.0 in 2027, 28.0.0 in 2028.
5656
- **Reduced Releasers' burden**.
5757

@@ -68,7 +68,7 @@ Total support: 35 months from release to [End of Life (EOL)](https://nodejs.org/
6868

6969
### About the Alpha Channel
7070

71-
The Alpha channel replaces odd-numbered releases. Alpha releases are signed,
71+
The Alpha channel fills the early-testing role that odd-numbered releases once served, but with a key difference: semver-major changes are allowed during Alpha. Alpha releases are signed,
7272
tagged, and tested through [CITGM](https://github.com/nodejs/citgm). CITGM (Canary in the Goldmine) is a tool we
7373
maintain that runs the test suite of major open-source packages on the upcoming
7474
version of Node.js, which can let us detect ecosystem breakage and notify the

0 commit comments

Comments
 (0)