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)?yes2/27 Call

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?NAno changes requested by ARCThe 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?

noIf 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.on readthedocshttp://onap.readthedocs.io/en/amsterdam/submodules/vnfsdk/model.git/docs/files/vnfsdk-apis.html
Release ManagementAre committed Sprint Backlog Stories been marked as "Done" in Jira board?yeshttps://jira.onap.org/secure/RapidBoard.jspa?rapidView=115&view=detail
Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira?yeshttps://jira.onap.org/secure/RapidBoard.jspa?rapidView=115&view=detail
Have all findings from previous milestones been addressed?NAno previous findings
DevelopmentHas the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar)In some repos.  Some are still in progressGoal: 50% for Incubation project in BeijingGuidance on Code Coverage and Static Code Analysis

Tools: Sonar

Is there any pending commit request older than 36 Business hours in Gerrit?nohttps://gerrit.onap.org/r/#/q/status:open+vnfsdk

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

yesUpgrading out-of-date components and addressing other issuesEnsure 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)?

Provide link to evidence

pending commits


Are all binaries available in Nexus?

https://nexus.onap.org/content/repositories/public/org/onap/vnfsdk/

pending commits


Integration and Testing

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


https://jenkins.onap.org/view/vnfsdk/

pending commits


Has the project code successfully passed the Daily Build process?NAdeferred until daily builds start again at M4Goal is to ensure the latest project commit has not broken the Integration Daily Build