...
Milestone | Target date | Status | Actual date |
|---|---|---|---|
| M0 | 04-15 | scope definition |
|
| M1 | 04-30 | ||
| M2 | 06-15 | ||
| M3 | 06-15 | ||
| M4 | 08-30 | ||
| 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.
...
This section is to be updated by the Commonalities and ICM working groups respectively.
| Working Group | Commonalities | ICM |
|---|---|---|
Target version | 1.0.0 | |
Target scope | <issue link> | <issue link> |
M0 date | ||
M1 date | ||
M2 date | ||
M5 date | ||
(Pre |
) |
release tag |
...
| <tag link> | <tag link> | |
| Public-release tag | <tag link> | <tag link> |
API release status
Each API Sub-project shall create and maintain a an API release tracker page for each API version release they are working on and planning to contribute to for the meta-release.
In the below table,
...
all data is automatically pulled from the API Sub-project owned API release trackers.
...
The API release tracker is the link in the first column called "API".
...
| Page Properties Report | ||||||||
|---|---|---|---|---|---|---|---|---|
|
...