...
Draft messages for the different announcements are prepared on the following page: Release Management announcements
Planning and progress tracking for a meta-release
...
Before M0
Request the TSC to declare the meta-release kick-off.
Provide the release-candidate of the Release Management assets in GitHub including any feedback / other updateswith any updates based on feedback received.
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 to create the API release tracker for their next planned API version(s) as described here: API release trackers.
the Outreach Committee to start preparation of marketing activities based on information in the meta-release plan
Once available, check the final alpha release PRs of Commonalities & ICM and their release asset availability. If OK, submit to TSC for approval.
Provide the public release of the Release Management assets in GitHub for use in the upcoming meta-releaseby the API Sub Projects.
After TSC approval, announce M1 on the release management and maintainers mailing lists.
M1
Check for Commonalities and ICM that all release assets are available in their final release candidate PRs.
If OK, request TSC to approve creation of the final release candidate of Commonalities and ICM.
After TSC approval, and update of the meta-release plan with the final release candidate tags of Commonalities and ICM, announce M2 milestone.
M2
From M1, for all APIs, once available, check the release PR for the release candidate API version, and, if OK, approve PR.
Announce M3 milestone once all approved API release candidates have update their API release tracker.
M3
For all APIs, once available, check the release PR for the final release candidate API version and, if OK, approve PR. 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.
For all APIs, once available, check API public release PR, and, if OK, ask for formal TSC approval.
Announce M4 milestone when all API public releases are approved by TSC.
M4
Check that all API release trackers are updated with their public release tag for the meta-release.
Propose meta-release content to TSC.
After TSC approval, publish the meta-release.
Announce the M5 meta-release on all@lists.camaraproject.org
M5
Review the release process with all teams and identify areas for improvement for the next meta release with all teams. A meta-release feedback page is available to all to add comments, feedback and suggestions for improvement. I
Propose improvements for TSC approval to TSC to be implemented for the next meat-release.
After TSC approval, announce M6 milestone
M6
...