Versions Compared

Key

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

...

The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.

Team Internal Milestone

This section is optional and may be used to document internal milestones within a project team or multiple project teams. For instance, in the case the team has made agreement with other team to deliver some artifacts on a certain date that are not in the release milestone, it is erecommended to provide these agreements and dates in this section.

It is not expected to have a detailed project plan.

The following table shows the major project milestones and intermediate milestones for the Dublin release. 


MilestoneDescription DateComments
M1End of release planning
Formal commitment to release scope

  • M1 worksheets ready for review
Jan 15, 2019Release manager reviews worksheets to assess readiness for M1 milestone

  • TSC M1 approval vote
Jan 17, 2019


M2Functionality Freeze


  • Stable user stories baselined
Feb 8, 2019

  • M2 worksheets ready for review
Feb 12, 2019Release manager reviews worksheets to assess readiness for M2 milestone

  • TSC M2 approval vote
Feb 14, 2019


M3API Freeze


  • Final API definitions (swagger, Yang) due
March 1, 2019Last day to submit Dublin swagger / Yang changes to Gerrit

  • M3 worksheets ready for review
March 05, 2019Release manager reviews worksheets to assess readiness for M3 milestone

  • TSC M3 approval vote
March 07, 2019


M4Code Freeze


  • Code due for Dublin user stories
March 22, 2019Last day to submit Dublin code changes to Gerrit

  • M4 worksheets ready for review
March 26, 2019

Release manager reviews worksheets to assess readiness for M4 milestone, including the following checks:

  • All repos must have >= 50% code (line) coverage in Sonar
  • No failed Jenkins jobs
  • All CSIT tests pass
  • Healthchecks pass

  • TSC M4 approval vote
March 28, 2019


RC0Release Candidate 1


  • Code due for RC0 fixes
April 12, 2019Last date to submit code fixes for release candidate 0

  • RC0 release artifacts available
April 16, 2019

  • RC0 worksheets ready for review
April 16, 2019

  • TSC RC0 approval vote
April 18, 2019


RC1Release Candidate 1


  • Code due for RC1 fixes
April 26, 2019Last date to submit code fixes for release candidate 1

  • RC1 release artifacts available
April 30, 2019

  • RC1 worksheets ready for review
April 30, 2019

  • TSC RC1
May 2, 2019


RC2Release Candidate 2


  • Code due for final Dublin fixes
May 10, 2019Last date to submit code fixes for final Dublin release (RC2)

  • RC2 release artifacts available
May 14, 2019

  • RC2 worksheets ready for review
May 14, 2019

  • TSC RC2
May 16, 2019


Release Sign-OffFinal TSC Sign-OffMay 23, 2019Dublin Release Sign-Off
DateProjectDeliverable
To fill outTo fill outTo fill out

Documentation, Training

  • Highlight the team contributions to the specific document related to he project (Config guide, installation guide...).
  • Highlight the team contributions to the overall Release Documentation and training asset
  • High level list of documentation, training and tutorials necessary to understand the release capabilities, configuration and operation.
  • Documentation includes items such as:
    • Installation instructions
    • Configuration instructions
    • Developer guide
    • End User guide
    • Admin guide
    • ...

...