...
| Practice Area | Checkpoint | Yes/No | Evidences | How to? | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product Management | Are all tasks associated with the release been marked as "Closed" in Jira? | Yes | Link to Jira | |||||||||||
| Have all findings from previous milestones been addressed? | N/A | Provide link to JIRA findings | ||||||||||||
| Development | Have all Defects of priority Highest and High been in status "Closed" in Jira? | Yes |
| |||||||||||
| Are all JIRA issues used as a reference in a commit in status "Closed" in Jira? | Yes | Very often, some JIRA issue remains in status "Todo" in JIRA while the commit they are referenced to is successful. | ||||||||||||
| Is there any pending commit related to Highest and High priority issues older than 36 hours in Gerrit? In case there are messages going back and forth between authors and reviewers, it is acceptable to be above 36 hours. | No | |||||||||||||
| Are all the Jenkins jobs successfully passed (verify + merge jobs)? | No | working on those failurethe failed jjb: https://jenkins.onap.org/view/multicloud/job/multicloud-k8s-master-merge-golang/ | ||||||||||||
Has the team delivered all their release artifacts in Nexus Release repo? There should be at least ONE version of each artifacts available in Nexus Release repo. | No | To be decided during Oct. 10th weekly meeting | Refer to Independent Versioning and Release Process for procedure | |||||||||||
| Integration and Testing | Have all CSIT Use Cases (created by each project team) passed? | No | Provide link to evidence. As things are moving fast, we want to ensure CSIT are still "green".Yes | https://jenkins.onap.org/view/CSIT/job/multicloud-master-csit-functionality1/ | ||||||||||
| At RC0, has the Pair Wise testing table been filled out? | Yes | Casablanca Pair Wise Testing master page | Due to the complexity of testing, SO/MC will not be pair-wise tested, neither the OOF/MC. These testing will be conducted as part of e2e testing | |||||||||||
| At RC0, have all OOM Release Healtcheck related to your project passed? | No | multicloud-windriver failed on health check on daily job. | The Root Cause is that the daily job is not executing with latest version of multicloud-windriver. This will be fixed automatically once the docker image are released after pariwise testing done | |||||||||||
| At RC0, is there a Docker image in Nexus Docker-Release repo available for each repository? | No | Provide link to evidence | pending on pairwise testing | |||||||||||
| Has the project code successfully passed the Daily Build process? | Yes | Goal is to ensure the latest project commit has not broken the Integration Daily Build | ||||||||||||
| Has the OOM deployment passed? | NoYes | Ensure in Jenkins External Labs all Health Check pass. | Yes for staging version, not for master version since the artifact/docker image version has not been released yet | |||||||||||
Has the Heat deployment passed? (not a gating item for Casablanca) | Yes | Ensure in Jenkins External Labs all Health Check pass. | ||||||||||||
| Documentation | For RC0, for project delivering binaries, has the team populated and validated all the sections of either the Platform Component or SDK template? No | Yes | Multi-VIM/Cloud has no SDK delivery. | Most teams have already created the high level file structures in readthedocs, and populated some actual documentation. However, the remaining sections of the appropriate teamplate must be completed. Platform: A&AI, APP-C, CLAMP, CLI, DCAE, DMaaP, Holmes, MSB, OOM, Policy, Portal, SDN-C SDC, SO, UseCase UI, VFC, VID SDKs: AAF, CCSDK, External API Framework, Multi VIM/Cloud, VNFSDK | ||||||||||
For RC1, has the team addressed any issue (recorded in JIRA) provided by the Documentation team? | N/A | |||||||||||||
For RC2, for project delivering binaries, has the team populated and validated all the sections of the Release Notestemplate? | N/A | |||||||||||||
| For RC2, has the Documentation Team provided the final approval for your project documentation? | N/A |
| To be decided during Oct. 10th weekly meeting |