OOM Beijing - M2 Deliverables for Functionality Freeze Milestone Checklist
- Roger Maitland
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 | Provide link to evidence | OOM Provides no APIs | |
For all completed Sprints, have Sprint Backlog Stories been marked as "Done" in Jira? | Yes | |||
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 | Link to blockers. - OOM is in the closed list | ||
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 | See OOM-677 | 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) | NA | |||
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 | |||
(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 | See OOM-677 | ||
(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? | Yes | |||
Have all API projects dependencies been captured? | N/A | Provide link to the "API Incoming Dependency" section within your project M1 Release Planning deliverable. | 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? | N/A | ||
Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | N/A | |||
Is there any binaries (jar, war, tar, gz, gzip, zip files) in Gerrit project repository? | No | |||
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. | Underway | The cloudify-onap directory will be removed. | ||
Is there any pending commit request older than 36 business hours in Gerrit? | Yes | See search | Several of these need to be abandoned | |
Have all the Jenkins jobs successfully passed (Merge-Jobs)? | No | See here for the sonar job that fails due to lack of support for the language go. All others pass. | ||
Are all snapshot binaries available in Nexus? | N/A | Provide link to evidence in Nexus project folder | ||
Integration and Testing | Have functional test cases been documented in wiki? | Yes | ||
Have you implemented in Jenkins at least 1 functional test case for each of the project repository? | Yes | As an example (provided by Integration Team) | ||
Has the project code successfully passed the Build process? | N/A | 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 |