...
For each meta-release, a meta-release plan provides the dates and progress of the meta-release. It covers the status of
- Commonalities Cmonalities and ICM releases
- The release of the API versions that are planned to be included in the meta-release.
...
The Commonalities and ICM teams shall respectively update and maintain their information on the meta-release page following the below steps.
Commonalities and ICM release tracking
The release tracking for Commonalities and ICM is done directly on the meta-release plan of the active meta-release accessible here: CAMARA meta-releases.
The following explains the fields of the Commonalities and ICM table on the meta-release pageplan:
- Target version: the public-release version expected to be published as part of the meta-release (latest by M1 but may be put earlier if known).
- Target scope: link to GitHub issue defining the release scope (as soon as issue is created after M1)
M1 date: actual alpha release milestone date - update also the pre-release tag field
M2 date: actual release-candidate milestone date - update also the pre-release tag field
- (Pre)release tag: updated with each new pre-release and at each milestone to point to the latest pre-release tag. Different alpha or release-candidate pre-release tags can be put here for usage by other teams, even if milestones are not yet reached.
M5 date: to be updated after TSC approval of the public-release PR for M5 with creation date of the public-release
Public-release tag: updated with the public-release tag once available.
Milestone activities
The activities of the Commonalities and ICM teams during the release cycle are the following:
...