Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Timeline

Meta-release milestone dates 

The possible status values are described in the Milestone release status section on the following page: Meta-release Milestones.

MilestoneTarget dateStatusActual date
M004-15

scope definition

 2024-04-18

M104-30

M206-15

M306-15

M408-30

M509-15

M609-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.

...

Working GroupTarget versionTarget scopeM0 dateM1 dateM2 dateM5 date(Pre)release tagPublic-release tag
Commonalities





<link><link>
ICM





<link><link>


This section is to be updated by the Commonalities and ICM working groups respectively.

Working GroupCommonalitiesICM

Target version

0.4.00.2.0 (tbc)

Target scope

Commonalities/issues/175IdentityAndConsentManagement/issues/146

M1 date

yyyy-mm-ddyyyy-mm-dd

M2 date

yyyy-mm-ddyyyy-mm-dd

(Pre)release tag

r0.4.0-alpha.1<release tag link>

M5 date

yyyy-mm-ddyyyy-mm-dd
Public-release tag<release tag link><release tag link>


Working GroupTarget versionTarget scopeM1 dateM2 date(Pre)release tagM5 datePublic release tag
Commonalities0.4.0Commonalities/issues/175yyyy-mm-ddyyyy-mm-ddr0.4.0-alpha.1yyyy-mm-dd<release tag link>
ICM0.2.0 (tbc)IdentityAndConsentManagement/issues/146yyyy-mm-ddyyyy-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

...

  • 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.

...