...
Draft Dublin Release milestone as proposed at TSC meeting on Oct 25, 2018
Dublin Release Calendar
| Review | Milestone | Date | Events |
|---|---|---|---|
| Kick-Off (Open Intent To Participate) | M0 | Nov 15, 2018 | Opening of Release Planning
|
| Project Submission Closure | Nov 30, 2018 | Last Date to announce Intention to Participate | |
| Project Proposal Approved | Dec 13, 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 | Jan 10, 2019 | 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 17, 2019 | 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 14, 2019 | 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 14, 2019 | 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 | April 11, 2019 | 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 | May 2, 2019 | 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 16, 2019 | Release Candidate 1 | |
| Marketing: Outline for written content agreed with LF marketing | May 23, 2019 | ||
| Marketing: Near-final draft for written content | May 30, 2019 | ||
| RC2 | May 30, 2019 | Release Candidate 2 | |
| Marketing: Content freeze | June 06, 2019 | ||
| Marketing: New video content | June 06, 2019 | ||
| Sign-Off | Release Delivery | June 06, 2019 | Dublin Release Sign-Off |
| Marketing: Public announcement | June 14, 2019 TBD |
Casablanca Release
This release calendar below has been presented during ONAP Break out session at ONS Los Angeles Developers on March 26, 2018.
...
| Review | Milestone | Date | Events |
|---|---|---|---|
| Kick-Off (Open Intent To Participate) | M0 | May 25, 2018 | Opening of Release Planning
|
| 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:
|
| 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:
|
| RC1 | Oct 25, 2018 | Release Candidate 1 | |
| Marketing: Outline for written content agreed with LF marketing | Nov 1, 2018 | ||
| Marketing: Near-final draft for written content | Nov 8, 2018 | ||
| RC2 |
Nov 27, 2018 | Release Candidate 2 TSC decision on Nov 8 to postpone RC2 to Nov 27. | |
| Marketing: Content freeze | |||
| Marketing: New video content | |||
| Sign-Off | Release Delivery |
Nov 30, 2018 | Casablanca Release Sign-Off TSC decision on Nov 8 to postpone Sign-Off to Nov 30. |
| Marketing: Public announcement |
Beijing Release
This release calendar below has been approved by TSC at Santa Clara Developers F2F on Dec 13, 2017.
...