Release Sign-Off Milestone Checklist VVP
- Steven wright
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? |
|---|---|---|---|---|
Product Management | Are committed Product Backlog Stories been coded and marked as "Closed" in Jira? | Yes | Link to Jira | |
Are all tasks associated with committed Product Backlog Stories been marked as "Closed" in Jira? | Yes | Link to Jira | ||
Provide the project features list under the form of a bulleted list. | yes | Link to evidence https://docs.onap.org/en/dublin/submodules/vvp/documentation.git/docs/release-notes.html | ||
Summarize any functionalities that were planned at Release planning and not delivered at Release Sign-Off | No | none | ||
Release Management | Have all issues pertaining to FOSS been addressed? | Yes | ||
Have all findings from previous milestones been addressed? | Yes | Provide link to JIRA findings | ||
Development | Are all the Jenkins jobs successfully passed (verify + merge jobs)? | Yes | ||
Are all binaries available in Nexus Release repository? | Yes | Provide link to evidence https://nexus3.onap.org/#browse/search=keyword%3D%22onap%2Fvvp%2Fvalidation%22 | ||
Are all Docker images available In Nexus? | Yes | Provide link to evidence https://nexus3.onap.org/#browse/search=keyword%3D%22onap%2Fvvp%2Fvalidation%22 | ||
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 | NA | VVP is stand alone tool - not built by OOM | ||
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 | NA | Provide link to evidence VVP is stand alone tool not used in existing use cases. | 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 | NA | VVP is stand alone tool not used in existing use cases. | Integration sanity tests in Dublin Release cover:
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? | NA | VVP is stand alone tool not used in existing use cases. | ||
Documentation | Has your team completed (reviewed, submitted and cherry picked) all documentation planned for the Dublin Release?
| yes | Provide Link to ReadTheDocs Release Notes https://docs.onap.org/en/dublin/submodules/vvp/documentation.git/docs/release-notes.html Provide Link to ReadTheDocs Project Documentation https://docs.onap.org/en/dublin/guides/onap-provider/vnfvalidator.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 |