Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

CNTT Elbrus release planning (for reference)


Proposed milestones

Note:  this table is ONLY intended to identify criteria for the milestones (i.e., a checklist to determine whether the milestone has been reached).  It does not speak to how these items will be done, or when they will be initiated.  Those will be determined separately.

Updated content via PRs, matching to issues createdCompletion of editing and proof reading of new/updated content via PRs
MilestoneDescriptionSoftware CriteriaSpecification Criteria (adapted from Elbrus release)DeltaNotes
M0Start of releaseNoneNone

M1Release planningDefinition
  • Determine version alignment with major upstream component (e.g., OpenStack, Kubernetes)
    • RM & RA versions selected 
    • Prioritized features selected for implementation from specifications
    • RC & RI effort scoped with owners identified
  • Project release plans submitted
  • High level scope createdCreated:  list of Github issues with the initial content or the content proposal
  • Release schedule approval requested
M0+4w

Pankaj Goyal:

Suggested changes



Release schedule approved
M2Contents Scope Freeze
  • Software development review of PRs completed
  • Initial RC(s) ready for RI implementation
  • Jira issues assigned to release
  •  High Level Issues created as per scope
  • Start creating content
  • (including review and feedback by software team)
M0+14w
M3

Code: RC Validation Testing

Spec: Content Freeze

  • RC validation testing completed
  • High priority Jira issues resolved
  • Preliminary documentation completed
  • Content created matching issues
  • Issues continue to be created
M0 + 18w
M4

Code: RI Validation Testing

Spec: Proofreading

  • RI validation testing completed
  • High priority Jira issues resolved
  • Proofreading: Validate content and make corrections
  • No new content after this point for this release
M0+22w
M5Release 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
  • Release content finalized
  • Creation and submission of marketing highlights
  • Finalize version numbering for RM, RA1, RA2
M0+25w

Marketing highlights page completed

M6Release
  • Release artifacts available for distribution 
  • Standalone project self-release completed
  • Release packaged (branched  in GitHub), specification documents presented in the ReadTheDocs format
M0+26w

...