Spring26 meta-release
Timeline
The Spring26 meta-release primarily focuses 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. There will be no alpha release of Commonalities. The API teams can look at the Commonalities M1 milestone for details on planned content. |
M1 (API Sub Projects) | dec 15 | Spring26 admitted APIs to prepare M3 |
M2 (Commonalities & ICM) | jan 31 feb 15 feb 19 | M2 declared by TSC on feb 19. |
M3 (API Sub Projects) | jan 31 feb 28 mar 15 mar 22 mar 28 | Delay due to M2 delay. |
M4 (Commonalities & ICM) | mar 15 mar 22 apr 15 apr 28 (Commonalities rc.2) may 19 may 21 (M4) | ICM M4 public release available on March 23. Commonalities M4 M4 public release available on May 22. TSC declared Spring26 M4 for Commonalities and ICM in the May 21 TSC meeting. Delay for Commonalities was due to the decision to include automated bundling of CAMARA common schemas into API yamls. This will help the teams with changes due to the introduction of OWASP security requirements. From this point on, also independent API releases shall target the Spring26 Commonalities and ICM baseline. |
M4 (API Sub Projects) | mar 31 may 27 jun 4 | Spring26 APIs have been released. Spring26 M4 for APIs was declared by TSC on June 4. |
M5 | apr 15 apr 30 may 15 may 29 jun 9 | Spring26 meta-release declared by Release Management. To be announced at All Hands Call on Jun 11. |
M6 | apr 30 may 15 jun 15 jun 18 | Release of the Release Management repository by TSC on June 18 |
Commonalities & ICM
This section is updated by the Commonalities and ICM working groups respectively.
API version release status
Spring26/Sync26 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/Sync26 timeframe:
Stable APIs (released in Fall25)
No API release in Spring26 (exception only on TSC approval)
Prepare updates for Sync26, using the finalized Spring26 Commonalities and ICM.
These APIs thereby enter the new meta-release cadence (annual release in the Sync 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 to use the independent release track and release when their next version when ready, following the guidance below:
Before M4 of Spring26 Commonalities/ICM:
API release should be based on Fall25 Commonalities/ICM.
After M4 of Spring26 Commonalities/ICM:
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 Sync26 meta-release (recommended)
Request inclusion in the Spring26 meta-release per the above schedule by declaring this intention at API M1 (Dec 15) (for consideration by Release Management).
Exceptions for release in Spring26: to be part of the Spring26 meta-release, the API team needs to first submit an issue in Release Management to request Spring26 participation