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.
Usage
- 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. | All new functional features introduced in Dublin have API stubs defined: Existing APIs: API Specifications for OOF Applications | |
| Is there a final list of externally consumable APIs available? | Yes | |||
For all completed Sprints, have Sprint Backlog Stories been marked as "Closed" in Jira? | Yes | Getting issues... | Difference between a Product and Sprint Backlog | |
Are all tasks associated with the completed Sprint Backlog Stories been marked as "Closed" in Jira? | Yes | Getting issues... | ||
| 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 | One risk has been identified for OOF with regards to K8S based CSIT, and the risk has been assessed. | Dublin Risks | |
| 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 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 license issues has been reported for OOF in the latest review. | ||
| 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 | OOF Dublin M1 Release Planning#APIIncomingDependencies | 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? | No | 3 existing repos cmso, osdf, HAS are good to go. 1 new repo created in Dublin (fgps) is yet to have the seed code upstreamed. However, the functional feature dependent on this repo is a POC. | 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 | |||
| 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)? | Yes | https://jenkins.onap.org/view/optf/job/optf-has-master-conductor-merge-java/ https://jenkins.onap.org/view/optf/job/optf-osdf-master-osdf-merge-java/ https://jenkins.onap.org/view/optf/job/optf-cmso-master-merge-properties-java/ | ||
| Are all snapshot binaries available in Nexus? | Yes | https://nexus.onap.org/content/groups/staging/org/onap/optf/ | ||
| Integration and Testing | Have 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 | OOF Dublin (R4) Functional Testing planning There is one CSIT bundled within the health check that interacts with an external dependency Music. Adding additional CSIT with the robot is an item that is in the Dublin risks and assessed. | |
| Have you implemented in Jenkins at least 1 functional test case for each of the project repository? | No | CSIT for the 3 existing repos have been successfully running. https://jenkins.onap.org/view/CSIT/ FGPS repo still needs to have the seed code upstreamed and the CSIT set up for it. | 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 | ||
| Security | Has the Release Security/Vulnerability table been updated in the protected Security Vulnerabilities wiki space? | Yes | 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 | None of the OOF containers run with securityContext: privileged: true | https://wiki.onap.org/display/DW/Best+Practices
|