Test meta-release page layout
- Casey Cain
- Tanja de Groot
Timeline
Meta-release milestone datesย
The possible status values are described in the Milestone release status section on the following page:ย Meta-release Milestones.
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 | Public-release tag |
|---|---|---|---|---|---|---|---|---|
Commonalities | ย | ย | ย | ย | ย | ย | <link> | <link> |
ICM | ย | ย | ย | ย | ย | ย | <link> | <link> |
ย
This section is to be updated by the Commonalities and ICM working groups respectively.
Working Group | Commonalities | ICM |
|---|---|---|
Target version | 0.4.0 | 0.2.0 (tbc) |
Target scope | ||
M1 date | yyyy-mm-dd | yyyy-mm-dd |
M2 date | yyyy-mm-dd | yyyy-mm-dd |
(Pre)release tag | <release tag link> | |
M5 date | yyyy-mm-dd | yyyy-mm-dd |
Public-release tag | <release tag link> | <release tag link> |
ย
Working Group | Target version | Target scope | M1 date | M2 date | (Pre)release tag | M5 date | Public release tag |
|---|---|---|---|---|---|---|---|
Commonalities | 0.4.0 | yyyy-mm-dd | yyyy-mm-dd | yyyy-mm-dd | <release tag link> | ||
ICM | 0.2.0 (tbc) | yyyy-mm-dd | yyyy-mm-dd | <release tag link> | yyyy-mm-dd | <release tag 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:ย API release trackers.
ย
ย
ย
ย
ย
ย
ย