You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 3
Next »
FOR REFERENCE ONLY: CNTT Elbrus release planning
| Milestone | Description | Tasks / Criteria | Delta | Notes |
|---|
| M0 | Start of release | None |
|
|
| M1 | Release planning | - RM & RA versions selected
- Features selected for implementation from specifications
- Major upstream component versions determined
- Project release plans submitted
- Release schedule approved
| M0+4w |
|
| M2 | Code Freeze | - Initial RC(s) ready for RI implementation
- Jira issues assigned to release
| M0+14w |
|
| M3 | RC Validation Testing | - RC validation testing completed
- High priority Jira issues resolved
- Preliminary documentation completed
| 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
- Marketing highlights page completed
| M0+25w |
|
| M6 | Release | - Release artifacts available for distribution
- Standalone project self-release completed
| M0+26w |
|
Notes
Attendees: David, Al, Jim, Trevor
- Plan for set of milestones for software development, since we have agreed that specifications and software will use different cadences.