M2 Checklist - DOC 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

How to integrate project source into documentation



Is there a final list of externally consumable APIs available?

Yes

Sphinx Reference Documentation



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

Sprint 1 in-progress

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?







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

NA



Link to blockers.

Release Management


Have all source code files been updated with License Apache 2 header?





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)





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?



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?







Have all API projects dependencies been captured?



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?

Yes

doc/ and doc/tools/

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)



Goal: 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?

Yes

Sphinx permits the use of png images, some of these will remain in the repository (eg. ONAP Logo).   Source editable images are preferred for all new or modified documents using Sphinx extensions.

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.







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

No





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

in-progress

Provide link as evidence to Jenkins project tab



Are all snapshot binaries available in Nexus?

NA

Alpha version / latest version published at onap.readthedocs.io



Integration and Testing  

Have functional test cases been documented in wiki?

in-progress

Provide link to evidence



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



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

As an example (provided by Integration Team)



Has the project code successfully passed the Build process?





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?