SDC R4 Deliverables for Release Sign-Off Milestone Checklist

SDC R4 Deliverables for Release Sign-Off Milestone Checklist

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 Area

Checkpoint

Yes/No

Evidences

How to?

Practice Area

Checkpoint

Yes/No

Evidences

How to?

Product Management

Are committed Product Backlog Stories been coded and marked as "Closed" in Jira?

Yes

Link to Jira

key summary type created updated due assignee reporter priority status resolution
Loading...
Refresh

 

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

Yes

Link to Jira

key summary type created updated due assignee reporter priority status resolution
Loading...
Refresh

 

Provide the project features list under the form of a bulleted list.

  • Support PNF onboarding

  • SOL 001 v2.5.1 support

  • VSP compliance check feature

  • SDC and CDS integration

Link to evidence

 

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

Slicing, CCVPN use cases

 

 

Release Management

Have all issues pertaining to FOSS been addressed?

Yes

 

 

Have all findings from previous milestones been addressed?

Yes, except for an CSIT with OOM

Provide link to JIRA findings

 

Development

Are all the Jenkins jobs successfully passed (verify + merge jobs)?

Yes

 

https://jenkins.onap.org/view/Merge-Jobs/

Are all binaries available in Nexus Release repository?

Yes

Provide link to evidence

https://nexus.onap.org/content/repositories/releases/org/onap/sdc/

 

Are all Docker images available In Nexus?

Yes

Provide link to evidence

https://nexus3.onap.org/#browse/search=keyword%3Dsdc%20AND%20version%3D1.4.1

 

Are the Java and Docker manifest updated with the same version as in Nexus Release repository?

Yes

 

 

OOM to Tag Release + Version in Helm Chart

 

 

 

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

Provide link to evidence

https://jenkins.onap.org/job/sdc-dublin-csit-nightly-testng/

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

Provide link to evidence

https://jenkins.onap.org/job/sdc-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 Tests

Yes

 

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

Provide Link to ReadTheDocs Release Notes

https://onap.readthedocs.io/en/dublin/submodules/sdc.git/docs/release-notes.html

Provide Link to ReadTheDocs Project Documentation

https://onap.readthedocs.io/en/dublin/submodules/sdc.git/docs/index.html

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