Instructions:
After copying this page
- Update the page title to the meta-release name (e.g. Fall25, 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.
- Update the below macro by setting the "Including text" filter to the meta-release name (e.g. Fall25, Spring26 etc). Then remove this line
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 | 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 | Actual date |
---|---|---|---|
M0 | 15/04 | scope definition |
|
M5 | 15/09 | ||
M6 | 30/09 |
Commonalities & ICM status
Each Working Group shall update the line to the below for the version they plan to release at the M0 date.
...
Working Group | Target version | M0 date | M1 date | M2 date | M5 date | Current version | Current version release package |
---|---|---|---|---|---|---|---|
Commonalities | <link to latest> | ||||||
ICM | <link to latest> |
API version status
Each API Sub-project shall add a line to the below tablefor each API they plan to release at M3 datecreate / maintain a release tracker page for each versions 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 link in the "Current API version release package" column shall be updated with each milestone to point to the associated latest release package.
Page Properties Report | ||
---|---|---|
|
...
|
...
|
...
|
...
|
...
|
...
Current API version
...
|