...
Note: this table is ONLY intended to identify criteria for the milestones (i.e., a checklist to determine whether the milestone has been reached). It does not speak to how these items will be done, or when they will be initiated. Those will be determined separately.
| Milestone | Description | Software Criteria | Software Processes | Specification Criteria (adapted from Elbrus release) | Specification Processes | Delta | Notes |
|---|
| M0 | Start of release | None |
| None |
|
|
|
| M1 | Release Definition | - Determine version alignment
- RC & RI effort scoped with owners identified
- RM & RA versions selected
- Note: RI version aligns with RA version (e.g., RI2 version number will be identical to the selected RA2 version)
- Note: the RA version selected will not be the same RA version that is currently in process with the specification team (N-1)
- Note: RA specifies Openstack/Kubernetes
- Prioritized features selected for implementation from specifications
|
RC & RI effort scoped with owners identified- Project release plans submitted
- Note: submission of a project release plan also serves as an intent-to-participate notification
| - Version alignment
- RI owner initiates community discussion with stakeholders (weekly technical discussion, email, etc.)
- Develop consensus
- RI owner(s) make recommendation to the TSC
- TSC votes
| |
| M0+4w | |
| Release schedule approved |
| M2 | Scope Freeze | - Software development review of PRs completed
- Initial RC(s) ready for RI implementation
- Jira issues assigned to release
|
| - High Level Issues created as per scope (including review and feedback by software team)
|
| M0+14w |
|
| M3 | Code: RC Validation Testing Spec: Content Freeze | - RC validation testing completed
- High priority Jira issues resolved
- Preliminary documentation completed
|
| - Content created matching issues
- Issues continue to be created
|
| M0 + 18w |
|
| M4 | Code: RI Validation Testing Spec: Proofreading | - RI validation testing completed
- High priority Jira issues resolved
|
| - Proofreading: Validate content and make corrections
- No new content after this point for this release
|
| 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
- Finalize version numbering for RM, RA1, RA2
|
| 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 |
|
Notes from release process discussion at weekly technical meeting (March 15, 2021): Anuket Weekly Technical Discussions - 2021.03.15#Releasemilestones(M1)-Releaseplanning-
...