Sync26 meta-release (ex-Fall26)
Timeline
Sync26 meta-release schedule (transition period)
APIs should preferably target the Sync26 meta-release, and align with Spring26 Commonalities and ICM.
Milestone status
Milestone | Target date | Status |
|---|---|---|
M1 (Commonalities & ICM) | nov 30 | from Spring26 |
M0 | jan 15 | kick-off preparation |
M2 (Commonalities & ICM) | jan 31 feb 15 feb 19 | from Spring26 |
M4 (Commonalities & ICM) | mar 15 mar 22 apr 15 apr 30 may 19 may 21 | from Spring26 |
M1 (API Sub Projects) | apr 30 may 31 | M1 passed: All Fall25 APIs and other APIs that want to participate in Sync26 MUST
|
M3 (API Sub Projects) | jun 15 jun 30 | impact from Spring26 delay |
M4 (API Sub Projects) | sep 30 |
|
M5 | oct 15 |
|
M6 | oct 31 |
|
Commonalities & ICM
The Commonalities and ICM releases to be used in the Sync26 meta-release are released in Spring26.
API version release status
The following table presents the progress of the meta-release or the APIs (for the APIs that have adopted the automated release management process).
Using the initial “bulk PR”, API projects need to include the ne release-plan.yaml in their repository. To reflect the release intent for Sync26, at least include the meta-release Sync26 and the API name(s), then merge the bulk PR. If no other changes are made, the API will be shown with Release State “None”. The target release and other info in the plan can be done later through normal PRs when the team has made their decisions.