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.

Practice AreaCheckpointYes/NoEvidencesHow to?

Has the Project team reviewed the APIs with the Architecture Committee (ARC)?N/AVNFRQTS does not create APIs

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?N/AVNFRQTS does not create APIsThe 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?N/AVNFRQTS does not create APIsIn 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?


Clarification:PNF functionality starts to be introduced in Beijing release  for management functions only. Additional aspects expected in future releases.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.N/AVNFRQTS does not create APIs
Release ManagementAre committed Sprint Backlog Stories been marked as "Done" in Jira board?YESProvide 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

release planning project status:

M1 pass

M2 pass

DevelopmentHas the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar)N/AVNFRQTS does not generate codeGuidance on Code Coverage and Static Code Analysis

Tools: Sonar

Is there any pending commit request older than 36 Business hours in Gerrit?NO

gerrit open issues:

VNF Guidelines

VNF Requirements

Do you have a plan to address by M4 the Critical  vulnerabilities in the third party libraries used within your project?

N/AVNFRQTS does not generate codeEnsure 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

Gerrit Merged issues:

VNF Guidelines

VNF Requirements

Are all binaries available in Nexus?Yesonap.readthedocs.ioVNFRQTS produces documentation rather than code binaries. All documentation is published on rather than Nexus
Integration and Testing

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

N/AVNFRQTS does not generate code
Has the project code successfully passed the Daily Build process?N/ANFRQTS does not generate code for daily build. it does publish dpocumentation to onap.readthedocs.ioGoal is to ensure the latest project commit has not broken the Integration Daily Build