...
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 retrospectivefeedback page.
Release Management
Before M0, the Release Management team shall create the meta-release plan (page) under CAMARA meta-releases as follows:
...
- M0: announce the meta-release kick-off on the CAMARA mailing list (all@lists.camaraproject.org). This announcement indicates:
- the Commonalities and ICM teams to prepare for M1 the scope definition of what they plan to put in the meta-release
- all API Sub-projects release contacts 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 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 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.
...