...
- M0:
- Request the TSC to declare the meta-release kick-off
- Request the Commonalities and ICM teams to update the meta-release page with 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 trackerstracking process.
- M4: start acceptance phase for proposed API versions
- M5: publish the meta-release
- M6: Conduct a meta-release retrospective as input to the next meta release
...
| Milestone | Before M data | After M date |
|---|---|---|
| M0 | kick-off preparation | kick-off done |
| M1 | wip / alpha preparation | alpha available for M2 |
| M2 | wip / release-candidate preparation | release-candidate available for M3 |
| M3 | alpha API wip / preparation | alpha API alpha available for M4 |
| M4 | API wip / release-candidate API preparation | API release-candidate API available for M5 |
| M5 | meta-release preparation | meta-release published |
| M6 | retrospective ongoingpreparation | retrospective donemeta-release concluded |