docs: add Alpha channel details and simplify LTS terminology

- 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)

Author: UlisesGascon

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

@@ -5,6 +5,7 @@ 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
@@ -39,14 +40,29 @@ Starting with `v27` in 2027:
 |-------|----------|-------------|
 | 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 |
+| LTS | 29 months | Long-term support with security fixes |
 
 Total support: 35 months from release to End of Life.
 
+This model follows a pattern similar to Ubuntu's release cycle: predictable April/October anchors, with interim releases for testing and LTS releases for production.
+
+### About the Alpha Channel
+
+The Alpha channel replaces odd-numbered releases.
+
+**Who it's for:** Library authors and CI pipelines testing compatibility with upcoming breaking changes. Not intended for production use.
+
+**What to expect:**
+- Semver-major changes land during this phase
+- No security patches (only stable releases receive security fixes)
+- API may change between Alpha releases
+- ABI stability guarantees are still being defined and will be documented separately
+
+**Why:** Provides early feedback on breaking changes without maintaining another full release line. Also allows landing V8 updates earlier in the cycle, so we don't ship a single V8 version per year.
+
 ## What's NOT Changing
 
-- **LTS support duration** remains similar (29 months: 12 Active + 17 Maintenance)
+- **LTS support duration** remains similar (29 months)
 - **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.
@@ -59,7 +75,6 @@ Total support: 35 months from release to End of Life.
 |-----------|------|
 | 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.
@@ -71,13 +86,12 @@ Total support: 35 months from release to End of Life.
 | 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.
+This change is the result of discussions across GitHub issues, 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).