| API | M3 | - The goal of the API Freeze is to ensure architecture alignment with all projects participating to an ONAP release.At API Freeze, API and Data Model are Frozen.
- Architecture should be carefully documented and stable (API, block diagram, flow diagram,... defined).
- All externally accessible APIs & data models may not be modified. An API exception process will allow for critical changes to APIs after API Freeze with the consent of the consuming projects. Any Changes to the API must be brought to the knowledge of the TSC for review and approval. APIs include, but are not limited to, all Java classes/interfaces declared public, all YANG models, all TOSCA profiles, all config file YANG schemas, and all REST/RESTCONF calls including the full URL with options.
- 50% of CSIT Test case complete(Project Team)
- Issues brought to TSC or Architecture Committee (ARC).
Note: Projects in Incubation State would have a lower threshold than projects in Mature/Core State.
Project in Core State would have a high threshold. | Prior to Architecture review, Project teams must also review APIs with the Architecture Committee (ARC).
To pass Architecture review, the PTL must:
- Fill out in project space the Deliverables for Architecture Milestone template
- Inform the TSC Chair and the Release Manager prior to the milestone on the availability of the deliverable
It is important to understand that activities started at Functionality Freeze are still ongoing until Code Freeze milestone. |
