|Practice Area||Checkpoint||Yes/No||Evidences||How to?|
|Architecture||Has the Project team reviewed the APIs with the Architecture Committee (ARC)?||Yes|
20180313:1000 EDT (GMT-5)
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|
code coverage for python work
moving epics over to Cassablanca
|The plan could be as simple as a Jira issue to track the implementation of findings or a documented plan within the wiki.|
|Does the team clearly understand that no changes in the API definition is allowed without formal TSC review and approval?||Yes||N/A||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?
|No||Critical point to understand is that change is inevitable, and that right timing and clear communication to the community will ease the process of accepting changes.|
|Provide link to the API Documentation.||N/A||What's New - ONAP Application Logging Guidelines|
|Release Management||Are committed Sprint Backlog Stories been marked as "Done" in Jira board?||No|
|Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira?||Yes||moved over remaining work to Cassablanca|
|Have all findings from previous milestones been addressed?||Ongoing|
|Development||Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar)||No|
Goal: 50% for Incubation project in Beijing
Python code just came in 20180312
|Guidance on Code Coverage and Static Code Analysis|
|Is there any pending commit request older than 36 Business hours in Gerrit?||No|
API work is being put in in phases and is under review
Do you have a plan to address by M4 the Critical vulnerabilities in the third party libraries used within your project?
|N/A||No functioning API yet||Ensure by M4 the Nexus-IQ report from “Jenkins CLM” shows 0 critical security vulnerability. Open the Nexus-IQ report for the details on each repo.|
|Are all the Jenkins jobs successfully passed ( Merge-Jobs)?||Yes|
Compile - yes
Merge - not required yet (do RI docker yet)
|Are all binaries available in Nexus?||Stretch goal for R2||Same ELK stack unchanged from amsterdam release|
|Integration and Testing|
Have 50 % of System Integration Testing Use Cases been implemented successfully in Jenkins?
|N/A||Test code not yet up|
|Has the project code successfully passed the Daily Build process?||Yes|
Jenkins compile builds pass as we commit pieces of the API
|Goal is to ensure the latest project commit has not broken the Integration Daily Build|