Anuket Project

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

CNTT Elbrus release planning (for reference)


Proposed milestones

MilestoneDescriptionSoftware CriteriaSpecification Criteria (adapted from Elbrus release)DeltaNotes
M0Start of releaseNoneNone

M1Release planning
  • 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 created
  • Created:  list of Github issues with the initial content or the content proposal
  • Release schedule approval requested
M0+4w

Release schedule approved
M2Contents Freeze
  • Initial RC(s) ready for RI implementation
  • Jira issues assigned to release
  • Updated content via PRs, matching to issues created 
M0+14w
M3RC Validation Testing
  • RC validation testing completed
  • High priority Jira issues resolved
  • Preliminary documentation completed
  • Completion of editing and proof reading of new/updated content via PRs
M0 + 18w
M4RI Validation Testing
  • RI validation testing completed
  • High priority Jira issues resolved

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
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

Schedule Proposal for June Release (compressed to 16 w)

MilestoneDateNotes
M0

 


M1

 


M2

 


M3

 


M4

 


M5

 


M6

 


Notes

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.
  • No labels