Policy R3 Casablanca M3 Deliverables for API Freeze Milestone Checklist Template
- Pamela Dragosh
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 Aug 7, 2018 | 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 | @Chris Donley to follow up with Pam on Interfaces consumed in the Architecture document. | ||
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? | Yes | CCVPN did not meet with Policy team for Closed Loop requirements prior to M1. 5G OOF PCI Optimization is also requiring support post-M1 timeframe. Resources for doing Logging v1.2 specification went away. | 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. | ||||
Release Management | Are committed Sprint Backlog Stories been marked as "Done" in Jira board? | Yes | https://jira.onap.org/secure/RapidBoard.jspa?rapidView=15&view=planning.nodetail | |
Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira? | Yes | |||
Have all findings from previous milestones been addressed? | Yes | No findings from previous milestones | ||
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 | |
Is there any pending commit request older than 36 Business hours in Gerrit? | No | |||
Do you have a plan to address by M4 the Critical vulnerabilities in the third party libraries used within your project? | Yes | Policy R3 Casablanca Security/Vulnerability Threat Template POLICY-1059: Address the security issues with Severe (and above) Level 4-6Closed | 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 | These are the MVP projects for Casablanca: https://jenkins.onap.org/view/policy/job/policy-common-master-merge-java/ https://jenkins.onap.org/view/policy/job/policy-drools-pdp-master-merge-scm-mvn-script/ https://jenkins.onap.org/view/policy/job/policy-drools-applications-master-merge-java/ https://jenkins.onap.org/view/policy/job/policy-engine-master-merge-scm-mvn-script/ https://jenkins.onap.org/view/policy/job/policy-distribution-master-merge-java/ | ||
Are all binaries available in Nexus? | Yes | https://nexus.onap.org/content/repositories/snapshots/org/onap/policy/ | ||
Integration and Testing | Have 50 % of System Integration Testing Use Cases been implemented successfully in Jenkins? | Yes | Our CSIT Tests are described here: Policy R3 Casablanca CSIT Functional Test Cases Our CSIT CI/CD Jobs: https://jenkins.onap.org/view/policy/job/policy-master-csit-health/ | |
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 |