...
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.
| Info | ||
|---|---|---|
| ||
|
...
| Practice Area | Checkpoint | Yes/No | Evidences | How to? | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product Management | Are committed Product Backlog Stories been coded and marked as "Closed" in Jira? | Yes |
| |||||||||||||
| Are all tasks associated with committed Product Backlog Stories been marked as "Closed" in Jira? | No |
| The 2 tasks 1 task left are:
| |||||||||||||
| Provide the project features list under the form of a bulleted list. | Yes | See Release Notes | ||||||||||||||
Summarize any functionalities that were planned at Release planning and not delivered at Release Sign-Off | Yes |
| ||||||||||||||
| Release Management | Have all issues pertaining to FOSS been addressed? | Yes | ||||||||||||||
| Have all findings from previous milestones been addressed? | Yes | |||||||||||||||
| Development | Are all the Jenkins jobs successfully passed (verify + merge jobs)? | No | Failed since oparent 2.0.0 update, however the images were released before this change. | https://jenkins.onap.org/view/Merge-Jobs/ | ||||||||||||
| Are all binaries available in Nexus Release repository? | Yes | https://nexus.onap.org/#nexus-search;quick~onap/logging | ||||||||||||||
| Are all Docker images available In Nexus? | Yes | https://nexus3.onap.org/#browse/search=keyword%3Dpomba%20AND%20version%3D1.4.0 | ||||||||||||||
| Are the Java and Docker manifest updated with the same version as in Nexus Release repository? | YesNo | Pending on this patch: https://gerrit.onap.org/r/c/integration/+/89769 | ||||||||||||||
| OOM to Tag Release + Version in Helm Chart | Yes | |||||||||||||||
| 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 | Provide link to evidence | Goal is to incease our confidence the latest commit did not break the major functionality. Jenkins CSIT JobsNo | essentially the pairwise testing is csit - since no library is exported -
| ||||||||||||
| Has the project code successfully passed the Daily Build process?Provide link to evidence | No | Builds were passing until the oparent 2.0.0 update, however the images were released before this change. | 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:
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 | POMBA - Functional Test Cases (Dublin) | ||||||||||||||
| Documentation | Has your team completed (reviewed, submitted and cherry picked) all documentation planned for the Dublin Release?
| No | https://docs.onap.org/en/dublin/submodules/logging-analytics.git/docs/release-notes.html Provide Link to ReadTheDocs Project Documentation | Yes for Release Note. No for project documentation - POMBA |
...