<meta-release name> meta-release
Instructions:
When copying this page for the planning of a new meta-release:
In the page title, change <meta-release name> to the actual meta-release name (e.g. Fall25, Spring26, etc).
Save the page
At the bottom of the page, click the “add label” button and create the new meta-release label: "camara-<meta-release name in lower case>" e.g. camara-spring26, camara-fall26, etc.
Edit the page as follows:
Remove the non-applicable timeline figure and text above it
Remove the non-applicable milestone dates table
If the dates need to be adjusted, edit the PlantUML source of the timeline figure.
In the "API version release status" section, update the macro to use the new meta-release label in the "Labels" section
In the "API version release review status" section, update the macro to use the new meta-release label in the "Labels" section
In the "API release contacts" section, update the macro to use the new meta-release label in the "Labels" section
Then remove these red lines.
Timeline
Spring meta-release schedule
Fall meta-release schedule
Milestone status
Milestone | Target date | Status |
|---|---|---|
M0 | sep 30 | kick-off preparation |
M1 (Commonalities & ICM) | oct 15 | |
M2 (Commonalities & ICM) | dec 07 | |
M3 (Sub Projects) | dec 21 | |
M4 (Commonalities & ICM) | feb 14 |
|
M4 (Sub Projects) | feb 28 | |
M5 | mar 5 | |
M6 | mar 31 |
Milestone | Target date | Status |
|---|---|---|
M0 | mar 31 | kick-off preparation |
M1 (Commonalities & ICM) | apr 15 | |
M2 (Commonalities & ICM) | jun 07 | |
M3 (Sub Projects) | jun 21 | |
M4 (Commonalities & ICM) | aug 15 |
|
M4 (Sub Projects) | aug 31 | |
M5 | sep 15 | |
M6 | sep 30 |