...
| Practice Area | Checkpoint | Yes/No | Evidence - Comment | How to? | ||
|---|---|---|---|---|---|---|
| Product Management | Are all provisional APIs interface (stub) been defined (at beta-quality level)? | N/A | No APIs | |||
| Is there a final list of externally consumable APIs available? | N/A | Provide link to evidence | ||||
For all completed Sprints, have Sprint Backlog Stories been marked as "Done" in Jira? | YES | 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? | 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). | No | Still awaiting some seed code reposYES | Link to blockers. | |||
| Release Management | Have all source code files been updated with License Apache 2 header? | No | Still awaiting some seed code repos | 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) | No | Still awaiting some seed code reposYES | 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? | No | Still awaiting some seed code repos | YES | Guidance for source code file that can't be edited | ||
| Has the project FOSS Table been updated with latest third party code? | No | 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? | Yes | in the image-scanner repo: · LGPL-2.1+ license for “chardet” component is a dynamically built and not a problem as we understand · MPL-2.0 license for “python-certifi” component is a dynamically built and not a problem as we understand | The non-project licenses (those other than Apache-2.0 / CC-BY-4.0) will need to be approved for a license exception by the ONAP Governing Board prior to release. | |||
Have all API projects dependencies been captured? | Yes | M1 Release Planning#ThirdPartyProductsDependencies | No API dependnecies idenitifed | |||
| Development | For new projects approved for this release, have all defined repositories source code been placed into Gerrit? | NO | vvp/devkit vvp/ansible-ice-bootstrap vvp/portal vvp/engagementmgr vvp/cms vvp/jenkins vvp/postgresql vvp/gitlab vvp/documentation | 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) | NO | Goal: 30-50% for Incubation project | ||||
| 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)? | NO | Provide link as evidence to Jenkins project tab | ||||
| Are all snapshot binaries available in Nexus? | NO | Provide link to evidence in Nexus project folder | ||||
| Integration and Testing | Have functional test cases been documented in wiki? | NO | Provide link to evidence | |||
| Have you implemented in Jenkins at least 1 functional test case for each of the project repository? | NO | 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? | NO | Not at ONAP, but code is in production in AT&T environment | ||||
| Documentation | Has the team identified and outlined the set of documentations to be delivered in this Release? | NOYES |