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.
|
| Practice Area | Checkpoint | Yes/No | Evidence - Comment | How to? | ||||
|---|---|---|---|---|---|---|---|---|
| Product Management | Are all provisional APIs interface (stub) been defined (at beta-quality level)? | Yes | Outgoing dependencies: Incoming dependencies: OOF - MultiCloud interaction in R2 | |||||
| Is there a final list of externally consumable APIs available? | Yes | |||||||
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). | 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 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 | 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 | optf/osdf: https://gerrit.onap.org/r/gitweb?p=optf/osdf.git;a=blob_plain;f=LICENSE.txt;hb=HEAD optf/has: https://gerrit.onap.org/r/#/c/29533/ | 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 | Reviewed the licenses for the seed-code with Steve Winslow, and got an okay for it to be upstreamed to OOF repos. | ||||||
| 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 | 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? | Yes | https://gerrit.onap.org/r/#/q/status:merged+projects:optf/osdf https://gerrit.onap.org/r/#/q/status:merged+projects:optf/has | 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) | No | Goal: 50% for Incubation project in Beijing optf/osdf: The most recent commit (https://jenkins.onap.org/job/optf-osdf-master-osdf-verify-python/6/console) shows 377 out of 576 statments covered (out of a total of 1107 statements), making it 34% code coverage. However, there is a pending commit, which showed 708 out of 1107 statements (64% coverage). Since this is the seed code and a new project, we anticipate to mainitain the coverage and gradually improve it as new functionality and more scenarios are added. optf/has: Team has started delivering unit tests using python unit testing framework. Current coverage is 27% (coverage_has_12Feb2018.html). Resources have been committed to working on unit tests to reach the target coverage in the subsequent sprints. | ||||||
| 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/ The verify jobs are running fine, the merge job is failing due to some mismatch in naming conventions used for Nexus. Working with LF ONAP Helpdesk#52267 to resolve this. For optf/osdf, we are working on setting up the merge job and expect to have it ready early in the week of 2018-02-12 | ||||||
| Are all snapshot binaries available in Nexus? | No | Same as above - working with LF ONAP Helpdesk#52267 to resolve this. | ||||||
| Integration and Testing | Have functional test cases been documented in wiki? | Yes | OOF Beijing (R2) Functional Testing planning | |||||
| Have you implemented in Jenkins at least 1 functional test case for each of the project repository? | Yes* | Clearing the issue we are having with merge-jobs described will resolve this as well. The user story corresponding to this task is currently being worked on at OPTFRA-5. [JIRA Link] | As an example (provided by Integration Team) | |||||
| Has the project code successfully passed the Build process? | Yes | optf/has: https://jenkins.onap.org/view/optf/job/optf-has-master-conductor-verify-python/ optf/osdf: https://jenkins.onap.org/view/optf/job/optf-osdf-master-osdf-verify-python/ | 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 |
|