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 | ||
|---|---|---|
| ||
|
| 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? | 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? |
| Yes |
| "Policy-based enhancements to capacity checks" proposed in M1, has been reduced in scope to implement only the Intent API (and exclude the intent-cost evaluation) - Edge Scoping MVP for Casablanca - ONAP Enhancements#ONAPEnhancements-ONAPEnhancements-Cloud-agnosticPlacement/Networking&HomingPolicies(Phase1-CasablancaMVP,Phase2-StretchGoal) | |||
| Provide link to the API Documentation. | https://onap.readthedocs.io/en/latest/submodules/optf/has.git/docs/sections/offeredapis.html https://onap.readthedocs.io/en/latest/submodules/optf/osdf.git/docs/sections/offeredapis.html | ||
| 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? | NA | Provide link to JIRA findings | |||||||||||
| Development | Is there any pending commit request older than 36 Business hours in Gerrit? | No | |||||||||||
| Do you have a plan to address by M4 the Critical and High vulnerabilities in the third party libraries used within your project? | NA | There are not identified security vulnerability for all repos | Ensure by M4 the Nexus-IQ report from “Jenkins CLM” shows 0 critical security vulnerability. Open the Nexus-IQ report for the details on each repo. | ||||||||||
Are all the Jenkins jobs successfully passed ( Merge-Jobs)? |
| Yes | https://jenkins.onap.org/view/optf/ | |
| Are all binaries available in Nexus? |
| Yes | OSDF: https://nexus.onap.org/content/repositories/snapshots/org/onap/optf/osdf/optf-osdf/1.2.0-SNAPSHOT/ | |
| Integration and Testing | Have 50 % of System Integration Testing Use Cases been implemented successfully in Jenkins? |
| Yes* | There are 35 functional test cases for the existing repo. (https://jenkins.onap.org/view/CSIT/) Tests for the new repo (CMSO) are being added by the team. | ||
| Has the project code successfully passed the Daily Build process? | Yes | https://jenkins.onap.org/view/optf/job/optf-has-master-verify-java/ https://jenkins.onap.org/view/optf/job/optf-osdf-master-osdf-verify-java/ | Goal is to ensure the latest project commit has not broken the Integration Daily Build |