| Practice Area | Checkpoint | Yes/No | Evidences | How to? |
|---|---|---|---|---|
| Architecture | Has the Project team reviewed the APIs with the Architecture Committee (ARC)? | Yes | ONAPARC-10 - Getting issue details... STATUS | 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 findings. | 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. | Yes | Holmes API Documentation - Beijing | ||
| Release Management | Are committed Sprint Backlog Stories been marked as "Done" in Jira board? | Yes | Getting issues... | Some of are long-term tasks. E.g. we are trying to parse the configuration data provided by DCAE. Due to the lack of the DCAE APIs, we have to try it out step by step. So some of the issues are still open. After the APIs are fully provided, I think they are going to be closed soon. |
| Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira? | Yes | Getting issues... | See above. PS. The backlog is changing dynamically because new tasks keeping coming, which makes it hard to make all of them "Done". Correct me if I understand this item incorrectly. | |
| Have all findings from previous milestones been addressed? | Yes | We are working on the Jenkins jobs, trying to set up the Sonar inspection job and CSIT workflow. Unknown errors occurred and we are still looking for help from the help desk of ONAP. | ||
| Development | Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | Yes | Still trying to set up the Sonar jobs. | Guidance on Code Coverage and Static Code Analysis |
| Is there any pending commit request older than 36 Business hours in Gerrit? | No | |||
| Are all the Jenkins jobs successfully passed ( Merge-Jobs)? | Yes | Holmes Jenkins Jobs | ||
| Are all binaries available in Nexus? | Yes | Holmes Binary List | ||
| Integration and Testing | Have 50 % of System Integration Testing Use Cases been implemented successfully in Jenkins? | Yes | Jenkins Link | |
| Has the project code successfully passed the Daily Build process? | Yes | Except for the Sonar jobs. (The errors are not caused by the code but by the building evironement.) | Goal is to ensure the latest project commit has not broken the Integration Daily Build |
Overview
Content Tools