...

•  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 (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)

...