Casablanca Release

This release calendar below has been presented during ONAP Break out session at ONS Los Angeles Developers on March 26, 2018.

Casablanca Release Planning

Link to PDF

Casablanca Release Calendar

Review	Milestone	Date	Events
Kick-Off (Open Intent To Participate)	M0	May 25, 2018	Opening of Release Planning For existing Projects: Every existing Beijing projects that plan to be part of Casablanca Release must email TSC to notify their intention through the ONAP TSC mailing list For New Projects: New Candidate project must fill out “Project Proposal Template” Post the proposal in the wiki at Proposed Projects Inform ONAP TSC of their intention throught the ONAP TSC mailing list
Project Submission Closure		June 07, 2018	Last Date to announce Intention to Participate
Project Proposal Approved		June 14, 2018	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		June 21, 2018	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	June 28, 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: Fill out the Release Planning Template Fill out the Deliverables for Planning Milestone Checklist Template Post these 2 project deliverables in wiki.
Functionality freeze	M2	July 26, 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	August 23, 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	Sept 20, 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	Oct 11, 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: supporting integration testing closing high priority defects supporting Documentation team
	RC1	Oct 25, 2018	Release Candidate 1
	RC2	Nov 08, 2018	Release Candidate 2
Sign-Off	Release Delivery	Nov 15, 2018	Casablanca Release Sign-Off

Beijing Release

This release calendar below has been approved by TSC at Santa Clara Developers F2F on Dec 13, 2017.

Beijing Release Planning

Link to ONAP Beijing Release Planning (PDF) as presented at Paris F2F, Sept 2017

Update ONAP Beijing Release Planning (PDF) as presented at Santa Clara F2F, Dec 2017

Beijng Release Calendar

Review	Milestone	Date	Events
Kick-Off (Open Intent To Participate)	M0	November 16, 2017	Opening of Release Planning For existing Projects: Every existing Amsterdam projects that plan to be part of Beijing Release must email TSC to notify their intention through the ONAP TSC mailing list For New Projects: New Candidate project must fill out “Project Proposal Template” Post the proposal in the wiki at Proposed Projects Inform ONAP TSC of their intention throught the ONAP TSC mailing list
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: Fill out the Release Planning Template Fill out the Deliverables for Planning Milestone Checklist Template Post these 2 project deliverables in wiki.
Functionality freeze	M2	Feb 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 Freeze	M3	March 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 Freeze	M4	March 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).
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: supporting integration testing closing high priority defects supporting Documentation team
	RC1	May 3, 2018	Release 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-Off	Release Delivery	~~May 24, 2018~~ June 7, 2018	Beijing Release Sign-Off TSC decision to postpone RC2 review by 2 weeks (Topic 3, section am)

Amsterdam Release

Amsterdam Release Planning

Amsterdam Release Calendar

Link to ONAP Amsterdam Release planning (PDF).

Amsterdam 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: use the Project Proposal Template post the proposal in the wiki at Proposed Projects inform ONAP TSC of their intention throught the ONAP TSC mailing list.
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: Fill out the Release Planning Template Fill out the Deliverables for Planning Milestone Checklist Template Post these 2 project deliverables in wiki.
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: supporting integration testing closing high priority defects supporting Documentation team
	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

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

ONAP API Dependencies

ONAP Release Lifecycle

Release Lifecycle. It provides a description of each of the above milestones and the activities to be implemented.