CLAMP R1 Amsterdam Release - M2 Functionality Freeze Milestone

Product Management

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

Yes

APIs were defined at M1

Is there a final list of externally consumable APIs available?

N/A

CLAMP is not providing any external outcoming API for ONAP R1

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

Yes

Provide Link to Project backlog

Difference between a Product and Sprint Backlog

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

Yes

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).

Yes

There remains a minor design item pending (blueprint for SDC) but this is not blocking

Link 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

CLAMP is new from 2017 so no modification to add in header

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

Main LICENSE.txt available at the root of the project

Guidance for source code file that can't be edited

Has the project FOSS Table been updated with latest third party code?

Yes

Link to FOSS list for CLAMP

Your project FOSS table is located under Project FOSS master page

Do you have a plan to address any issue raised by FOSSology?

N/A

No issue raised by FOSSology (was run internally at AT&T) before publishing the code

Have all API projects dependencies been captured?

Yes

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.

Development

For new projects approved for this release, have all defined repositories source code been placed into Gerrit?

Yes

link to CLAMP gerrit repo

CLAMP has a single repository for its first version

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

Yes

Sonar link

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.

No

As discussed between AT&T Legal & LF council, the agreed license.txt and copyright are added to CLAMP repo.

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

No

Have all the Jenkins jobs successfully passed (Merge-Jobs)?

Yes

link to CLAMP Jenkins project tab

Are all snapshot binaries available in Nexus?

Yes

link to Nexus project folder

Integration and Testing  

Have functional test cases been documented in wiki?

Yes

link to functional test cases in wiki

Have you implemented in Jenkins at least 1 functional test case for each of the project repository?

Yes

see CSIT Jenkins tab

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.

Documentation

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

Yes

These are captured in stories in planned sprints