Skip to end of metadata
Go to start of metadata

The following items are expected to be completed for the project to Pass the M2 Functionality Freeze Milestone.

M2 Release Functionality Freeze Milestone definition.

Practice AreaCheckpointYes/NoEvidence - CommentHow to?
Product Management

Are all provisional APIs interface (stub) been defined (at beta-quality level)? 


only part of the identified functionalities are provided with required CLI impl. in place. others will be addressed in up-comming milestones.

Is there a final list of externally consumable APIs available?YES

Following APIs are available but IMO they are existing openecomp API. so CLI project will watch for the updated API in M3:




MSB / AAF API are missing in wiki.

For all completed Sprints, have Sprint Backlog Stories been marked as "Done" in Jira?

YES between a Product and Sprint Backlog

Are all tasks associated with the completed Sprint Backlog Stories been marked as "Done" in Jira?


If applicable to your project, has your team been able to clear the project' blockers? If not provide status on the plan to close the blocker(s).NANO BlockersLink to blockers.
Release Management

Have all source code files been updated with License Apache 2 header?YES
Specific rules and instruction are available in ONAP wiki.
Has the year format in copyright header of all source code files been updated? (Rules for new files created in 2017 and existing files modified in 2017 are different)YES
Guidance on year format
In case source code can't be edited, has a "License.txt" file been placed at the root directory for which the license is applicable?NAAll source code is provided with license.Guidance for source code file that can't be edited
Has the project FOSS Table been updated with latest third party code?YESCommand Line InterfaceYour project FOSS table is located under Project FOSS master page
Do you have a plan to address any issue raised by Fossology?NANO issues

Have all API projects dependencies been captured?

YESProvide link to the "API Incoming Dependency" section within your project M1 Release Planning deliverable.The source of information for the API dependency is the "API Incoming Dependency" of the M1 Release Planning deliverable. Please update the source accordingly, and let The Release Manager aware of the changes.
DevelopmentFor new projects approved for this release, have all defined repositories source code been placed into Gerrit?YES

Provide link to evidence

For evidences, provide link(s) to Gerrit repos by providing the URL as shown in this example


Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar)YESGoal: 30-50% for Incubation project

Guidance on Code Coverage and Static Code Analysis

Tools: Sonar

Is there any binaries (jar, war, tar, gz, gzip, zip files) in Gerrit project repository?NO
Refer to CI Development Best Practices
Could you ensure that all proprietary trademarks, logos, product names, company name, etc. have been removed? All ONAP deliverables must comply with this rule and be agnostic of any proprietary symbols.YES

Is there any pending commit request older than 36 business hours in Gerrit?NO
Have all the Jenkins jobs successfully passed (Merge-Jobs)?

Are all snapshot binaries available in Nexus?YES;quick~org.onap.cli
Integration and Testing  Have functional test cases been documented in wiki?YESCLI Functional test cases
Have you implemented in Jenkins at least 1 functional test case for each of the project repository?NO

Planning as part of next milestone, as CLI depends on the API freeze.

Has the project code successfully passed the Build process?YES

Goal is to ensure your project latest commits have not broken the build.

DocumentationHas the team identified and outlined the set of documentations to be delivered in this Release?YES