Meta-release <meta-release name>

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).
At the top of the page, click the label icon and create the new meta-release label: "camara-<meta-release name>" e.g. camara-fall25, camara-spring26, etc.
Remove the non-applicable timeline
Remove the non-applicable milestone dates table
if the dates need to be adjusted: here are the source pictures -
- picture display size = 960px and middle size.
In the "API version status" section, update the macro adding a filter using the newly created meta-release label
Then remove these red lines.

Timeline

Milestone	Target date	Status
M0	30/09	scope definition
M1	15/10
M2	31/12
M3	15/12
M4	28/02
M5	15/03
M6	31/03

Milestone	Target date	Status
M0	31/03	scope definition
M1	15/04
M2	15/06
M3	15/06
M4	31/08
M5	15/09
M6	30/09

Each Working Group shall update the line to the below for the version they plan to release at the M0 date.

In the below table,

Milestone dates shall be updated with the actual dates on which the milestone is achieved.
The link in the Current version release package column shall be updated with each milestone to point to the associated latest release package.

Working Group	Target version	Target scope	M0 date	M1 date	M2 date	M5 date	Pre-release tag	Public-release package
Commonalities							<link>	<link>
ICM							<link>	<link>

Each API Sub-project shall create and maintain a release tracker page for each API version they are working on and planning to release.

In the below table,

Milestone dates shall be updated by each API development team with the actual dates on which the milestone is achieved.
The links shall be updated with each milestone to point to the associated latest tag or release package.