DRAFT PROPOSAL FOR COMMENTS
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.
Usage
- Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki.
- Fill out the Yes/No column
- Provide link to evidence (when necessary)
| 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... marked Done Getting issues... pending, but are tasks associated with S3P or integration testing | |
| Have all findings from previous milestones been addressed? | No | One of our CSIT job is still failing | ||
| Development | Have all Defects of priority Highest and High been in status "Done" in Jira? | Yes | Getting issues... marked Done | |
| Are all JIRA issues used as a reference in a commit in status "Done" in Jira? | Yes | We believe our team has marked tasks as Done when the commit is made - not sure how to verify this though. | ||
| 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-osdf-master-osdf-verify-java/ https://jenkins.onap.org/view/optf/job/optf-osdf-master-osdf-verify-python/ https://jenkins.onap.org/view/optf/job/optf-has-master-conductor-verify-java/ https://jenkins.onap.org/view/optf/job/optf-has-master-conductor-verify-python/ https://jenkins.onap.org/view/optf/job/optf-osdf-master-osdf-merge-java/ https://jenkins.onap.org/view/optf/job/optf-has-master-conductor-merge-java/ | ||
Has the team delivered all their release artifacts in Nexus Release or Nexus Staging repo? There should be at least ONE version of each artifacts available in Nexus Release or Nexus Staging repo. | Yes | Staging repo: https://nexus.onap.org/content/repositories/staging/org/onap/optf/ | Refer to Independent Versioning and Release Process for procedure | |
| Integration and Testing | Have all CSIT Use Cases (created by each project team) passed? | No | Passing: https://jenkins.onap.org/view/optf/job/optf-has-master-csit-has/ https://jenkins.onap.org/view/optf/job/optf-has-master-verify-csit-has/ Failing: https://jenkins.onap.org/view/optf/job/optf-osdf-master-csit-osdf/ | |
| Is there a Docker images available for each repository? | Yes | |||
| Has the project code successfully passed the Daily Build process? | Yes* | Two of our release jobs have failed yesterday, but was successful before then. Our team is working on identifying the issue here. https://jenkins.onap.org/view/optf/job/optf-has-master-conductor-docker-java-version-shell-daily/ https://jenkins.onap.org/view/optf/job/optf-osdf-master-osdf-docker-java-version-shell-daily/ https://jenkins.onap.org/view/optf/job/optf-has-master-conductor-release-version-java-daily/ https://jenkins.onap.org/view/optf/job/optf-osdf-master-osdf-release-version-java-daily/ | Goal is to ensure the latest project commit has not broken the Integration Daily Build | |
| Has the OOM deployment passed? | No | Pending review from OOM team. Our team committed the changes for review on 04/08. | ||
| Has the Heat deployment passed? | No | Our team is currently working with the Integration team (Marco Platania). | ||
| 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 | We have the file structures in readthedocs and have been populating content in it (https://onap.readthedocs.io/en/latest/submodules/optf/has.git/docs/index.html). We also have the the required content in the Wiki (architecture, API, Deployment instruction etc). Our team is working on converting our existing documentation into the required format as a part of the S3P usability user story: OPTFRA-41 - Getting issue details... STATUS . We plan to make progress on this and get it ready by RC1. | 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 |