Skip to end of metadata
Go to start of metadata

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

  1. Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki.
  2. Fill out the Yes/No column
  3. Provide link to evidence (when necessary)
Practice AreaCheckpointYes/NoEvidencesHow to?
Architecture


Has the Project team reviewed the APIs with the Architecture Committee (ARC)?Yeshttps://jira.onap.org/browse/ONAPARC-93


Is there a plan to address the findings the API review?NA
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?YesNAIn 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


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.YesSO API (Existing APIs)
New API Specifications (SO - OOF APIs)

Release ManagementAre 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

DevelopmentHas the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar)No

Goal: 50% for Incubation project in Beijing

Work in progress

Guidance on Code Coverage and Static Code Analysis

Tools: Sonar

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  vulnerabilities in the third party libraries used within your project?

Yes

SO-457 - Getting issue details... STATUS

SO-458 - Getting issue details... STATUS


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

Ticket raised to LF to release the latest build components for making clm jobs ok.


Are all binaries available in Nexus?Yes

https://nexus.onap.org/content/groups/staging/org/onap/so/



Integration and Testing

Have 50 % of System Integration Testing Use Cases been implemented successfully in Jenkins?

Yes

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 

Risk: 

Risk as identified at M1 and M2 has materialized.

ATT code is not merged yet. This may impact code quality (static code checks, security vulnerabilities and Licensing) and code coverage.

Code merge may impact other current development. Code Merge is currently planned by March 14.