DRAFT PROPOSAL FOR COMMENTS
The following items are expected to be completed for the project to Pass Release Sign-Off Milestone.
Release Sign-Off Milestone overview is available in wiki.
| Info | ||
|---|---|---|
| ||
|
| Practice Area | Checkpoint | Yes/No | Evidences | How to? | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product Management | Are committed Product Backlog Stories been coded and marked as "Done" in Jira? | Yes |
| |||||||||||
| Are all tasks associated with committed Product Backlog Stories been marked as "Done" in Jira? | Yes |
| ||||||||||||
| Provide the project features list under the form of a bulleted list. | The ONAP Optimization Framework (OOF) is new in Beijing. A summary of features inclduesincludes:
| |||||||||||||
Summarize any functionalities that were planned at Release planning and not delivered at Release Sign-Off | Supporting VNF scale out is moved to R3, due to this being stretch goal for our dependencies. | |||||||||||||
| Release Management | Have all issues pertaining to FOSS been addressed? | Yes | No FOSS items have been flagged for OOF. | |||||||||||
| Have all findings from previous milestones been addressed? | Yes | Integration and pairwise testing with all our dependencies has passed. | ||||||||||||
| Development | Are all the Jenkins jobs successfully passed (verify + merge jobs)? | Yes | https://jenkins.onap.org/view/optf/ | |||||||||||
| Are all binaries available in Nexus Release repository? | Yes | |||||||||||||
| Are all Docker images available In Nexus? | Yes | https://nexus3.onap.org/#browse/search=keyword%3Doptf | ||||||||||||
| Are the Java and Docker manifest updated with the same version as in Nexus Release repository? | Yes | https://git.onap.org/integration/tree/version-manifest/src/main/resources/docker-manifest.csv | ||||||||||||
| Integration and Testing | Have all CSIT Use Cases (created by each project team) passed? | Yes | https://jenkins.onap.org/view/optf/job/optf-has-master-csit-has/ | Goal is to incease our confidence the latest commit did not break the major functionality. Jenkins CSIT Jobs | ||||||||||
| Has the project code successfully passed the Daily Build process? | Yes | https://jenkins.onap.org/view/optf/job/optf-has-master-conductor-docker-java-version-shell-daily/ https://jenkins.onap.org/view/optf/job/optf-osdf-master-osdf-docker-java-version-shell-daily/ https://jenkins.onap.org/view/optf/job/optf-osdf-master-osdf-release-version-java-daily/ https://jenkins.onap.org/view/optf/job/optf-has-master-conductor-release-version-java-daily/ | Goal is to ensure the latest project commit has not broken the Integration Daily Build | |||||||||||
Has the project done the integration testing with related dependent projects? | Yes | |||||||||||||
| Documentation | Has your team contributed and completed work in the following documentations in ReadTheDocs:
| Yes |
2. Project Documentation: https://onap.readthedocs.io/en/beijing/submodules/optf/has.git/docs/index.html https://onap.readthedocs.io/en/beijing/submodules/optf/osdf.git/docs/index.html |