Page History

This section explains the processes for meta-release planning, milestone scheduling and progress reporting on the planned a meta-release.

Meta-release plan

For each meta-release, a meta-release plan provides the dates and progress of the meta-release. It covers the status of

• Commonalities and ICM releases
• The release of the API versions that are planned to be included in the meta-release.

Meta-release schedule

There are 2 CAMARA meta-releases per year: a Spring meta-release and a Fall meta-release. These are called SpringYY and FallYY respectively, where YY is the (short) year number.

...

Actual dates for a given meta-release shall be managed on the dedicate meta-release plan listed here: CAMARA meta-releases.

Spring meta-release schedule

Fall meta-release schedule

Planning and progress reporting on a meta-release

The following actions are requested from the various teams to plan and provide visibility on the progress of a meta-release.

Release Management

The Release Management team shall create the meta-release plan (page) under CAMARA meta-releases as follows:

...

• the Commonalities and ICM data is updated directly on the meta-release page by the respective teams.
• the API data is managed by the API Sub-project teams on their API release tracker page(s) and pulled into the meta-release page automatically.

Commonalities and ICM

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

...

• As soon as possible after M1, fix the scope of the release in a dedicated GitHub issue, e.g. called "Commonalities or ICM scope Fall24".
• Whenever a new pre-release is made available, the (Pre-)release tag column shall be updated with the release tag link for the Commonalities and ICM version respectively.
• The actual milestone dates shall be put in the table when the milestone release is approved. 
• Once TSC approval is given at M2, the target public-release version (release tag and release package) shall be created and shall be used by the API Sub-projects to work with. It will also be used for M5 for inclusion in the meta-release and the meta-release page shall be updated with M2 date and the public-release tag.

API Sub-projects

API Sub-project teams shall create and update the API release tracker for each of their API version(s) as follows: 

...

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

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:

...