| Milestone | Description | Software Criteria | Specification Criteria (adapted from Elbrus release) | Delta | Notes |
|---|
| M0 | Start of release | None | None |
|
|
| M1 | Release planning | - Major Determine version alignment with major upstream component versions determined (e.g., OpenStack, Kubernetes)
- RM & RA versions selected
- Features Prioritized features selected for implementation from specifications
- RC & RI effort scoped with owners identified
- Project release plans submitted
- Release schedule approved
| - High level scope created
- Created: list of Github issues with the initial content or the content proposal
- Release schedule approved approval requested
| M0+4w |
|
| Release schedule approved |
| M2 | Contents Freeze | - Initial RC(s) ready for RI implementation
- Jira issues assigned to release
| - Updated content via PRs, matching to issues created
| M0+14w |
|
| M3 | RC Validation Testing | - RC validation testing completed
- High priority Jira issues resolved
- Preliminary documentation completed
| - Completion of editing and proof reading of new/updated content via PRs
| M0 + 18w |
|
| M4 | RI Validation Testing | - RI validation testing completed
- High priority Jira issues resolved
|
| M0+22w |
|
| M5 | Release Readiness | - Final documentation completed
- RI cookbook completed
- Manifest completed
- Remaining Jira issues assigned to the release closed or pushed to next release
- Release artifacts prepared
- Standalone project testing completed
| - Release content finalized
- Creation and submission of marketing highlights
| M0+25w |
|
Marketing highlights page completed |
| M6 | Release | - Release artifacts available for distribution
- Standalone project self-release completed
| - Release packaged (branched in GitHub), specification documents presented in the ReadTheDocs format
| M0+26w |
|