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 T Created Updated Due Assignee Reporter P Status Resolution
Refresh

Jira Query

project=CLAMP AND issuetype= Story AND fixVersion ="Dublin Release" AND status != Closed ORDER BY fixVersion ASC, status DESC, priority DESC, updated

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

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Refresh

Jira Query

project=CLAMP AND issuetype!= Bug AND fixVersion ="Dublin Release" AND status != Closed ORDER BY fixVersion ASC, status DESC, priority DESC, updated

Provide the project features list under the form of a bulleted list.Yes
  • Stabilize Platform maturity by stabilizing CLAMP maturity matrix see `Wiki <Dublin Release Platform Maturity>`_.
  • CLAMP supports of Policy-model based Configuration Policy
  • CLAMP supports new Policy Engine direct Rest API (no longer based on jar provided by Policy Engine)
  • CLAMP main Core/UI have been reworked, removal of security issues reported by Nexus IQ.

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

Yes

Release ManagementHave all issues pertaining to FOSS been addressed?Yes

Have all findings from previous milestones been addressed?Yes

DevelopmentAre all the Jenkins jobs successfully passed (verify + merge jobs)?YesJenkins project tabhttps://jenkins.onap.org/view/Merge-Jobs/
Are all binaries available in Nexus Release repository?YesNexus project folder
Are all Docker images available In Nexus?YesNexus project folder
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

Yes

CSIT jenkins

but we didn't have time to integrate to OOM Lab test (see risk raised on this topic on the Dublin risk page)

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?YesJenkins project tabGoal 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?

Yes

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

https://docs.onap.org/en/dublin/submodules/clamp.git/docs/release-notes.html

https://docs.onap.org/en/dublin/submodules/clamp.git/docs/index.html


Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Refresh

JIRA Query

((labels=Documentation AND project=CLAMP) OR (labels=CLAMP AND project=Documentation)) AND fixVersion ="Dublin Release" AND status != Closed ORDER BY fixVersion ASC, status DESC, priority DESC, updated DESC