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. Rows in green are interim milestones the project team needs to meet in order to meet the overall release schedule.


MilestoneDescription DateComments
M1End of release planning
Formal commitment to release scope

  • M1 worksheets complete
Jan 15, 2019

  • TSC approval vote
Jan 17, 2019


M2Functionality Freeze


  • M2 worksheets complete
Feb 12, 2019

  • TSC Approval vote
Feb 14, 2019


M3API FreezeMarch 07, 2019

API/data model freeze. Mark the end of API and Data Model change. API and Data Model are now Frozen.

Any changes to the API must be brought to the knowledge of the TSC for review and approval.

50% of Functional Test Case are automated.

M4Code FreezeMarch 28, 2019

Code Freeze. Mark the end of the Features coding.

Jira issues are either fixed in the current release or assigned to next release.

100% of Functional Test Case are automated.

End 2 End Release Test Cases are implemented (Integration Team).

All new VNF Requirements planned for the release reviewed and  implemented in VNF Requirements project.

RC0IntegrationApril 18, 2019

Release Candidate 0

RCs are to ensure proper alignment and execution on End 2 End Release Test Cases and End 2 End functional Test Cases.

Project Team focused its effort on:

  1. supporting integration testing (complete Health Check and Pair Wise Testing)
  2. closing high priority defects
  3. supporting Documentation team
RC1
May 02, 2019Release Candidate 1

Marketing: Outline for written content agreed with LF marketing May 09, 2019

Marketing: Near-final draft for written content May 16, 2019
RC2
May 16, 2019Release Candidate 2

Marketing: Content freeze May 23, 2019

Marketing: New video contentMay 23, 2019
Release Sign-OffSign-OffMay 23, 2019Dublin Release Sign-Off

Marketing: Public announcement May 30, 2019 TBD


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

...