Beijing Release
This release calendar proposal has been presented to the Community at the Developers F2F in Paris on Sept 27, and have been updated to incorporate the feedback received.
ONAP Beijing Release Planning
Link to ONAP Beijing Release Planning (PDF)
Release Calendar
Review | Milestone | Date | Events |
---|---|---|---|
Kick-Off (Open Intent To Participate) | M0 | November 16, 2017 | Opening of Release Planning
|
Project Submission Closure | November 30, 2017 | Last Date to announce Intention to Participate | |
Project Proposal Approved | December 13, 2017 | The 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. | |
Planning | M1 | Jan 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:
|
Functionality freeze | M2 | Feb 15, 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 Freeze | M3 | March 1, 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 Freeze | M4 | Avril 5, 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). |
Integration | RC0 | Avril 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:
|
RC1 | May 3, 2018 | Release Candidate 1 | |
RC2 | May 17, 2018 | Release Candidate 2 | |
Sign-Off | Release Delivery | May 24, 2018 | Beijing Release Sign-Off |
Amsterdam Release
ONAP Amsterdam Release Planning
Link to ONAP Amsterdam Release planning (PDF).
Release Calendar
Review | Milestone | Date | Events |
---|---|---|---|
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 28, 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 | Oct 12, 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 26, 2017 | Release Candidate 1 | |
RC2 | Nov 9, 2017 | Release Candidate 2 | |
Sign-Off | Release Delivery | Nov 16, 2017 | Amsterdam Release Sign-Off |
Release Dependencies
API Dependencies
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.
More info on how to generate the graph are available.
Release Lifecycle
- Release Lifecycle. It provides a description of each of the above milestones and the activities to be implemented.