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 AreaCheckpointYes/NoEvidence - CommentHow to?
Product Management

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

YesOOM exposing Helm and K8S APIs - fully defined.


Is there a final list of externally consumable APIs available?YesProvide link to evidence

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

YesOOM Jira BoardDifference between a Product and Sprint Backlog

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

YesOOM Jira Board
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).YesNo blockersLink to blockers.
Release Management

Have all source code files been updated with License Apache 2 header?In progressSome files still need to be updatedSpecific 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

LICENSEGuidance 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?YesLICENSEGuidance for source code file that can't be edited
Has the project FOSS Table been updated with latest third party code?YesONAP Operations ManagerYour project FOSS table is located under Project FOSS master page
Do you have a plan to address any issue raised by Fossology?Yes

Have all API projects dependencies been captured?

Yes

https://wiki.onap.org/display/DW/OOM++-+M1+Release+Planning+Template

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

OOM Gerritt

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)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)?Yes


Are all snapshot binaries available in Nexus?YesProvide link to evidence in Nexus project folder
Integration and Testing  Have functional test cases been documented in wiki?YesOOM Deployment Status
Have you implemented in Jenkins at least 1 functional test case for each of the project repository?N/AOOM is leveraging the functional tests from all other projects to be successful.

As an example (provided by Integration Team)


Has the project code successfully passed the Build process?N/ANo build required.

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?YesOOM User Guide