You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 27
Next »
CNTT Elbrus release planning (for reference)
Proposed milestones
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 | - 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
| - Version alignment
- RI (Note: aligned with RA version for which an RC exists, or which will be completed before RI)
- initiates community discussion with stakeholders (weekly technical discussion, email, etc.)
- RM and RA versions
- Features from RA selected for implementation
- Develop consensus
- RI WSL make recommendation to the TSC
- TSC votes
- Project plans
- Software projects will submit a project plan, following the template developed for OPNFV for the Jerma release.
- Jira
- Release manager creates common release name string for Jira
| | High Level Scope - Work stream leads complete template (see example from Elbrus planning)
- Present to TSC
- TSC approval
RC - If there is a new or updated RA, then we will need a new, or updated RC. Note that this is NOT necessarily the same RC referenced by the RI under development in the current release cycle. It may be the same, if the plan is to complete an RC before development of the RI within the same release cycle (see M2).
- Affirmation from RC workstream lead that RC will be developed in the current release cycle.
- GitHub
- Release manager sets release name
- Release manager sets milestone dates
| M0+4w | |
Release schedule approved (Release manager prepares schedule and presents to TSC for feedback and approval) |
M2 | Scope Freeze | - Initial RC(s) ready for RI implementation (not required if RI selected at M1 is pre-existing)
- Jira issues assigned to release
| RC Readiness - RC workstream lead confirms RC readiness (email, documented in the TSC, etc), including identifying coverage of the associated RA.
JIRA issues - Release manager confirms that each participating project has assigned issues to the release using the "Fix Version" field in Jira
| - Software development review of PRs completed
- High Level Issues created as per scope (including review and feedback by software team)
| Software development review of specifications - Developers review specifications being referenced for the current release cycle.
- Developers create issues in GitHub Issues for the GitHub project that represents the specific specification being reviewed.
High Level issues created in GitHub - Work stream leads submit GitHub query to release manager that identify the high level issues
| M0+14w |
|
M3 | Code: RC Validation Testing Spec: Content Freeze | - RC validation testing completed
- High priority Jira issues resolved
- Preliminary documentation completed
| RC validation testing - RC workstream lead confirms successful completion of validation test plan (Note: validation test plan is TBD)
- Should be independent of RI
High priority Jira issues resolved - Confirmed by release manager
Preliminary documentation - Confirmed by the DOCs team (Note: currently no DOCs team or integrated documentation)
| - 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-
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.