AAF R1 Amsterdam Release - M3 API Freeze Milestone Checklist
- Varun Gudisena
- Sai Gandham
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.
Usage
Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki.
Fill out the Yes/No column
Provide link to evidence (when necessary)
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? | NA | No issues were found. | 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 | |||
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? | Sonar for 2 components are pending. One functional test case has to be automated in Jenkins | 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 | https://sonar.onap.org/overview?id=46017 inno - 43.1% https://sonar.onap.org/overview?id=54083 Authz - 32.6% https://sonar.onap.org/overview?id=45529 Cadi - 32.2% | |
Is there any pending commit request older than 36 Business hours in Gerrit? | No | |||
Are all the Jenkins jobs successfully passed ( Merge-Jobs)? | Done | https://jenkins.onap.org/view/aaf/job/aaf-authz-master-merge-java/ https://jenkins.onap.org/view/aaf/job/aaf-cadi-master-merge-java/ https://jenkins.onap.org/view/aaf/job/aaf-inno-master-merge-java/ | ||
Are all binaries available in Nexus? | Yes | https://nexus.onap.org/index.html#view-repositories;snapshots~browsestorage~/org/onap/aaf | ||
Integration and Testing | Have 50 % of System Integration Testing Use Cases been implemented successfully in Jenkins? | Yes | Completed 100% functional test cases https://jenkins.onap.org/view/aaf/job/aaf-master-csit-aafapi/ | |
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 |