...
| Practice Area | Checkpoint | Yes/No | Evidence - Comment | How to? |
|---|---|---|---|---|
| Product Management | Are all provisional APIs interface (stub) been defined (at beta-quality level)? | Yes | All interfaces of Beijing hold good. | |
| Is there a final list of externally consumable APIs available? | Yes | SO readthedocs | ||
For all completed Sprints, have Sprint Backlog Stories been marked as "Done" in Jira? | Yes | SO Issues Done | Difference between a Product and Sprint Backlog | |
Are all tasks associated with the completed Sprint Backlog Stories been marked as "Done" in Jira? | Yes | SO Issues Done | ||
| 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 | Link to blockers. | ||
| Release Management | Have all source code files been updated with License Apache 2 header? | 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 2018 and existing files modified in 2018 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 | ||
| (a) Has the Project Team added appropriate license and copyright notices to all ONAP source code and documentation files, where possible for the particular file format? | Yes | |||
| (b) Has the Project Team reviewed and understood the most recent license scan reports from the LF, for both (a) licenses within the codebase and (b) licenses for third-party build time dependencies? | Yes | No issue reported from LF scan | ||
| For both (a) and (b) questions, have all high priority non-Project Licenses been either removed, planned for removal before code freeze, or escalated as likely exception requests? | Yes | |||
Have all API projects dependencies been captured? | Yes | 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? | NA | Not a new project or repo is added. | 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 | SONAR SO passed quality control | ||
| 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 | No issue reported from LF scan | ||
| Is there any pending commit request older than 36 business hours in Gerrit? | No | All checkins are reviewed and merged / comments provided. | ||
| Have all the Jenkins jobs successfully passed (Merge-Jobs)? | Yes | Jenkins SO | The ARIA verify job will be deleted, merge request has been submitted for this already. | |
| Are all snapshot binaries available in Nexus? | Yes | Nexus SO | ||
| Integration and Testing | Have functional test cases been documented in wiki? | Yes | Beijing (R2) Functional Testing planning | |
| Have you implemented in Jenkins at least 1 functional test case for each of the project repository | yes | 30 CSIt test cases are running, | 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. | ||
| Documentation | Has the team identified and outlined the set of documentations to be delivered in this Release? | Yes |