Release Process Milestone Planning

• Determine version alignment with major upstream component (e.g., OpenStack, Kubernetes)
  • 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

• 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

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
  

Code: RI Validation Testing

Spec: Proofreading

• RI validation testing completed
• High priority Jira issues resolved

• Proofreading: Validate content and make corrections
• No new content

• 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

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