| pre-M0 activities | - Release Management: prepare meta-release plan
- Commonalities & ICM: define scope and start alpha release development
- TSC: declare M0 - meta-release kickoff
|
|
|
| M0 | Meta-release kickoff | M0 | 0 |
| starts activities for M1 start @ M0 | - Commonalities & ICM: fix scope and develop final alpha release for M1
- API Sub Groups: check Commonalities and ICM scope definition to assess API impact
- TSC: approve Commonalities and ICM scope and final alpha release
- Release Management: Declare M1 - Commonalities and ICM alpha release available
| 2 weeks |
|
M1 | Alpha Commonalities & ICM | M0 + 2 weeks | 2 |
| starts activities for M2 start @ M1 | - API Sub Groups: align to Commonalities and ICM alpha release and provide feedback
- Commonalities & ICM: Fix bugs and prepare final release-candidate for M2
- TSC: approve Commonalities and ICM final release-candidate
- Release Management; declare M2 - Commonalities and ICM release-candidate available
| 7 weeks |
|
M2 | Release-candidate Commonalities & ICM | M1 + 7 weeks | 9 |
| starts activities for M3 start @ M1 | - API Sub Projects: prepare API scope and develop alpha releases, ending by the first release-candidate for M3
- TSC: review scope of APIs (case by case selection)
- Release Management: check API readiness of each API and declare M3 - all API first release-candidates available
| 9 weeks |
|
M3 | Release-candidate APIs (Code Freeze) | M1 + 9 weeks | 9 |
| starts activities for M4 start @ M3 | - API Sub Projects: fix bugs and prepare public-release
- Commonalities & ICM: prepare public-release
- Release Management: check API readiness of each API and declare M4 - all API public-releases available
- TSC: give formal approval of Commonalities, ICM and API (case-by-case) public-releases
| 9 weeks |
|
M4 | Public-release APIs | M3 + 9 weeks | 18 |
activities for M5 starts @ public-release PR for an API | - Release Management: prepare and declare M5 - meta-release availability
- TSC: approve meta-release for M5
| 2 weeks |
|
M5 | Meta-release | M4 + 2 weeks | 20 |
| starts activities for M6 start @ M5 | - Commonalities & ICM: assess meta-release and provide feedback
- API Sub Groups: assess meta-release and provide feedback
- Release Management: assess meta-release, create improvement plan and declare M6 - post-release assessment available
- TSC: approve improvement plan for M6
| 2 weeks |
|
M6 | Post Release Assessment | M5 + 2 weeks | 24 |