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.
| Info |
|---|
|
- Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki.
- Fill out the Yes/No column
- Provide link to evidence (when necessary)
|
| Practice Area | Checkpoint | Yes/No | Evidence - Comment | How to? |
|---|
| Product Management | Are all provisional APIs interface (stub) been defined (at beta-quality level)? | YES |
|
|
| Is there a final list of externally consumable APIs available? | YES | VNF Test Platform (VTP) |
|
For all completed Sprints, have Sprint Backlog Stories been marked as " |
DoneIssues are handled at JIRA issue level without sprint in place. How ever, to take the advantage of the sprint, we are started it again.DoneClosed" in Jira? | YES | |
|
| If applicable to your project, has your team been able to clear |
the | the project' blockers? If not provide status on the plan to close the blocker(s). | NA |
| Link to blockers. |
| What new features or changes to existing features in this project scope need to be communicated to VNF Providers? List the changes in the Evidence tab. | NA |
|
|
| If yes to the previous question, have these been communicated to the VNF Requirements project? | NA |
|
|
Release Management
| Have all source code files been updated with License Apache 2 header? | YES |
| Specific rules and instruction are available |
in | in ONAP wiki. |
| Has the year format in copyright header of all source code files been updated? (Rules for new files created in |
2018 | 2019 and existing files modified in |
2018 a file | file been placed at the root directory for which the license is applicable? | YES |
License.txt is already available | Has | 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 |
|
|
| 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 |
Link.| Model & Interface details (same as earlier) | 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 | Provide link to evidence | 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 50% request functional test cases been functional test cases i.e. CSIT been documented in wiki? It should include at least 1 or 2 CSIT that will be run on Lab-xxx-OOM-Daily Jenkins Job | YES |
Link an an example (provided by Integration Team)
|
| Has the project code successfully passed the Build process? | YES | https://jenkins.onap.org/view/cli/job/cli-master-merge-java/ | 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? |
YesR4 CLI Security/Vulnerability - Full Content| YES |
|
|
| Security | Has the Release Security/Vulnerability table been updated in the protected Security Vulnerabilities wiki space? |
Yes | | YES | Table in in the protected Security Vulnerabilities wiki space corresponding to the latest NexusIQ scan | PTL reviews the NexusIQ scans for their project repos and fills out the vulnerability review table |
| Have all project containers been designed to run as a non-root user? |
Yes| YES |
| https://wiki.onap.org/display/DW/Best+Practices - The Docker and Kubernetes engines may run as root until such time as the products support non-root execution.
- Applications may run as root within a container.
- The process ID of a container must not run as the root ID with the exception of containers supporting ONAP features that require the container to run as the root ID.
- Containers may run with root privileges.
- Project containers that run as the root ID must document this in the release notes along with the functionality that requires the container to run as the root ID.
|