...
This template must be filled out for every Release Candidate Milestone (RC0, 1, 2, x)
RC Release Candidate Milestone overview is available in wiki.
| Practice Area | Checkpoint | Yes/No | Evidences | How to? | |||||
|---|---|---|---|---|---|---|---|---|---|
| Product Management | Are all tasks associated with the release been marked as "Done" in Jira? | No - In Progress |
|
|
Pamela Dragosh
Jorge Hernandez-Herrero
- These are all the Tasks marked as Closed and Resolved
| |||||||||||
| Have all findings from previous milestones been addressed? | Yes |
| Development | Have all Defects of priority Highest and High been in status "Done" in Jira? | Yes |
|
| |||||||
| Are all JIRA issues used as a reference in a commit in status "Done" 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 | https://gerrit.onap.org/r/#/q/status:open+projects:policy | |
| Are all the Jenkins jobs successfully passed (verify + merge jobs)? | Yes |
https://jenkins.onap.org/view/policy/job/policy-common-master-verify-java/ https://jenkins.onap.org/view/policy/job/policy-common-master-merge-java/ https://jenkins.onap.org/view/policy/job/policy-drools-applications-master-verify-java/ https://jenkins.onap.org/view/policy/job/policy-drools-applications-master-merge-java/ https://jenkins.onap.org/view/policy/job/policy-engine-master-verify-java/ https://jenkins.onap.org/view/policy/job/policy-engine-master-merge-java/ https://jenkins.onap.org/view/policy/job/policy-drools-pdp-master-verify-java/ https://jenkins.onap.org/view/policy/job/policy-drools-pdp-master-merge-java/ | |||
Has the team delivered all their release artifacts in Nexus Releases repo? There should be at least ONE version of each artifacts available in Nexus Releases repo. | Yes | Staging artifacts were available. | Refer to Independent Versioning and Release Process for procedure |
| Integration and Testing | Have all CSIT Use Cases (created by each project team) passed? |
| Yes | https://jenkins.onap.org/view/policy/job/policy-master-csit-health/ | |
| Is there a Docker images available for each repository? | Yes |
| Docker staging images were available. | ||||
| 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 | ||
| Documentation | For RC0, for project delivering binaries, has the team populated and validated all the sections of either the Platform Component or SDK template? | Yes | There are only a subset of the suggested Platform Component list that are applicable to policy: http://onap.readthedocs.io/en/latest/submodules/policy/engine.git/docs/index.html | 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 |