Evolving the Node.js Release Schedule#1
Evolving the Node.js Release Schedule#1UlisesGascon wants to merge 6 commits intoevolving-release-schedulefrom
Conversation
👋 Codeowner Review RequestThe following codeowners have been identified for the changed files: Team reviewers: @UlisesGascon/releasers Please review the changes when you have a chance. Thank you! 🙏 |
- Add "About the Alpha Channel" section explaining: - Target audience (library authors, CI pipelines) - Expectations (no security patches, API may change) - Rationale (feedback loop + V8 updates) - ABI stability noted as TBD - Simplify schedule phases: Alpha → Current → LTS (29 months) - Remove Active LTS / Maintenance distinction - Add Ubuntu release cycle comparison for familiarity - Clean up v26/v27 timelines (remove Maintenance milestone)
UlisesGascon
force-pushed
the
release-announcement
branch
from
687fe4b to
62a4ff2
Compare
| Starting with `v27` in 2027: | ||
|
|
||
| - **One major release per year** (April), with LTS promotion in October |
There was a problem hiding this comment.
If v27 is scheduled for 2027, it means that the new schedule starts with v26 (or at least most of it, such as 1 release per year, every release becomes LTS, and version number aligns with year)
There was a problem hiding this comment.
Good observation! The version-year alignment is coincidental for v26 since it follows the existing even-numbered LTS pattern. The key difference starts with v27: there won't be an odd v27 release in October 2026. Instead, we'll have v27 Alpha (nightly builds), and v27 itself will become LTS... which wouldn't happen under the old schedule where odd releases didn't get LTS status.
- Add comprehensive 10-year schedule table (v27-v36) with Alpha, Release, LTS, and End of Life dates - Clarify that Alpha channel uses only nightly builds (no formal alpha releases, reducing releaser workload) - Link to nodejs.org/download/nightly for early testing - Reorder Timeline section: v26 → v27 → 10-year table
RafaelGSS
left a comment
RafaelGSS
left a comment
There was a problem hiding this comment.
Echoing some questions from nodejs-release-private channel, so we have all these things well defined before publishing this
- We get a version of alpha in April, and it will last 5 months. During those 5 months, all commits that land on main will go through the
alphaor majors landed on main during this period will only be released in the next year's alpha version?\ - How are we going to communicate the difference between Alpha and Nightly?
- What would be the period of releases for Alpha? Once every other week, like Current releases?
- What will be the rules to ship semver-major during on alpha phrase
|
In favor of nodejs#8631 |
3 participants
No description provided.