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)? | N/A | OOM Provides no APIs | |
| Is there a final list of externally consumable APIs available? | N/A | OOM Provides no APIs | ||
For all completed Sprints, have Sprint Backlog Stories been marked as "Done" in Jira? | Yes | 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). | Yes | Risk item #6 added. Email sent to Portal PTL, regarding risk item #4. Hi Manoop, I just saw Casablanca risk item #4 on Casablanca Risks. I’m not completely clear if the risks that your team has identified are caused by OOM or are to be addressed using OOM to meet Casablanca requirements? Regardless, is there something that the OOM team can do to help address this risk? Thanks, Mike. | Need LF to complete build process to generate and publish Helm charts to LF hosted repository. Will work with Portal team to address risk item #4. | |
| 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. | None | |||
| If yes to the previous question, have these been communicated to the VNF Requirements project? | N/A | |||
| Release Management | Have all source code files been updated with License Apache 2 header? | Underway | License updates are enforced for all new OOM patches submitted for review before being merged into repo. Any files that were merged prior to Beijing enforcement, will be updated via OOM-1123 | 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 | During ongoing development of Casablanca features, all new and modified files will include current year 2018. | 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 | OOM Global License File | 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? | Underway | License updates are enforced for all new OOM patches submitted for review before being merged into repo. Any files that were merged prior to Beijing enforcement, will be updated via OOM-1123 | ||
| (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 violations see report | ||
| 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? | N/A | |||
Have all API projects dependencies been captured? | N/A | OOM provides no APIs. | ||
| Development | For new projects approved for this release, have all defined repositories source code been placed into Gerrit? | N/A | ||
| Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | N/A | Helm/Kubernetes do not have unit tests and is not supported by Sonar. See Sonar OOM Results | ||
| 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. | In Progress | OOM-1297 - Getting issue details... STATUS | The cloudify-onap directory will be removed as part of this story. | |
| Is there any pending commit request older than 36 business hours in Gerrit? | Yes | See search | Ignore patches in Draft state as they are works in progress and not to be merged. | |
| Have all the Jenkins jobs successfully passed (Merge-Jobs)? | Yes | OOM CD Jenkins Jobs | ||
| Are all snapshot binaries available in Nexus? | No | Blocked waiting on OOM-752 - Getting issue details... STATUS to be delivered by LF. See Casablanca Risks # 6. | ||
| Integration and Testing | Have functional test cases been documented in wiki? | Yes | Functional testing of ONAP using ROBOT health checks, validates OOM deployments as seen in Auto Continuous Deployment via Jenkins and Kibana | |
| Have you implemented in Jenkins at least 1 functional test case for each of the project repository? | Yes | Functional testing of ONAP using ROBOT health checks, validates OOM deployments as seen in Auto Continuous Deployment via Jenkins and Kibana | ||
| Has the project code successfully passed the Build process? | Yes | OOM CD Jenkins Jobs | Makefile was added to OOM in Beijing to "build" helm charts. This is part of the oom build jobs running in Jenkins. | |
| Documentation | Has the team identified and outlined the set of documentations to be delivered in this Release? | Yes | Updates will be made to the official OOM User, Developer and Cloud Setup Guides at readthedocs in response to the user stories being delivered in Casablanca. |