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 text above the applicable timeline figure
Remove the non-applicable
timeline timeline figure and text above it
Remove the non-applicable milestone dates table
if If the dates need to be adjusted
: here are , edit the
source pictures -picture display size = 960px and middle size.PlantUML source of the timeline figure.
In the "API version release status" section, update the macro by adding the newly created meta-release label in the "Labels" section
In the "API version release review status" section, update the macro
adding a filter using by adding the newly created meta-release label in the "Labels" section
In the "API release contacts" section, update the macro by adding the newly created meta-release
label label in the "Labels" section
Then remove these red lines.
Table of Contents |
---|
Timeline
...
Spring meta-release schedule
Plantumlcloud | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Fall meta-release schedule
Plantumlcloud | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Milestone status
Milestone | Target date | Status | Actual date | Comment |
---|---|---|---|---|
M0 |
09-30 | kick-off preparation |
|
|
M1 (Commonalities & ICM) | 10-15 |
M2 (Commonalities & ICM) |
12-07 | |||
M3 (Sub Projects) |
12-21 | |||
M4 (Sub Projects) | 02-28 |
M5 | 03-15 |
M6 | 03-31 |
Milestone | Target date | Status | Actual date | Comment |
---|---|---|---|---|
M0 |
03-31 | kick-off preparation |
|
|
M1 (Commonalities & ICM) | 04-15 |
M2 (Commonalities & ICM) |
06-07 | |||
M3 (Sub Projects) |
06-21 | |||
M4 (Sub Projects) | 08-31 |
M5 | 09-15 |
M6 | 09-30 |
Commonalities & ICM
...
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.
...
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 release.
In the below table,
...
This section is updated by the Commonalities and ICM working groups respectively.
Working Group | Commonalities | ICM |
---|---|---|
Target version | 0.5.0 | 0.3.0 |
Target scope | <shortened issue link> | <shortened issue link> |
(Pre-)release tag | <shortened release tag link> | <shortened release tag link> |
M1 date | yyyy-mm-dd | yyyy-mm-dd |
M2 date | yyyy-mm-dd | yyyy-mm-dd |
Public-release tag | <shortened release tag link> | <shortened release tag link> |
M5 date | yyyy-mm-dd | yyyy-mm-dd |
Patch date | yyyy-mm-dd | yyyy-mm-dd |
API version release status
Below are the API release trackers of the API versions presented by the Sub Projects for this meta-release.
The below table is automatically pulled from the API release trackers owned by the Sub Projects.
The individual API release trackers are in the first column called "API version".
Page Properties Report | ||||
---|---|---|---|---|
|
...
|
...
|
...
|
...
|
API version release review status
Page Properties Report | ||||||||
---|---|---|---|---|---|---|---|---|
|
...
|
API release contacts
Page Properties Report | ||||||||
---|---|---|---|---|---|---|---|---|
|
...
|