DRAFT.
| 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 | 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 | CLI commands | ||
| Release Management | Are committed Sprint Backlog Stories been marked as "Done" in Jira board? | YES | https://jira.onap.org/secure/RapidBoard.jspa?rapidView=21&view=planning.nodetail (Current sprint is continuing till March 29) | |
| Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira? | YES | https://jira.onap.org/secure/RapidBoard.jspa?rapidView=21&view=planning.nodetail (Current sprint is continuing till March 29) | ||
| Have all findings from previous milestones been addressed? | NO | | Jira Legacy | | |
| server | System Jira | |||
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 | key | CIMAN-23NA||
| Development | Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | YESGoal: 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? | NOYES | They are DRAFTs one. | ||
| Are all the Jenkins jobs successfully passed ( Merge-Jobs)? | YES | https://jenkins.onap.org/view/cli/ | ||
| Are all binaries available in Nexus? | YES | once CIMAN-23 issue is fixed, docker image also will be available. | ||
| Integration and Testing | Have 50 % of System Integration Testing Use Cases been implemented successfully in Jenkins? | YES | https://jenkins.onap.org/job/cli-master-verify-csit-sanity-check/2/ | |
| Has the project code successfully passed the Daily Build process? | YESrelated CI bug CIMAN-23 | Goal is to ensure the latest project commit has not broken the Integration Daily Build |