...
| Practice Area | Checkpoint | Yes/No | Evidences | How to? | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product Management | Are committed Product Backlog Stories been coded and marked as "Closed" in Jira?Link to Jira | Yes |
| |||||||||||
| Are all tasks associated with committed Product Backlog Stories been marked as "Closed" in Jira?Link to Jira | Yes |
| ||||||||||||
| Provide the project features list under the form of a bulleted list. | Yes | http://onap.readthedocs.io/en/latest/submodules/portal.git/docs/release-notes.html
| ||||||||||||
Summarize any functionalities that were planned at Release planning and not delivered at Release Sign-Off | No | All planned functionalities are completed for the release. | ||||||||||||
| Release Management | Have all issues pertaining to FOSS been addressed? | Yes | ||||||||||||
| Have all findings from previous milestones been addressed?Provide link to JIRA findings | InProgress |
| ||||||||||||
| Development | Are all the Jenkins jobs successfully passed (verify + merge jobs)? | Yes | https://jenkins.onap.org/view/portal/ (required master branch verify and merge jobs are all PASSING) However, INFO yaml and maven stage jobs setup by LF support team recently are not critical, but they never passed at least once, so I request LF team to continue looking into it and fix them. | https://jenkins.onap.org/view/Merge-Jobs/ | ||||||||||
| Are all binaries available in Nexus Release repository?Provide link to evidence | Yes | https://nexus.onap.org/#nexus-search;quick~portal/sdk portal/sdk - (Release branch: “release-2.5.0”) | ||||||||||||
| Are all Docker images available In Nexus?Provide link to evidence | Yes | | ||||||||||||
| Are the Java and Docker manifest updated with the same version as in Nexus Release repository? | InProgress | https://git.onap.org/integration/tree/version-manifest/src/main/resources/docker-manifest.csv https://git.onap.org/integration/tree/version-manifest/src/main/resources/java-manifest.csv InProgress for Java manifest; docker images version updated. | ||||||||||||
| OOM to Tag Release + Version in Helm Chart | Yes | Portal team delivered to OOM, dockers tagged and released. | ||||||||||||
| 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/portal/Provide link to evidence | 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 | Daily build jobs are passingProvide 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 | InProgress | 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? | InProgress | |||||||||||||
| 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 | http://onap.readthedocs.io/en/latest/submodules/portal.git/docs/release-notes.html http://onap.readthedocs.io/en/latest/submodules/portal.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 |
...