Skip to end of metadata
Go to start of metadata

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.


Usage

  1. Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki.
  2. Fill out the Yes/No column
  3. Provide link to evidence (when necessary)
Practice AreaCheckpointYes/NoEvidencesHow to?
Product ManagementAre committed Product Backlog Stories been coded and marked as "Done" in Jira?Yes

Getting issues...


Are all tasks associated with committed Product Backlog Stories been marked as "Done" in Jira?Yes

Getting issues...


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 includes:

  • Baseline Homing functionality
    • Homing support for VCPE use case
    • Support for enhanced homing using HPA (Hardware Platform Awareness)
  • Integration with SO, Policy, AAI, and Multi-Cloud
  • S3P maturity and integration with OOM.

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 ManagementHave all issues pertaining to FOSS been addressed?YesNo FOSS items have been flagged for OOF.
Have all findings from previous milestones been addressed?YesIntegration and pairwise testing with all our dependencies has passed.
DevelopmentAre all the Jenkins jobs successfully passed (verify + merge jobs)?Yeshttps://jenkins.onap.org/view/optf/
Are all binaries available in Nexus Release repository?Yes
Are all Docker images available In Nexus?Yeshttps://nexus3.onap.org/#browse/search=keyword%3Doptf
Are the Java and Docker manifest updated with the same version as in Nexus Release repository?Yeshttps://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?Yeshttps://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

OOF Pair Wise Testing for Beijing Release

OOF Beijing S3P Status


Documentation

Has your team contributed and completed work in the following documentations in ReadTheDocs:

  1. Release Notes
  2. Project Documentation
Yes
  1. Release Notes: https://onap.readthedocs.io/en/beijing/submodules/optf/has.git/docs/sections/release-notes.html
    https://onap.readthedocs.io/en/beijing/submodules/optf/osdf.git/docs/sections/release-notes.html


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