M5

• 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
• Release content finalized
• Creation and submission of marketing highlights
• Finalize version numbering for RM, RA1, RA2
• Traceability matrix updated

M4

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

Notes on M4

• RI1 is unsupported per TSC agreement at M1
• RI2 validation is ambiguous since we have not yet established criteria 

M3

• RC1 - RC workstream lead confirms successful completion of validation test plan (statement in TSC meeting or email to TSC list)
• 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)
• RI1 development completed (confirmed by workstream lead)
• RI2 development completed (confirmed by workstream lead)
• Specification content created matching high level issues (M2)
  • Workstream leads review PR status with TSC
  • PRs indicated as closed on the specification dashboard

Notes on M3

• RI1 is unsupported per TSC agreement at M1

M2

• RC1 - ready to begin validation testing (statement in TSC meeting or email to TSC list)
• RC1 - coverage of RA specified
• 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)
• Software development team review of RA1 completed.  GitHub issues submitted.
  • Barometer
  • Airship
  • VinePerf
  • CIRV
• Software development team review of RA2 completed.  GitHub issues submitted (Lakelse RA2 Review)
  • Airship
  • Barometer
  • Kuberef
  • VinePerf
  • CIRV
• High level issues identified by specification team and appear on dashboard.

Notes on M2

• The team determined that RA1 had been reviewed sufficiently last fall and that there have not been many changes, therefore, the review of RA1 was skipped in favor of spending the time available on reviewing RA2.

M1

• 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
• Workstream leads recommend RA features to TSC for implementation in the release
• RC validation plan created or updated
• RI validation plan created or updated
• Release string "Lakelse Release" created in Jira (already done)
• Release string "Lakelse Release" created in GitLab 
• Release milestone dates added to GitLab
• 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

• Approved by TSC on July 13 with acknowledgment that there is no support for RI1 in Lakelse.