| Practice Area | Checkpoint | Yes/No | Evidences | How to? |
|---|---|---|---|---|
| Architecture | Has the Project team reviewed the APIs with the Architecture Committee (ARC)? | Yes | 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? | N/A | 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? | Yes | MSB Client SDK is provided. | 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 | Microservice Bus API Documentation | ||
| Release Management | Are committed Sprint Backlog Stories been marked as "Done" in Jira board? | Yes |
| |
| Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira? | Yes | |||
| Have all findings from previous milestones been addressed? | Yes |
| ||
| Development | Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | Yes | Now MSB has nearly 70% coverage, but there is an issue with the connection between Jenkins and sonar so the coverage data is not updated in sonar.
I raised an issue to LF: https://rt.linuxfoundation.org/SelfService/Display.html?id=45586 | 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 | https://jenkins.onap.org/view/msb/ | All the merger jobs successfully passed. Java site jobs failed due to wrong deployment site configruation. It has been fixed and will succeed next time. | |
| Are all binaries available in Nexus? | Yes | https://nexus.onap.org/#nexus-search;quick~org.onap.msb | ||
| Integration and Testing | Have 50 % of System Integration Testing Use Cases been implemented successfully in Jenkins? | Yes | https://jenkins.onap.org/view/CSIT/ | |
| 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 |
Overview
Content Tools