...
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 Area | Checkpoint | Yes/No | Evidence - Comment | How to? | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product Product Management | Are all provisional APIs interface (stub) been defined (at beta-quality level)? | Yes | There are no provisional API's. The policy team will not make changes to its current API for R1. | ||||||||||||
| Is there a final list of externally consumable APIs available?Provide link to evidence | Yes | Policy API | |||||||||||||
For all completed Sprints, have Sprint Backlog Stories been marked as "Done" in Jira? | Provide Link to Project backlog | Policy R1 Deliverables for Functionality Freeze Milestone Checklist TemplateYes | https://jira.onap.org/secure/RapidBoard.jspa?projectKey=POLICY&rapidView=15&view=planning | Difference between a Product and Sprint Backlog | |||||||||||
Are all tasks associated with the completed Sprint Backlog Stories been marked as "Done" in Jira? | Has all Product Backlog not implemented in current release been scoped for next release? | Provide link to issue scoped for next release | 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 | Link to blockers. | |||||||||||||
| Release Management | Have all source code files been updated with License Apache 2 header? | Definition of Source code fileYes | |||||||||||||
| 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 | |||||||||||||
| 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 | Yes | https://lf-onap.atlassian.net/wiki/display/DW/Policy+Framework
| |||||||||||||
| Do you have a plan to address any issue raised by Fossology? | No Issues | If anything comes up we will address. | |||||||||||||
| Development | For new projects approved for this release, have all defined repositories source code been placed into Gerrit? | Provide link to evidenceYes | 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 | |||||||||||||
| Is there any binaries (jar, war, tar, gz, gzip, zip files) in Gerrit project repository?Policy R1 Deliverables for Functionality Freeze Milestone Checklist Template | No | Refer to CI Development Best Practices | |||||||||||||
| Could you ensure ensure that all proprietary trademarks, logos, product names, company name, etc. have been removed? All OPEN-O ONAP deliverables must comply with this rule and be agnostic of any proprietary symbols. | No | AT&T Legal did not approve it and LF Council has been informed. | |||||||||||||
| Is there any pending commit request older than 24 36 business hours in Gerrit? | No | ||||||||||||||
| Are Have all the Jenkins jobs successfully passed (Merge-Jobs)? | Provide link to "Merge job" as evidence in Jenkins project tab | Jenkins has two types of Jobs "Verify" and "Merge". The question covers the "Merge-Jobs".Yes | |||||||||||||
| Are all snapshot binaries available in Nexus?Provide link to evidence in Nexus project folder | Yes | https://nexus.onap.org/#view-repositories;snapshots~browsestorage~org/openecomp/policy/ | |||||||||||||
| Integration and Testing | Have Continuous System Integration Testing (CSIT) Use Cases been functional test cases been documented in wiki? | Provide link to evidence | Template is available in wikiYes | Policy R1 Amsterdam Functional Test Cases | |||||||||||
| Have you implemented in Jenkins at least 1 CSIT 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).Yes | As an example (provided by Integration Team) | |||||||||||||
| Has the project code successfully passed the Daily Build process? | Yes | Goal is to ensure your project latest commits have not broken the Integration Daily Buildbuild.You have to check that the latest Integration Daily Build was not broken by your project. | |||||||||||||
| Documentation | Has the team identified and outlined the set of documentations to be delivered in this Release? | Yes | Policy - Architecture Policy API - API Definitions |