...
Practice Area | Checkpoint | Yes/No | Evidences | How to? | |||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Architecture | Has the Project team reviewed the APIs with the Architecture Committee (ARC)? | Yes | Review 8/22 | 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? | Link to plan | Yes |
| Need to finalize the VF-C schema changes, if any. Need to finalize attributes needs for ESRThe 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? | If Yes, please a link to the evidence of these changes. | Yes |
| Moved AAF integration into Beijing release. We have made babel, gizmo, and champ Beijing incubationCritical 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. | A&AI REST API Documentation | ||||||||||||||||||||||||
Release Management | Are committed Sprint Backlog Stories been marked as "Done" in Jira board? | Yes | A&AI JIRA BoardProvide Link to Project backlog | ||||||||||||||||||||||
Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira? | Yes | ||||||||||||||||||||||||
Have all findings from previous milestones been addressed? | Yes | Provide link to JIRA findings | |||||||||||||||||||||||
Development | Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | Yes | Goal: 30-50% for Incubation project | 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)?Provide link to evidence | Yes, every job has passed at some point. | A&AI Jenkins | The one job that has never passed is being removed as part of this commit: https://gerrit.onap.org/r/#/c/14577/2 | ||||||||||||||||||||||
Are all binaries available in Nexus? | Yes | Nexus A&AIProvide link to evidence | |||||||||||||||||||||||
Integration and Testing | Have 50 % of System Integration Testing Use Cases been implemented successfully in Jenkins? | Yes | https://jenkins.onap.org/view/CSIT/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 |