API Freeze | M3 | The goal of the API Freeze is to ensure API and Data Model are Frozen. At API Freeze, API stubs must be in implemented. All provisional APIs are at least functional if not yet fully tested. At API Freeze, the following activities have been achieved:
All externally accessible APIs & data models may not be modified. An API exception process will allow for critical changes to APIs after API Freeze. 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 Functional Test Cases are automated (Project Team). Issues brought to TSC or Architecture Coordinator.
| Prior to API review, Project teams must also review APIs Architecture Sub-committee.
To pass API Freeze, the PTL must:
Fill out in project space the Deliverables for API Freeze Milestone Checklist Template template Inform ONAP TSC and Release Manager (through the ONAP TSC mailing list) prior to the milestone on the availability of the deliverable
|