...
Info | ||
---|---|---|
| ||
|
Practice Area | Checkpoint | Yes/No | Evidences | How to? |
---|---|---|---|---|
Architecture | Has the Project team reviewed the APIs with the Architecture Committee (ARC)? | yes | 2/27 Call | 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? | NA | no changes requested by ARC | 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 | 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? | no | If Yes, please a link to the evidence of these changes. | 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. | on readthedocs | http://onap.readthedocs.io/en/amsterdam/submodules/vnfsdk/model.git/docs/files/vnfsdk-apis.html | ||
Release Management | Are committed Sprint Backlog Stories been marked as "Done" in Jira board? | yes | https://jira.onap.org/secure/RapidBoard.jspa?rapidView=115&view=detail | |
Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira? | yes | https://jira.onap.org/secure/RapidBoard.jspa?rapidView=115&view=detail | ||
Have all findings from previous milestones been addressed? | NA | no previous findings | ||
Development | Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | In some repos. Some are still in progress | Goal: 50% for Incubation project in Beijing | 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+vnfsdk | ||
Do you have a plan to address by M4 the Critical vulnerabilities in the third party libraries used within your project? | yes | Upgrading out-of-date components and addressing other issues | 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)? | Provide link to evidence pending commits | |||
Are all binaries available in Nexus? | https://nexus.onap.org/content/repositories/public/org/onap/vnfsdk/ pending commits | |||
Integration and Testing | Have 50 % of System Integration Testing Use Cases been implemented successfully in Jenkins? | https://jenkins.onap.org/view/vnfsdk/ pending commits | ||
Has the project code successfully passed the Daily Build process? | NA | deferred until daily builds start again at M4 | Goal is to ensure the latest project commit has not broken the Integration Daily Build |