Page Comparison

...

Milestone	Description	Software Criteria	Software Processes	Specification Criteria (adapted from Elbrus release)	Specification Processes	Delta
M0	Start of release	None		None
M1	Release Definition	Agreement on scope and versions 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 Project release plans submitted Note: submission of a project release plan also serves as an intent-to-participate notification	Agreement on scope and versions RI (Note: aligned with RA version for which an RC exists, or which will be completed before RI) RI workstream lead (WSL) 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 RC validation plan created or updated RC lead(s) confirm validation plan ready RI validation plan created and or updated RI lead(s) confirm validation plan is ready	High level scope created	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
M1	Release Definition	Release schedule approved (Release manager prepares schedule and presents to TSC for feedback and approval)				M0+4w
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 Issues appear on project dashboard	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) RI development is completed Confirmed by RI workstream lead(s)	Content created matching issues Note: this does NOT mean that the creation of issues will stop. Issues will continue to be created as needed.	Content created matching issues Only scope covered by closed PRs is included in the release Workstream leads present the closed PRs to the TSC RM, RA(s), RC(s), RI(s) PRs are marked complete in the project dashboard	M0 + 18w
M4	Code: RI Validation Testing Spec: Proofreading	RI validation testing completed High priority Jira issues resolved	RI validation testing completed The lead for each RI presents the validation plan and results to the TSC and confirms that testing is completed. Cédric Ollivier : What about Jenkins ? Here is the live run about RC1 (OpenStack Train / OPNFV Jerma). JIRA is falsy here (release process vs true verification) https://build.opnfv.org/ci/view/functest/job/functest-jerma-daily/487/ High priority Jira issues resolved Confirmed by release manager	Proofreading: Validate content and make corrections No new content after this point for this release	Proofreading All issues in to do list (dashboard) should be completed or backlogged.	M0+22w
M5	Release Readiness	Final documentation completed RI cookbook completed Remaining Jira issues assigned to the release closed or pushed to next release Release artifacts prepared Standalone project testing completed	Final documentation Track issue in Jira or equivalent RI Cookbook Track issue in Jira or equivalent Jira cleanup Cédric Ollivier : a bug could remain open if tracked by release notes. No need to falsy close it or to change the criteria to please the release management process. Verified by release manager Release artifacts Questions: Link to individual docs in github, or just point to main repo? Do we have any format requirements for software artifacts (container, RPMs, etc.)?	Release content finalized Creation and submission of marketing highlights Finalize version numbering for RM, RA1, RA2 Traceability matrix	Traceability Matrix (RI=>RA, RC=>RA, RA=>RM) Captured by current specification documentation processes	M0+25w
M5	Release Readiness	Marketing highlights page completed				M0+25w
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

...

Versions Compared

Old Version 42

New Version 43

Key