The following items are expected to be completed for the project to Pass the Release Candidate Milestone.
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? | yes | Getting issues... | |
| Release Management | (For RC0 only) As the project team identified the reduced set of Committers who will proceed with Code Merge after RC0? | Provide the name of committers. Recommendation is 3 committers max per project (1 per geographic area)? | ||
| Have all findings from previous milestones been addressed? | yes | M2,3,4 links | ||
| Development | Have all Defects of priority Highest and High been in status "Done" in Jira? | yes | Getting issues... | |
| 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 request older than 24 hours in Gerrit? | no | |||
| Are all the Jenkins jobs successfully passed (verify + merge jobs)? | yes | https://jenkins.onap.org/view/portal/ | ||
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 | https://nexus.onap.org/#nexus-search;quick~portal/sdk | 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/portal/job/portal-master-verify-csit-testsuite/ | |
| Have all end-to-end CSIT (created by Integration Team) been identified (for RC0) and passed (for RC1)? | Provide link to evidence | |||
| Is there a Docker images available for each repository? | yes | https://nexus3.onap.org/repository/docker.snapshot/v2/onap/portal-apps/manifests/1.3-STAGING-latest https://nexus3.onap.org/repository/docker.snapshot/v2/onap/portal-db/manifests/1.3-STAGING-latest https://nexus3.onap.org/repository/docker.snapshot/v2/onap/portal-wms/manifests/1.3-STAGING-latest | ||
| Has the project code successfully passed the Daily Build process? | yes | https://jenkins.onap.org/view/portal/job/portal-master-release-version-java-daily/ | 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 | Greg from documentation team verified and looks good. http://onap.readthedocs.io/en/latest/submodules/portal.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? | NA | |||
| For RC2, for project delivering binaries, has the team populated and validated all the sections of the Release Notestemplate? | ||||
| For RC2, has the Documentation Team provided the final approval for your project documentation? |