CLAMP R2 - M2 Functionality Freeze Milestone Checklist
- ChrisC
The following items are expected to be completed for the project to Pass the M2 Functionality Freeze Milestone.
M2 Release Functionality Freeze Milestone definition.
Practice Area | Checkpoint | Yes/No | Evidence - Comment | How to? |
|---|---|---|---|---|
Product Management | Are all provisional APIs interface (stub) been defined (at beta-quality level)? | Yes | APIs were defined at M1 | |
Is there a final list of externally consumable APIs available? | N/A | CLAMP is not providing any external outcoming API for ONAP R2 | ||
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 | No specific blocker as of now | ||
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. | N/A | No impacting feature for VNF | ||
If yes to the previous question, have these been communicated to the VNF Requirements project? | N/A | No impacting feature for VNF | ||
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) | N/A | Clarification from LF provided that this is not mandatory. | ||
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? | 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 | Note that files are being modified and designer part is being removed which will remove the problem identified | ||
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 | Planned for removal | ||
Have all API projects dependencies been captured? | Yes | |||
Development | For new projects approved for this release, have all defined repositories source code been placed into Gerrit? | N/A | CLAMP is not a new project | |
Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | No | Goal: 50% for Incubation project in Beijing - Plan is to reach this level by M4 | ||
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. | 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 | |||
Are all snapshot binaries available in Nexus? | Yes | |||
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? | 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 |