DRAFT PROPOSAL FOR COMMENTS
ONAP Release 1 Release Planning Draft Proposal
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, must use the Project Proposal Template, post the proposal in the wiki at Proposing A Project and inform ONAP TSC of their intention throught the ONAP TSC mailng list. | |
| Project Approved | June 1, 2017 | The TSC has a goal to review and provide its disposition for all submitted projects. | |
| 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. The Document and Training teams have defined their plans. The packaging and installation strategy is defined. |
| 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 functional Test Case. The vendor equipments have been delivered. A stable document describing the API is documented and available |
| API Freeze | M3 | August 24, 2017 | API/data model freeze. Any Changes to the API must be brought to the knowledge of the TSC for review and approval. 50% of 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 Test Case are automated. |
| Integration | RC0 | Sept 28, 2017 | Release candidate 0 |
| RC1 | Oct 12, 2017 | Release candidate 1 | |
| RC2 | Oct 26, 2017 | Release candidate 2 | |
| Sign-Off | Release Delivery | Nov 2, 2017 | Target release date |
Release Lifecycle
- Release Lifecycle proposal draft. It provides a description of each above milestone and the activities that to be conducted.