Release Process Milestone Planning Update for community release management

This page contains a proposal to modify the Anuket release milestone criteria to support Anuket releases without a dedicated Release Manager.

Milestone	Original criteria	Proposed criteria
M0		Release milestones are defined by a volunteer TSC member Release milestones approved by the TSC
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 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)	Release string "Orinoco Release" created in Jira by a volunteer TSC member or LF staff Release string "Orinoco Release" created in GitHub by a volunteer TSC member or LF staff Release milestone dates added to GitHub by a volunteer TSC member or LF staff PTLs of non specification sub-projects submit project-level release plans if they plan to participate in the release PTLs of specification sub-projects complete specification planning template for the release
M2	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.	For non specification sub-projects participating in the release Jira issues assigned to release (should reflect work described in project release plan) by the PTL-s and reported to the TSC in a mail High level issues identified by specification sub-project teams and appear on the GitHub dashboard by the PTL-s and reported to the TSC in a mail
M3	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)	For non specification sub-projects participating in the release high priority Jira issues resolved (closed or assigned to future release) For non specification sub-projects participating in the release preliminary documentation completed (confirmed by DOCs team)
M4	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	For non specification sub-projects participating in the release high priority Jira issues resolved (closed or assigned to future release) last resolved issue is reported to the TSC on mail or in the TSC meeting by the PTL Non specification sub-projects have a release branch created by a committer of the sub-project or LF staff Specification content created matching high level issues (M2) Specification sub-project leads review PR status with TSC PRs indicated as closed on the specification dashboard
M4-S	Proofreading completed	Proofreading completed
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 Verify that there are no unmerged patches Release content finalized Creation and submission of marketing highlights Finalize version numbering for RM, RA1, RA2 Traceability matrix updated	Final documentation completed 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. Prepare release artifacts Tag the version of artifacts to be released releng job updated to use release branch instead of master PTLs collect all artifact references and communicates them to LF staff LF staff moves artifacts to hosting location and provides URLs to the PTL-s and the TSC PTL-s verify URLs PTL provides confirmed URL list to LF staff and the TSC for publication on the website PTL-s verify that there are no unmerged patches or PR-s. In case of any unmerged patches or PR-s notify the TSC. A volunteer TSC member or LF staff creates release branch for GitHub 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