...
The Commonalities and ICM teams shall respectively update and maintain their information directly on the active meta-release page following the below steps.plan accessible here: CAMARA meta-releases (select the active meta-release from the list).
Release tracking
The release tracking for Commonalities and ICM is done directly by updating the Commonalities and ICM table available on the meta-release plan of the active meta-release accessible here: CAMARA meta-releases (select the active meta-release form the list).
The following explains the fields of this table and when / how it needs to be updated by the Commonalities and ICM table on the meta-release planteams:
| Field | Field explanation | When to update |
|---|---|---|
Target version |
...
| the public-release version |
...
| targeted for the meta-release |
...
| at M0 or when the target scope issue is created | |
Target scope |
...
| link to GitHub issue defining the release scope |
...
| when the issue is created |
...
M1 date |
...
| actual final alpha release milestone date |
...
| when alpha release is created (before M1) | |
M2 date |
...
| actual final release-candidate milestone date |
...
| when public-release is created (before M2) | |
(Pre)release tag |
...
| link to latest pre-release |
...
M5 date: to be updated after TSC approval of the public-release PR for M5 with creation date of the public-release
...
| when a new pre-release is created | ||
M5 date | actual final public-release milestone date | when public-release is created |
| Public-release tag | link to final public-release | when public-release is created |
Milestone activities
The activities of the Commonalities and ICM teams during the release cycle are the following:
...