Spring26 meta-release (transition schedule)
Please note this schedule is under review until Nov 6 TSC meeting, so some updates may still be done
Timeline
The Spring26 meta-release will primarily focus on Commonalities and ICM updates. No or only limited API releases are expected during this cycle. For details, see the API release guidance section below.
Spring26 meta-release schedule for Commonalities and ICM
Spring26 optional meta-release schedule for initial APIs (not for stable APIs) (NOTE: due to tight schedule in this transition period, it is not recommended to do API releases for Spring26).
Milestone status
Milestone | Target date | Status |
|---|---|---|
M0 | sep 30 oct 02 | kick-off done in TSC meeting of Oct 02 |
M1 (Commonalities & ICM) | oct 15 nov 30 | Cut off date for new issues in the Commonalities / ICM scope issue. |
M1 (API Sub Projects) | dec 15 | APIs to prepare scope issue |
M2 (Commonalities & ICM) | jan 31 |
|
M3 (API Sub Projects) | jan 31 |
|
M4 (Commonalities & ICM) | mar 15 |
|
M4 (API Sub Projects) | mar 31 |
|
M5 | apr 15 |
|
M6 | apr 30 |
|
Commonalities & ICM
This section is updated by the Commonalities and ICM working groups respectively.
Working Group | Commonalities | ICM |
|---|---|---|
Target version | 1.0.0 (tbc) | 0.5.0 (tbc) |
Target scope | #543 (WIP) | #311 (WIP) |
(Pre-)release tag | <shortened release tag link> | <shortened release tag link> |
M1 date | yyyy-mm-dd | yyyy-mm-dd |
M2 date | yyyy-mm-dd | yyyy-mm-dd |
Public-release tag | <shortened release tag link> | <shortened release tag link> |
M4 date | yyyy-mm-dd | yyyy-mm-dd |
Patch date | yyyy-mm-dd | yyyy-mm-dd |
Spring26/Fall26 guidance for API release planning
API releases targeting to be part of Spring26 entail a tight and risky schedule due to alignment pressures with Spring26 Commonalities/ICM milestones and coordination overhead.
This is not recommended except under some agreed conditions:
for stable APIs to be approved by TSC
for initial APIs for consideration by Release Management.
To align with the updated meta-release schedules and ensure a smooth transition, the following guidance applies for API release in Spring26/Fall26 timeframe:
Stable APIs (released in Fall25)
No API release in Spring26 (exception only on TSC approval)
Prepare updates for Fall26, using the finalized Spring26 Commonalities and ICM.
These APIs thereby enter the new meta-release cadence (annual release in the Fall meta-release).
Initial APIs (released in Fall25) and new initial API versions
Initial APIs are not mandated to release as part of a meta-release.
They may choose when to release their next version, following the guidance below:
Before M4 of Spring26 Commonalities/ICM (≈15 March 2026):
API release should be based on Fall25 Commonalities/ICM.
After M4 of Spring26 Commonalities/ICM (≈15 March 2026):
API release should be based on Spring26 Commonalities/ICM.
Depending on their preferred timing, initial APIs can:
Release independently (outside any meta-release)
Target the Fall26 meta-release (recommended)
Request inclusion in the Spring26 meta-release per the above schedule by declaring this intention before API M1 (Dec 15) (for consideration by Release Management).