...
- M0:
- Request the TSC to declare the meta-release kick-off
- Request the Commonalities and ICM teams to prepare for 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.
- M4: start acceptance apprioval phase for proposed API versions
- 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 the next meta release - A release retrospective page is available to all to add comments, feedback and suggestions for improvement.
The actual milestone dates shall be put in the Milestone table when the milestone is achieved.
...
Meta-release progress is visible on the meta-release pageplan created for each meta-release. The data is obtained as follows:
...