...
This template must be filled out for every Release Candidate Milestone (RC0, 1, 2, x)
RC Release Candidate Milestone overview is available in wiki.
| Info | ||
|---|---|---|
| ||
|
| Practice Area | Checkpoint | Yes/No | Evidences | How to? | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product Management | Are all tasks associated with the release been marked as "Closed" in Jira? | Yes |
| |||||||||||||||||||||
| Have all findings from previous milestones been addressed? | Yes | Our latest runs of the CSIT has successfully passed for our repos: HAS: https://jenkins.onap.org/view/optf/job/optf-has-master-csit-has/457/ https://jenkins.onap.org/view/optf/job/optf-has-master-csit-has/458/ OSDF: https://jenkins.onap.org/view/optf/job/optf-osdf-master-csit-osdf/24/ https://jenkins.onap.org/view/optf/job/optf-osdf-master-csit-osdf/25/ | ||||||||||||||||||||||
| Development | Have all Defects of priority Highest and High been in status "Closed" in Jira? | No |
| |||||||||||||||||||||
| Are all JIRA issues used as a reference in a commit in status "Closed" in Jira? | Yes* | I believe our team has closed all issues as the changes get merged, but not sure how to search for JIRAs and commits together. | 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)? | Yes | https://jenkins.onap.org/view/optf/job/optf-has-master-conductor-merge-java/ https://jenkins.onap.org/view/optf/job/optf-osdf-master-osdf-merge-java/ https://jenkins.onap.org/view/optf/job/optf-cmso-master-cmso-merge-java/. This hasn't run yet for this new repo, but the corresponding verify job is running fine: https://jenkins.onap.org/view/optf/job/optf-cmso-master-cmso-verify-java/ | ||||||||||||||||||||||
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. | Yes | https://nexus.onap.org/content/repositories/releases/org/onap/optf/has/optf-has-conductor/1.2.2/ https://nexus.onap.org/content/repositories/releases/org/onap/optf/osdf/optf-osdf/1.2.2/ | Refer to Independent Versioning and Release Process for procedure | |||||||||||||||||||||
| Integration and Testing | Have all CSIT Use Cases (created by each project team) passed? | Yes | Our latest runs of the CSIT has successfully passed for our repos: https://jenkins.onap.org/view/optf/job/optf-has-master-csit-has/457/ https://jenkins.onap.org/view/optf/job/optf-osdf-master-csit-osdf/25/ | |||||||||||||||||||||
| At RC0, has the Pair Wise testing table been filled out? | Yes | OOF Pair Wise Testing for Casanblanca Casablanca Release | ||||||||||||||||||||||
| At RC0, have all OOM Release Healtcheck related to your project passed? | Yes | There are some timing related errors that happen very infrequently: Grafana stats below: Basic_OOF-Homing_Health_Check - 2 failures in the last 15 days. | ||||||||||||||||||||||
| At RC0, is there a Docker image in Nexus Docker-Release repo available for each repository? | ||||||||||||||||||||||||
| Has the project code successfully passed the Daily Build process? | Yes for 2/3 repos 1 new repo cmso is still WIP | https://jenkins.onap.org/view/optf/job/optf-has-master-conductor-release-version-java-daily/285/ https://jenkins.onap.org/view/optf/job/optf-osdf-master-osdf-release-version-java-daily/278/ Team is still working on fixing the daily jobs for our new repo cmso: https://jenkins.onap.org/view/optf/job/optf-cmso-master-cmso-release-version-java-daily/ | Goal is to ensure the latest project commit has not broken the Integration Daily Build | |||||||||||||||||||||
| Has the OOM deployment passed? | Yes | https://jenkins.onap.org/view/External%20Labs/job/lab-windriver-oom-daily/201/ [However, I did see some intermittent timeouts in some runs on the daily] https://jenkins.onap.org/view/External%20Labs/job/lab-windriver-oom-staging-daily/99/ | ||||||||||||||||||||||
Has the Heat deployment passed? (not a gating item for Casablanca) | Yes | https://jenkins.onap.org/view/External%20Labs/job/lab-windriver-heat-daily/164/ https://logs.onap.org/production/vex-yul-ecomp-jenkins-1/lab-windriver-heat-staging-daily/57/ | ||||||||||||||||||||||
| Documentation | For RC0, for project delivering binaries, has the team populated and validated all the sections of either the Platform Component or SDK template? | NA | 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? | NA | |||||||||||||||||||||||
For RC2, for project delivering binaries, has the team populated and validated all the sections of the Release Notestemplate? | NA | |||||||||||||||||||||||
| For RC2, has the Documentation Team provided the final approval for your project documentation? | NA |