M3 Release Architecture Milestone overview is available in wiki.
| Practice Area | Checkpoint | Yes/No | Evidences | How to? | |||
|---|---|---|---|---|---|---|---|
| Architecture | Has the Project team reviewed the APIs with the Architecture Committee (ARC)? | yes | ONAP Services List#PortalPlatform | 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? | no | Link to plan | 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 | ONAP Services List#PortalPlatform | |||||
| Release Management | Are committed Sprint Backlog Stories been marked as "Done" in Jira board? | Provide Link to Project backlogYes | https://jira.onap.org/secure/RapidBoard.jspa?rapidView=33&projectKey=PORTAL&view=planning.nodetail | ||||
| Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira? | Yes | https://jira.onap.org/secure/RapidBoard.jspa?rapidView=33&projectKey=PORTAL&view=planning.nodetail | |||||
| Have all findings from previous milestones been addressed? | Provide link to JIRA findingsYes | https://jira.onap.org/secure/RapidBoard.jspa?rapidView=33&projectKey=PORTAL&view=planning.nodetail | |||||
| 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 | https://jenkins.onap.org/view/portal/ | |||||
| Are all binaries available in Nexus?Provide link to evidence | Yes | https://nexus.onap.org/#nexus-search;quick~portal/sdk | |||||
| Integration and Testing | Have 50 % of System Integration Testing Use Cases been implemented successfully in Jenkins? | Provide link to evidence | Have you reviewed all the Test Case with Integration Team? | Schedule a meeting with Integration Team to review the deliverable. | Yes | CSIT tests - https://gerrit.onap.org/r/#/c/11451/ 2 Jenkins jobs - https://jenkins.onap.org/view/CSIT/job/portal-master-csit-testsuite/ https://jenkins.onap.org/view/CSIT/job/portal-master-verify-csit-testsuite/ Tests executed on Rackspace: | |
| Has the project code successfully passed the Daily Build process? | Yes | https://jenkins.onap.org/view/portal/ | Goal is to ensure the latest project commit has not broken the Integration Daily Build |
