feat(blog): create post evolving the Node.js Release Schedule

Author: UlisesGascon

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

@@ -0,0 +1,83 @@
+---
+date: '2026-04-01T00:00:00.000Z'
+category: announcements
+title: Evolving the Node.js Release Schedule
+layout: blog-post
+author: The Node.js Release Team
+---
+Starting with `v27`, Node.js will move from two major releases per year to one. This post explains what's changing, why, and what it means for users.
+
+## Why This Change
+
+The current release schedule is 10 years old. It was created during the io.js merger to balance the needs of a growing ecosystem. As one contributor put it at the time, it was "a guess of what enterprises would need."
+
+We now have a decade of data showing how people actually use Node.js:
+
+- Odd-numbered releases see minimal adoption. Users wait for LTS.
+- The odd/even distinction confuses newcomers.
+- Many organizations skip odd releases entirely, upgrading only between LTS versions.
+
+### Volunteer Sustainability
+
+Node.js is maintained primarily by volunteers. While some contributors receive sponsorship, most of the work (reviewing PRs, handling security issues, cutting releases, backporting fixes) is done by people in their spare time.
+
+Managing security releases across four or five active release lines has become difficult to sustain. Each additional line increases backporting complexity. By reducing concurrent release lines, we can focus on better supporting the releases people actually use.
+
+## What's Changing
+
+Starting with `v27` in 2027:
+
+- **One major release per year** (April), with LTS promotion in October
+- **Every release becomes LTS**. No more odd/even distinction.
+- **Alpha channel replaces odd-numbered releases** for early testing
+- **Version numbers align with years**: `v27` in 2027, `v28` in 2028
+- **Maximum 3 active release lines** (down from 5)
+
+### New Schedule
+
+| Phase | Duration | Description |
+|-------|----------|-------------|
+| Alpha | 5 months | Oct to Mar. Early testing, semver-major allowed |
+| Current | 6 months | Apr to Oct. Stabilization |
+| Active LTS | 12 months | Regular updates and fixes |
+| Maintenance | 17 months | Security and critical fixes only |
+
+Total support: 35 months from release to End of Life.
+
+## What's NOT Changing
+
+- **LTS support duration** remains similar (29 months: 12 Active + 17 Maintenance)
+- **Migration windows preserved**. Overlap between LTS versions remains.
+- **Quality standards unchanged**. Same testing, same CITGM, same security process.
+- **Predictable schedule**. April releases, October LTS promotion.
+
+## Timeline
+
+### `v26` (Current Schedule)
+
+| Milestone | Date |
+|-----------|------|
+| Release | April 2026 |
+| Enters LTS | October 2026 |
+| Maintenance | October 2027 |
+| End of Life | April 2029 |
+
+`v26` follows the existing schedule. This is the last release under the current model.
+
+### `v27` (New Schedule)
+
+| Milestone | Date |
+|-----------|------|
+| Alpha begins | October 2026 |
+| Release | April 2027 |
+| Enters LTS | October 2027 |
+| Maintenance | October 2028 |
+| End of Life | March 2030 |
+
+`v27` is the first release under the new schedule.
+
+## Thank You
+
+This change is the result of discussions across [GitHub issues](https://github.com/nodejs/Release/issues/1113), Release Working Group meetings, and [the Collaboration Summit Chesapeake 2025](https://youtu.be/ppi87YjU9x0?si=NFF5WKIGDJE_U-_V&t=6524). We thank everyone who contributed feedback.
+
+For questions or comments, see [GitHub Issue #1113](https://github.com/nodejs/Release/issues/1113).