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
This section is to be updated by the Commonalities and ICM working groups respectively.
| Working Group | Commonalities | ICM |
|---|---|---|
Target version | 1.0.0 | |
Target scope | <issue link> | <issue link> |
M0 date | ||
M1 date | ||
M2 date | ||
M5 date | ||
(Pre)release tag | <tag link> | <tag link> |
| Public-release tag | <tag link> | <tag link> |
API release status
Each API Sub-project shall create and maintain an API release tracker for each API release they are working for the meta-release.
In the below table, all data is automatically pulled from the API Sub-project owned API release trackers.
The API release tracker is the link in the first column called "API".