AAI M3 Deliverables for API Freeze Milestone Checklist
The following items are expected to be completed for the project to Pass the M3 API Freeze Milestone.
M3 Release Architecture Milestone overview is available in wiki.
Practice Area | Checkpoint | Yes/No | Evidences | How to? |
|---|---|---|---|---|
Architecture
| Has the Project team reviewed the APIs with the Architecture Committee (ARC)? | Yes | Review 8/22 | Architecture walkthrough to understand how each project contributes on Release Use Case. ARC to organize the walkthrough. |
Is there a plan to address the findings the API review? | Yes | Need to finalize the VF-C schema changes, if any. Need to finalize attributes needs for ESR. | ||
Does the team clearly understand that no changes in the API definition is allowed without formal TSC review and approval? | Yes | NA | In the case some changes are necessary, bring the request to the TSC for review and approval. | |
Is there any changes in the scope, functionalities, deliverable, dependency, resources, API, repositories since M1 milestone? | Yes | Moved AAF integration into Beijing release. We have made babel, gizmo, and champ Beijing incubation | ||
Provide link to the API Documentation. |
|
| ||
Release Management | Are committed Sprint Backlog Stories been marked as "Done" in Jira board? | Yes |
| |
Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira? | Yes |
|
| |
Have all findings from previous milestones been addressed? | Yes | Provide link to JIRA findings |
| |
Development | Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | Yes
| Goal: 30-50% for Incubation project | |
Is there any pending commit request older than 36 Business hours in Gerrit? | No |
|
| |
Are all the Jenkins jobs successfully passed ( Merge-Jobs)? | Yes, every job has passed at some point. | The one job that has never passed is being removed as part of this commit: https://gerrit.onap.org/r/#/c/14577/2 | ||
Are all binaries available in Nexus? | Yes |
| ||
Integration and Testing | Have 50 % of System Integration Testing Use Cases been implemented successfully in Jenkins? | Yes |
| |
Has the project code successfully passed the Daily Build process? | Yes |
| Goal is to ensure the latest project commit has not broken the Integration Daily Build |