Timeline
Meta-release milestone dates
The possible status values are described in the Milestone release status section on the following page: CAMARA Release Process.
| Milestone | Target date | Status | Actual date |
|---|---|---|---|
| M0 | 04-15 | scope definition | 2024-04-18 |
| 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.
- 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 | 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.