Timeline
Milestone dates
| MilestoneDate | Target date | Status | Actual date |
|---|---|---|---|
| M0 | 15/04 | alph zrelease preparationscope definition |
|
| M1 | 30/04 | ||
| M2 | 15/06 | ||
| M3 | 15/06 | ||
| M4 | 31/08 | ||
| 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.
In the below table,
- Milestone dates shall be updated with the actual dates on which the milestone is achieved.
- The link in the Current version release package column shall be updated with each milestone to point to the associated latest release package.
| Working Group | Target version | M0 date | M1 date | M2 date |
|---|
| M5 date | Current version | Current version release package | |||||
|---|---|---|---|---|---|---|---|
| Commonalities | 0.4.0 (tbc) | <link to latest> | |||||
| ICM | 0.1.0 (tbc) |
APIs progress
| <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 date
In the below table,
- Milestone dates shall be updated 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.
| API name | Target API |
|---|
| version | M3 date | M4 date | M5 |
|---|
| date |
|---|
Current API version | Current API version release package |
|---|
| qod | qod-0.10.0-rc.2 |
| <link to latest> | ||||
| location-verification | location-verification-0.2.0-rc.1 |
| location-retrieval | location-retrieval-0.2.0-rc.3 |
...