You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 16
Next »
CNTT Elbrus release planning (for reference)
Proposed milestones
Milestone | Description | Software Criteria | Specification Criteria (adapted from Elbrus release) | Delta | Notes |
---|
M0 | Start of release | None | None |
|
|
M1 | Release | - RM & RA versions selected
- Prioritized features selected for implementation from specifications
- RC & RI effort scoped with owners identified
- Project release plans submitted
| - High level scope created
Created: list of Github issues with the initial content or the content proposal
- Release schedule approval requested
| M0+4w | Pankaj Goyal: Suggested changes
|
Release schedule approved |
M2 | Contents Scope Freeze | - Initial RC(s) ready for RI implementation
- Jira issues assigned to release
| Updated content via PRs, matching to issues created- High Level Issues created as per scope
- Start creating content
| M0+14w |
|
M3 | Code: RC Validation Testing Spec: Content Freeze | - RC validation testing completed
- High priority Jira issues resolved
- Preliminary documentation completed
| Completion of editing and proof reading of new/updated content via PRs
- 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
| 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 |
|
Schedule Proposal for June Release (compressed to 16 w)
Milestone | Date | Notes |
---|
M0 | |
|
M1 | |
|
M2 | |
|
M3 | |
|
M4 | |
|
M5 | |
|
M6 | |
|
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.