This section explains the meta-release plan, schedule and progress reporting on the planed a meta-release.
Meta-release plan
For each meta-release, a meta-release plan shall be created that will visualize the progress of the meta-release. It covers the status of
- Commonalities and ICM releases
- 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.
- A meta-release cycle covers 6 months between M0 and M6, including holidays.
- The first CAMARA meta-release is Fall24, followed by Spring25, Fall25, etc.
The following figures provide the typical planning and milestone dates for a Spring or Fall meta-release.
Actual dates for a given meta-release can be found through the list of CAMARA meta-releases.
Spring meta-release plan
Fall meta-release roadmap
Progress reporting on a meta-release
The following actions are requested from the various teams to provide visibility on the progress of a meta-release.
Release Management
The Release Management team shall create a meta-release plan (page) as follows:
- Copy the following page Meta-release <meta-release name>, changing the parent paged to: CAMARA meta-releases (tick the "copy files and images" box).
- Follow the instructions in red on the copied page.
During the meta-release cycle, the Release Management team maintains the meta-release page as follows:
- The actual milestone dates shall be put in the Milestone table when the milestone is achieved.
Commonalities and ICM
The Commonalities and ICM teams shall respectively update and maintain their line on the meta-release page as follows:
- 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)
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
M5 date: to be updated on TSC approval of the public-release PR for M5 with creation date of the public-release
(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.
Public-release tag: updated with the public-release tag once available.
API Sub-projects
API Sub-projects do not need to edit the meta-release page.
An API release of an API Sub-project should automatically show on the meta-release page as soon as an API release tracker has been created under the API Sub-project's API release tracking page for the API version planned to be released in the meta-release.
If an API release is not visible, please make sure to add the meta-release label to the API release tracker page as indicated on that page.