DRAFT PROPOSAL FOR COMMENTS
ONAP Release 1 Release Planning Draft Proposal
Link to ONAP Release 1 planning PPT.
|Kick-Off (Open Intent To Participate)||M0||May 4, 2017||Planning process opens for all projects to submit their intent.|
|Project Submitted||May 15, 2017|
All projects candidate for the first ONAP Release have to:
|Project Approved||June 1, 2017||The TSC has a goal to review and provide its disposition on all submitted projects proposal.|
|Planning||M1||June 29, 2017|
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:
|Functionality freeze||M2||August 03, 2017|
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 Freeze||M3||August 24, 2017|
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 Freeze||M4||Sept 14, 2017|
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).
|Integration||RC0||Sept 28, 2017|
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:
|RC1||Oct 12, 2017||Release Candidate 1|
|RC2||Oct 26, 2017||Release Candidate 2|
|Sign-Off||Release Delivery||Nov 2, 2017||Target release date|
The source of information to generate this information are the data point gathered into the project Release Planning template.
The graph below represents API dependencies for M1 Release Planning projects.
- Release Lifecycle proposal draft. It provides a description of each of the above milestones and the activities to be implemented.
- Release Planning template
- Deliverables for Release Planning Milestone Template
- Deliverables for Functionality Freeze Milestone Checklist Template
- Deliverables for API Freeze Milestone Checklist Template
- Deliverables for Code Freeze Milestone Checklist Template
- Deliverables for Release Candidate Milestone Checklist Template
- Deliverables for Release Sign-Off Milestone Checklist Template