Page History

• Determine version alignment
  • 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
  • RC & RI effort scoped with owners identified
• Project release plans submitted
  • Note: submission of a project release plan also serves as an intent-to-participate notification

• High level scope created
• Release schedule approval requested

• Software development review of PRs completed
• Initial RC(s) ready for RI implementation
• Jira issues assigned to release

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

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