M5 (7/25/2023)

•  Final documentation completed
•  RI cookbook completed
•  Remaining Jira issues assigned to the release closed or pushed to next release
•  Prepare release artifacts
  • Tag the version of artifacts to be released
    •  releng job updated to use release branch instead of master
  • Release manager collects artifact references from PTLs and communicates those to releng
  • Releng moves artifacts to hosting location and provides URLs to RM
  • RM verifies URLs
  • RM provides confirmed URL list to website manager (aka Brandon) for publication on the website
•  Standalone project testing completed
•  Verify that there are no unmerged patches
•  Release content finalized
•  Creation and submission of marketing highlights
•  Finalize version numbering for RM, RA1, RA2
  • pull/3382 - merged
  • pull/3402 - created
•  Traceability matrix updated

Notes on M5

M4-S (6/27/2023)

•  Proofreading completed (that RA1 build is fixed). (2023-06-27 TSC Agenda and Minutes)

Notes on M4-S

M4 (5/2/2023) - New Date 5/16

•  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
•  Specification content created matching high level issues (M2) (Note: moved from M3, per TSC agreement Mar 29, 2022)
  •  Workstream leads review PR status with TSC
  •  PRs indicated as closed on the specification dashboard

Notes on M4

M3 (4/4/2023) - New Date 5/16

•  RC2 - RC workstream lead confirms successful completion of validation test plan (statement in TSC meeting or email to TSC list)
•  High priority Jira issues resolved (closed or assigned to future release)
•  Preliminary documentation completed (confirmed by DOCs team)
•  RI2 development completed (confirmed by workstream lead)

Notes on M3

M2 (3/1/2023)

•  RC2 - ready to begin validation testing (statement in TSC meeting or email to TSC list)
•  RC2 - coverage of RA specified
•  Jira issues assigned to release for each participating project (should reflect work described in project release plan)
•  High level issues identified by specification team and appear on dashboard.

Notes on M2

M1 (2/1/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 
•  Release string "Orinoco Release" created in GitHub
•  Release milestone dates added to GitHub
•  PTLs submit project-level release plans
•  Workstream leads complete specification planning template for release
•  RC workstream leads propose plan for RC development (based on an updated RA)

Notes on M1

27 Mar - Gergely Csatari created Ticket for String in Jira.