M5 (XX/XX/2023)

•  Final documentation completed
•  RI cookbook completed Remaining

  For non specification sub-projects the remaining Jira issues assigned to the release closed or pushed to next release by the PTL-s. Movement of the issues reported to the TSC in a mail or in a TSC meeting.

  Project	Mail or meeting

  
  

•  Prepare release artifacts
  • Tag the version of artifacts to be released
    •  releng job updated to use release branch instead of master
  • Release manager collects PTLs collect all artifact references from PTLs and communicates those them to relengLF staff
  • Releng LF staff moves artifacts to hosting location and provides URLs to RM
  • RM verifies URLs
  • the PTL-s and the TSC
  • PTL-s verify URLs
  • PTL RM provides confirmed URL list to website manager (aka Brandon) LF staff and the TSC for publication on the website
•  Standalone project testing completed Verify PTL-s verify that there are no unmerged patches or PR-s. In case of any unmerged patches
•  Release content finalized
•  Creation and submission of marketing highlights
•  Finalize version numbering for RM, RA1, RA2
•  Traceability matrix updated
• or PR-s notify the TSC.
•  A volunteer TSC member or LF staff creates release branch for GitHub
  • Volunteer:
•  PTL-s create sub-project specific release highlights and report the creation to the TSC
•  TSC drafts release announcement blog post and sends it to LF staff for publication
  
•  TSC member finalizes version numbering for the specification projects
  
  • Volunteer

Notes on M5

M4-S (XX/XX2023)

•  Proofreading completed. 

Notes on M4-S

M4 (XX/XX/2023)

•  RI validation testing completed. The lead for each RI presents the validation plan and results to the TSC.
•  High priority Jira issues resolved (closed or assigned to future release)
•  Software projects create release branch

• Non specification sub-projects have a release branch created by a committer of the sub-project or LF staff

  Project	Volunteer	Branch

  
  

•  Specification content created matching high level issues (M2) (Note: moved from M3, per TSC agreement Mar 29, 2022)
  •  Workstream  Specification sub-project leads review PR status with TSC

    
    

    Project	Review meeting or mail

    
    

  •  PRs indicated as closed on the specification dashboard

Notes on M4

M3 (XX/XX/2023)

•  RC2 - RC workstream lead confirms successful completion of validation test plan (statement in TSC meeting or email to TSC list) High For non specification sub-projects participating in the release high priority Jira issues resolved (closed or assigned to future release)  Preliminary last resolved issue is reported to the TSC on mail or in the TSC meeting by the PT
•  For non specification sub-projects participating in the release preliminary documentation completed (confirmed by DOCs team)
•  RI2 development completed (confirmed by workstream lead)
• volunteer TSC members)
  
  • Volunteer:

Notes on M3

M2 (XX/XX/2023)

•  RC2 - ready to begin validation testing (statement in TSC meeting or email to TSC list)
•  RC2 - coverage of RA specified
•  

  For non specification sub-projects participating in the release Jira issues assigned to release

  for each participating project

  (should reflect work described in project release plan) by the PTL-s and reported to the TSC in a mail
  

  Project	Mail

  
  

•  

  High level issues identified by specification

  team

  sub-project teams and appear on

  dashboard.

  the GitHub dashboard by the PTL-s and reported to the TSC in a mail

  Project	Mail

  
  

Notes on M2

M1 (XX/XX/2023)

•  RC Workstream lead(s) recommend RM and RA versions to the TSC for use in the release
•  RI workstream lead(s) recommend RM and RA versions to the TSC for use in the release
•  RC validation plan created or updated
•  RI validation plan created or updated
•  Release string "Orinoco Release" created in Jira Jira by a volunteer TSC member or LF staff
  
  • Volunteer:
•  Release string "Orinoco Release" created in GitHub by a volunteer TSC member or LF staff
  
  • Volunteer:
•  Release milestone dates added to GitHub by a volunteer TSC member or LF staff
  
  • Volunteer
•  PTLs of non specification sub-projects submit project-level release plans Workstream leads if they plan to participate in the release
•  PTLs of specification sub-projects complete specification planning template for the release
•  RC workstream leads propose plan for RC development (based on an updated RA)

Notes on M1

M0 (xx/xx/2023)

•  Release milestones are defined by a volunteer TSC member
  • Volunteer: Gergely Csatari 
•  Release milestones approved by the TSC
•  Volunteer TSC members sends a mail to the Tech Discuss mailing list asking for PTLs of non specification sub-projects to submit project-level release plans if they plan to participate in the release and asking the PTLs of specification sub-projects to complete the specification planning template for the release
  • Volunteer:

Notes on M0