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.
| Info |
|---|
|
- 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| Review is scheduled for Tuesday Aug - 22nd. |
| 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? |
yes | no findings | TBD. Review is scheduled for Tuesday Aug - 22nd. | 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 |
I\SDC has new repositories for the DCAE-D and ONAP-UI.this is our stretch goal to deliver them in Beijing| 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 | | 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. | SDC API |
|
|
| Release Management | Are committed Sprint Backlog Stories been marked as "Done" in Jira board? | Yes | Provide 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| Under invistigation | Provide link to JIRA findings |
|
| Development | Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | No | Goal: 30-50% for Incubation project |
work in progresshttps://jenkins.onap.org/view/sdc-sdc-workflow/https://jenkins.onap.org/view/sdc/job/sdc-master-sdc-merge-java/
https://jenkins.onap.org/view/sdc-jtosca/
https://jenkins.onap.org/view/sdc-sdc-distribution/
https://jenkins.onap.org/view/sdc-sdc-titan/
https://jenkins.onap.org/view/sdc-sdc-tosca/
| Provide link to evidence |
|
| Are all binaries available in Nexus? | Yes | Provide link to evidence |
|
Integration and Testing
| Have 50 % of System Integration Testing Use Cases been implemented successfully in Jenkins? |
N/A| No | Provide link to evidence |
|
| Has the project code successfully passed the Daily Build process? |
Yes