AAI R4 Deliverables for Release Sign-Off Milestone Checklist

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.





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

Getting issues...



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

Yes

Getting issues...



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

Yes

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



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

N/A





Release Management

Have all issues pertaining to FOSS been addressed?

Yes





Have all findings from previous milestones been addressed?

WIP

1 issue still in Delivered state, waiting for Portal team to close after successfuly test

AAI-2411: Portal Pairwise testing: A&AI Redirect URL is incorrectClosed



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

https://nexus.onap.org/#view-repositories;releases~browsestorage



Are all Docker images available In Nexus?

Yes

nexus3.onap.org:10001



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

https://jenkins.onap.org/view/CSIT/

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

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

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

https://onap.readthedocs.io/en/dublin/guides/onap-developer/developing/index.html#active-and-available-inventory

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