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.


Practice AreaCheckpointYes/NoEvidencesHow to?
Product ManagementAre committed Product Backlog Stories been coded and marked as "Closed" in Jira?yes

Key Summary Reporter Status
Loading...
Refresh


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

Key Summary Reporter Status
Loading...
Refresh


Provide the project features list under the form of a bulleted list.>>
  • Consistent ID of a Cloud Region: Adopt the ONAP format of ID when referring to a cloud region
  • Change Management - Flexible Designer & Orchestrator: Initiate workflows designed in SDC

Summarize any functionalities that were planned at Release planning and not delivered at Release Sign-Off

n/a(none)
Release ManagementHave all issues pertaining to FOSS been addressed?n/a

Have all findings from previous milestones been addressed?n/a(none)
DevelopmentAre all the Jenkins jobs successfully passed (verify + merge jobs)?yes

https://jenkins.onap.org/view/vid/job/vid-dublin-verify-java/

https://jenkins.onap.org/view/vid/job/vid-dublin-merge-java/

https://jenkins.onap.org/view/Merge-Jobs/
Are all binaries available in Nexus Release repository?yeshttps://nexus.onap.org/content/repositories/releases/org/onap/vid/vid-parent/4.2.0/
Are all Docker images available In Nexus?yeshttps://nexus3.onap.org/#browse/...
Are the Java and Docker manifest updated with the same version as in Nexus Release repository?yes

OOM to Tag Release + Version in Helm Chartyes

Integration and Testing

Have all CSIT Use Cases (created by each project team) passed?


It should include at least 1 CSIT that will be run on


Lab-xxx-OOM-Daily Jenkins Job

yeshttps://jenkins.onap.org/view/vid/job/vid-dublin-csit-healthCheck/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?yeshttps://jenkins.onap.org/view/vid/job/vid-dublin-docker-version-java-daily/Goal is to ensure the latest project commit has not broken the Integration Daily Build 
Has the project passed the Integration Sanity Testsyes

Integration sanity tests in Dublin Release cover:

  • ONAP deployment
  • All components health check
  • VNF onboarding and service creation for vFW use case
  • Model distribution for vFW
  • vFW instantiation
  • vFW closed loop
  • vFW deletion

No test failure reported on http://onapci.org/grafana/d/8cGRqBOmz/daily-summary?orgId=1

No Integration Blocking Issue with no workaround: Dublin Release Integration Test Blocking Issues

Has the project done the integration testing with related dependent projects?

in progress

In Dublin Release Integration Testing Status two use-cases still on-going; no issues pending on VID:

#22 Consistent ID of a Cloud Region

#13 Change Management - Flexible Designer & Orchestrator


Documentation

Has your team completed (reviewed, submitted and cherry picked) all documentation planned for the Dublin Release?

  1. Release Notes
  2. Project Documentation
  3. No remaining Documentation tickets
yes

JIRA Query

project != "Sandbox Project" AND project != "ONAP TSC" AND project != CI-Management AND (labels=Documentation OR project=Documentation) AND status != Closed ORDER BY fixVersion ASC, status DESC, priority DESC, updated DESC