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 dates
| Milestone | Target date | Status | Actual date |
|---|---|---|---|
| M0 | 09-30 | scope definition |
|
| M1 | 10-15 | ||
| M2 | 12-31 | ||
| M3 | 12-15 | ||
| M4 | 02-28 | ||
| M5 | 03-15 | ||
| M6 | 03-31 |
Milestone | Target date | Status | Actual date |
|---|---|---|---|
| M0 | 04-15 | scope definition |
|
| M1 | 04-30 | ||
| M2 | 06-15 | ||
| M3 | 06-15 | ||
| M4 | 08-30 | ||
| M5 | 09-15 | ||
| M6 | 09-30 |
Commonalities & ICM status
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,
- The Target version is the version planned to be published in the meta-release.
- Its scope is defined in a GitHub issue in the Working Group repository.
- Milestone dates shall be updated with the actual dates on which the milestone is achieved.
- The (Pre-)Release tag and (Pre-)Release package columns shall be updated with each pre-release and at each milestone to point to the latest release assets.
| Working Group | Target version | Target scope issue | M0 date | M1 date | M2 date | M5 date | (Pre-)Release tag | (Pre-)Release package |
|---|---|---|---|---|---|---|---|---|
| Commonalities | <link> | <link> | ||||||
| ICM | <link> | <link> |
API version status
Each API Sub-project shall create and maintain a release tracker page for each API version they are working on and planning to contribute to the meta-release
In the below table,
- All data is pulled from the API Sub-project API release trackers. The actual source page are the links in the first column called "API".
- The information on the source pages shall be updated by each API Sub-project team with each pre-release and with the final public-release.
- The way to fill the API release tracker is described here: How to track an API release