Release Process Milestone Planning

Proposed milestones

Milestone	Description	Software Tasks / Criteria	Specification Tasks / Criteria (adapted from Elbrus release)	Delta
M0	Start of release	None	None
M1	Release planning	RM & RA versions selected Features selected for implementation from specifications RC & RI effort scoped with owners identified Major upstream component versions determined Project release plans submitted Release schedule approved	Create the high level scope Create initial list of Github issues, starting with issues that match the scope (originally M2 for Elbrus) Release schedule approved	M0+4w
M2	Contents Freeze	Initial RC(s) ready for RI implementation Jira issues assigned to release	Update content via PRs, matching to issues created	M0+14w
M3	RC Validation Testing	RC validation testing completed High priority Jira issues resolved Preliminary documentation completed	Find typo's, correct with PRs	M0 + 18w
M4	RI Validation Testing	RI validation testing completed High priority Jira issues resolved		M0+22w
M5	Release Readiness	Final documentation completed RI cookbook completed Manifest completed Remaining Jira issues assigned to the release closed or pushed to next release Release artifacts prepared Standalone project testing completed Marketing highlights page completed	Select release content (originally M4 for Elbrus)	M0+25w
M6	Release	Release artifacts available for distribution Standalone project self-release completed	Package the release, setup tag at ReadTheDocs	M0+26w

Attendees: David, Al, Jim, Trevor

Plan for set of milestones for software development, since we have agreed that specifications and software will use different cadences.