Versions Compared

Key

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

...

Review MilestoneDateEvents
Kick-Off (Open Intent To Participate)M0November 16, 2017

Opening of Release Planning

Project Submission Closure
November 30, 2017

Last Date to announce Intention to Participate

Project Proposal Approved
December 13, 2017The TSC has a goal to review and provide its disposition on all submitted projects proposal.

This is the last date for TSC to formally approved New Project Proposal

Project Planning Closure
Jan 8, 2017

Project Planning submission, by this date all projects have submitted in wiki their Release Planning materials.

That will give everyone to time to understand project scope and dependencies.

PlanningM1Jan 18, 2018

Planning process complete, all Project Deliverables are defined (including functional architecture, scope, dependencies,...)

Integration Team has defined the vendor Equipments list and the End 2 End Release Test Cases are fully defined.

The Document and Training teams have defined their plans. The packaging and installation strategy is defined.

To pass the M1 milestones, all approved projects have to:

  1. Fill out the Release Planning Template
  2. Fill out the Deliverables for Planning Milestone Checklist Template
  3. Post these 2 project deliverables in wiki.
Functionality freezeM2Feb 12, 2018

Functionality freeze, no new visible functionality is to be added to the current ONAP release.

Each Project team has defined and documented their Functional Test Cases.

The vendor equipments have been delivered.

A stable document describing the API is documented and available in wiki.

API FreezeM3March 8, 2018

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.

Code FreezeM4March 29, 2018

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

IntegrationRC0Avril 19, 2018

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

RC1May 3, 2018Release Candidate 1

RC2

May 17, 2018

May 31, 2018

Release Candidate 2

TSC decision to postpone RC2 review by 2 weeks (Topic 3, section am)

Sign-OffRelease Delivery

May 24, 2018

June 7, 2018

Beijing Release Sign-Off

TSC decision to postpone RC2 review by 2 weeks (Topic 3, section am)

...