Page Comparison

...

...

NOTE: in case of differences between this page and the milestone table, or in case of missing points or proposed changes or other feedback, please use the Meta-release feedback page.

Release Management

During the meta-release cycle, the Release Management team actions for progressing the meta-release are the following:

...

Meta-release tracking

To be able to track a meta-release, the Release Management team

...

first create the meta-release plan

...

under the CAMARA meta-releases

...

page as

...

follow:

• Copy Go to the following page Meta-release <meta-release name>, and create a copy, changing the parent paged page to: CAMARA meta-releases (make sure to tick the "copy files and images" box).
• Follow the instructions in red on the copied page.

This results in the new meta-release plan to be used for tracking the meta-release.

Milestone activities

• Request the TSC to declare the meta-release kick-off.

...

The actual milestone dates and status shall be updated on the meta-release plan when the milestone is achieved.

Release milestone status

The overall milestone status is reflected by the milestone status table on the meta-release plan. Its content is managed by the Release Management team and shall have values defined as follows:

Commonalities and ICM

The Commonalities and ICM teams shall respectively update and maintain their information on the meta-release page following the below steps.

...

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

...

• If an API release is not visible, please check that the correct meta-release label is added to the API release tracker page. 

Milestone activities

The following are the actions for milestones:

...

• M0: Declare meta-release kickoff 
  • Approve Commonalities and ICM scope
  • Approve final alpha release PRs of Commonalities & ICM
• M1
  • Approve final release-candidate PRs of Commonalities & ICM
• M2
  • Review scope of selected APIs (case by case selection)
• M3
  • Formal approval of the Commonalities & ICM public-release PRs
  • Formal approval API public-release PRs
• M4
  • Meta-release approval
• M5
  • Provide feedback on meta-release
  • Meta-release improvements approval
• M6

Release milestone status

The milestone status values on the meta-release pages are managed by the Release Management team and shall have values defined as follows:

...

API final release-candidate PR

API public-release PR

...

API final release-candidate

API public-release for M5

...