...
| Practice Area | Checkpoint | Yes/No | Evidences | How to? | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product Management | Are committed Product Backlog Stories been coded and marked as "Closed" in Jira? | Yes for OOM. For the offline installer sub project, stories are remaining open as per discussion with Jim on acceptable exceptions. These stories will be delivered independently of Dublin sign-off. |
| |||||||||
| Are all tasks associated with committed Product Backlog Stories been marked as "Closed" in Jira? | Yes | See above. | ||||||||||
| Provide the project features list under the form of a bulleted list. | Yes | Release notes up for review and to be merge d shortly: https://gerrit.onap.org/r/#/c/oom/+/89388/ | ||||||||||
Summarize any functionalities that were planned at Release planning and not delivered at Release Sign-Off | Yes | Deferred to El Alto
| ||||||||||
| Release Management | Have all issues pertaining to FOSS been addressed? | N/A | ||||||||||
| Have all findings from previous milestones been addressed? | Yes | |||||||||||
| Development | Are all the Jenkins jobs successfully passed (verify + merge jobs)? | Yes | https://jenkins.onap.org/view/oom/job/oom-master-merge-helm/ | https://jenkins.onap.org/view/Merge-Jobs/ | ||||||||
| Are all binaries available in Nexus Release repository? | Yes | There are Helm Chart artifacts in the Staging repo in Nexus: https://nexus.onap.org/content/sites/oom-helm-staging/master/ Once the Dublin branch is cut for OOM (awaiting sign off from Integration), artifacts will move to https://nexus.onap.org/content/sites/oom-helm-release/4.0.0-ONAP/ This is a manual LF initiated activity. | ||||||||||
| Are all Docker images available In Nexus? | N/A | Provide link to evidence | ||||||||||
| Are the Java and Docker manifest updated with the same version as in Nexus Release repository? | N/A | |||||||||||
| OOM to Tag Release + Version in Helm Chart | ?N/A | |||||||||||
| 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 | N/A | Provide link to evidence | Goal is to increase our confidence the latest commit did not break the major functionality. Jenkins CSIT Jobs | ||||||||
| Has the project code successfully passed the Daily Build process? | N/A | 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 | N/A | 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? | N/A | |||||||||||
| Documentation | Has your team completed (reviewed, submitted and cherry picked) all documentation planned for the Dublin Release?
Provide Link to ReadTheDocs Release Notes Provide Link to ReadTheDocs Project Documentation | Yes | https://onap.readthedocs.io/en/latest/release/releaserepos.html#doc-releaserepos https://onap.readthedocs.io/en/latest/guides/onap-user/platformoperations.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 |
...