Instructions:
When copying this page for the planning of a new meta-release:.
Remove the text above the applicable timeline figure
Remove the non-applicable timeline figure and text above it
Remove the non-applicable milestone dates table
If the dates need to be adjusted, edit the 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 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 in the "Labels" section
Then remove these red lines.
Timeline
Milestone status
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
This section is updated by the Commonalities and ICM working groups respectively.
Working Group | Commonalities | ICM |
|---|---|---|
Target version | tbd | tbd |
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
This section lists 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".