Release Process Milestone Planning

• 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
• Project release plans submitted
  • Note: submission of a project release plan also serves as an intent-to-participate notification

• Version alignment
  • RI (Note:  aligned with RA version for which an RC exists, or which will be completed before RI)
    1. RI workstream lead (WSL) initiates community discussion with stakeholders (weekly technical discussion, email, etc.)
       1. RM and RA versions
       2. Features from RA selected for implementation
    2. Develop consensus
    3. RI WSL make recommendation to the TSC
    4. TSC votes

• Project plans
  • Software projects will submit a project plan, following the template developed for OPNFV for the Jerma release.

• 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.

Release schedule approved

(Release manager prepares schedule and presents to TSC for feedback and approval)

• Software development review of PRs completed
• Initial RC(s) ready for RI implementation (not required if RI selected at M1 is pre-existing)
• Jira issues assigned to release

• High Level Issues created as per scope (including review and feedback by software team)

Software development review of specifications

1. Developers review specifications being referenced for the current release cycle.
2. Developers create issues in GitHub Issues for the GitHub project that represents the specific specification being reviewed.

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
  

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

• 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

Marketing highlights page completed

• Release artifacts available for distribution 
• Standalone project self-release completed

• Release packaged (branched  in GitHub), specification documents presented in the ReadTheDocs format