...
| Practice Area | Checkpoint | Yes/No | Evidences | How to? | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Architecture | Has the Project team reviewed the APIs with the Architecture Committee (ARC)? | Yes | 20180814 | 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 | Adjust Logging Casablanca Scope | 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 | 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 | If Yes, please a link to the evidence of these changes. see spec page started in beijing | 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. | ONAP Application Logging Specification v1.2 (Casablanca) | ||||||||||
| Release Management | Are committed Sprint Backlog Stories been marked as "Done" in Jira board? | Yes | https://jira.onap.org/secure/RapidBoard.jspa?rapidView=143&view=planning.nodetail&epics=visible | query project = LOG AND status in (Open, "In Progress", REOPENED) AND (labels not in ("POMBA") or labels is EMPTY) | |||||||
| Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira? | Yes | https://jira.onap.org/secure/RapidBoard.jspa?rapidView=143&view=planning.nodetail&epics=visible | |||||||||
| Have all findings from previous milestones been addressed? | Yes | Provide link to JIRA findings and addressed logging resource issues in Casablanca Risks | |||||||||
| Development | Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | Yes | Goal: 50% for Incubation project in Beijing we have 88.8 https://sonar.onap.org/dashboard?id=org.onap.logging-analytics%3Alogging-analytics | Guidance on Code Coverage and Static Code Analysis | |||||||
| Is there any pending commit request older than 36 Business hours in Gerrit? | No | https://gerrit.onap.org/r/#/q/status:open+project:+logging-analytics | |||||||||
Do you have a plan to address by M4 the Critical vulnerabilities in the third party libraries used within your project? | Yes |
| 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. There are license issues with the IQ server as of 20180820: https://lists.onap.org/g/onap-discuss/topic/clm_cve_links_from_jenkins/24819369?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,24819369 | ||||||||
| Are all the Jenkins jobs successfully passed ( Merge-Jobs)? | Yes | first 5 jobs are for logging | |||||||||
| Are all binaries available in Nexus? | yes | link 2 libraries in nexus.onap.org details in Logging Developer Guide#pom.xml | |||||||||
| Integration and Testing | Have 50 % of System Integration Testing Use Cases been implemented successfully in Jenkins? | N/A | Provide link to evidence | ||||||||
| 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 |