Skip to end of metadata
Go to start of metadata

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

M2 Release Functionality Freeze Milestone definition.

Practice AreaCheckpointYes/NoEvidence - CommentHow to?
Product Management

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


Is there a final list of externally consumable APIs available?noN/A

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

yesPortal Sprint 1Difference between a Product and Sprint Backlog

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

noPortal Backlog
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 blocksNo blockersLink to blockers.
Release Management

Have all source code files been updated with License Apache 2 header?yesWe did it for the ONAP Launch so we should be all good  
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)yesWe did it for the ONAP Launch so we should be all goodGuidance 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

We did it for the ONAP Launch so we should be all good but please also think about your new repos (if any)

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?YesPortal PlatformYour project FOSS table is located under Project FOSS master page
Do you have a plan to address any issue raised by Fossology?N/ANo issue raised by FOSSology (was run internally at AT&T) before publishing the code

Have all API projects dependencies been captured?

Yeslink 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.
DevelopmentFor new projects approved for this release, have all defined repositories source code been placed into Gerrit?Yes;a=tree

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


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

Goal: 30-50% for Incubation project

Note: Need to fix Jenkins jobs to reflect 30% coverage

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

removed binary files

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

Are all snapshot binaries available in Nexus?Yes;quick~portal.sdk
Integration and Testing  Have functional test cases been documented in wiki?YesPortal R1 Amsterdam Functional Test Cases
Have you implemented in Jenkins at least 1 functional test case for each of the project repository?Yes



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?yesPortal Architectures, SDK documentation