Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

DRAFT PROPOSAL FOR COMMENTS

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

M2 Release Functionality Freeze Milestone definition.

...

titleUsage

...

.

...


Practice AreaCheckpointYes/NoEvidence - CommentHow to?
Product Management

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

nono new API were identified


Is there a final list of externally consumable APIs available?nowill be provided

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

n/a1st sprint not yet completeDifference between a Product and Sprint Backlog

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

n/a1st sprint not yet complete
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?yes
Guidance for source code file that can't be edited
Has the project FOSS Table been updated with latest third party code?yesVirtual Infrastructure DeploymentYour project FOSS table is located under Project FOSS master page
Do you have a plan to address any issue raised by Fossology?yesNo issues are identifiedIf any issues arise with Fossology, they will be addressed

Have all API projects dependencies been captured?

yesno new dependencies have been identifiedThe 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?N/A

http://ml636r@gerrit.onap.org/r/a/vid

http://ml636r@gerrit.onap.org/r/a/vid/asdcclient

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

Example

Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar)No, this is work in progressGoal: 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?Yesno binaries are currently in the repoRefer 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.No
This item is currently under discussion between AT&T Legal & LF Legal
Is there any pending commit request older than 36 business hours in Gerrit?No

Have all the Jenkins jobs successfully passed (Merge-Jobs)?Yeshttps://jenkins.onap.org/view/vid/


Are all snapshot binaries available in Nexus?Yeshttps://nexus.onap.org/#nexus-search;quick~org.openecomp.vid
Integration and Testing  Have functional test cases been documented in wiki?YesVID R1 Amsterdam - M2 Functional Test Cases
Have you implemented in Jenkins at least 1 functional test case for each of the project repository?Yes

https://jenkins.onap.org/view/vid/job/vid-master-verify-csit-healthCheck/

(the other repository is library, not dockerized)

As an example (provided by Integration Team)


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?YesDocumentation Epic