...
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 retrospective page.
Release Management
The Before M0, the Release Management team shall create the meta-release plan (page) under CAMARA meta-releases 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.
- Request the TSC to declare the meta-release kick-off.
During the meta-release cycle, the Release Management team maintains the meta-release page as follows:
- M0: Request the TSC to declare announce the meta-release kick-off on the CAMARA mailing list (all@lists.camaraproject.org). This announcement indicates:
- Request the Commonalities and ICM teams to prepare for M1 the M1 the scope definition of what they plan to put in the meta-release
- Request all API Sub-projects release contacts through the release management mailing list to create the API release tracker for their next planned API version(s) as described here: API release tracking process.
- the Outreach Committee to start preparation of marketing activities based on information in the meta-release plan
- M2: check for Commonalities and ICM that all release assets are available in their public-release PR. If OK, request TSC to approve creation of public-release of Commonalities and ICM. Check that the meta-release plan is updated with public-release information of Commonalities and ICM.
- M4: start apprioval approval phase for proposed release-candidate API versions - Approval can start as soon as an API Sub-project indicates "M4: ready for RM" on the API release tracker in the comments field. It is not necessary to wait for the actual M4 date if an API release is ready before.
- M5: publish the meta-release - this is done by ensuring all approved APIs are listed in the meta-release plan and their M5 date and public-release tag and package are available.
- M6: Conduct a meta-release retrospective as input to for the next meta release - A meta-release retrospective page is available to all to add comments, feedback and suggestions for improvement. Improvement proposals are submitted for approval to TSC.
The actual milestone dates and status shall be put in the Milestone table updated on the meta-release plan when the milestone is achieved.
...
- the Commonalities and ICM data is updated directly on the meta-release page plan by the respective teams.
- the API data is managed by the API Sub-project teams on their API release tracker pagetracke(sr) and pulled into the meta-release page plan automatically.
Commonalities and ICM
...
- 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 the meta-release page shall be updated with M2 date and the public-release tag. This public-release shall be used by the API Sub-projects to work with for their release-candidates. 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:
...