APPC M2 Functionality Freeze Milestone Checklist (Amsterdam Release)

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.



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 Area

Checkpoint

Yes/No

Evidence - Comment

How to?

Practice Area

Checkpoint

Yes/No

Evidence - Comment

How to?

Product Management

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

Yes

API Guide

APIs needed for support of vCPE and regression of vFW are available; Additional APIs will be contributed in Sprint 2, but no one has dependencies on these and API Guide will be updated accordingly.

Currently details can be found here: APPC_OAM_Overview - ONAP.pdf

Is there a final list of externally consumable APIs available?

Yes

API Guide

What is needed to support vCPE use case and regression of vFW use case, which is what APPC committed for R1, are available.

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

Yes

APPC Project backlog

Difference between a Product and Sprint Backlog

First sprint kicked off on 8/1, however some items were completed outside of sprint and are correctly marked in Jira.

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

Yes



First sprint kicked off on 8/1, however some items were completed outside of sprint and are correctly marked 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).

No

Yes



Link to blockers.

Still waiting on ODL docker from SDNC team; current ETA is 8/4.

9/10/17: ODL provided by CCSDK.

MultiVIM integration - mitigation plan if MutlVIM & CDP-PAL are not ready by end of Aug for integration testing is to fall back to CDP-PAL, which is what APPC is currently using.

9/10/17: Integration testing planning in progress

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

This was done for ONAP Launch

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?

Yes

Provide link to evidence

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



If any issues arise with Fossology, they will be addressed

Have all API projects dependencies been captured?

Yes

Provide 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?

N/A

No new repo

https://gerrit.onap.org/r/#/admin/projects/appc

https://gerrit.onap.org/r/#/admin/projects/appc/deployment

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)

Work in progress

Goal: 30-50% for Incubation project



Guidance on Code Coverage and Static Code Analysis

Tools: Sonar

Note that trouble tickets was submitted to LF Helpdesk because Sonar is inconsistent in reporting Unit Test/Code Coverage.

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 removal of trademark and company name is not applicable to AT&T.

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

No





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

Yes

APPC Jenkins

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

Are all snapshot binaries available in Nexus?

Yes

APPC Snapshots

https://nexus.onap.org/content/repositories/snapshots/

Integration and Testing  

Have functional test cases been documented in wiki?

Yes

APPC Functional Test Cases



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

Yes

As an evidence, provide a link to Jenkins (CSIT Jobs) that shows a sample test case implemented (1 job for each repo).

https://gerrit.onap.org/r/#/c/8635/

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

Documentation Epic