...
| Info | ||
|---|---|---|
| ||
|
| Practice Area | Checkpoint | Yes/No | Evidences | How to? |
|---|---|---|---|---|
| Product Management | Are all tasks associated with the release been marked as "Done" in Jira? |
| No | Search for: project = "ONAP Operations Manager" AND fixVersion = 10341 AND NOT type = Epic AND NOT type = Bug AND status != Closed AND status != Done AND status != Delivered Remaining work:
| |||
| 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 "Done" in Jira? |
| No |
| ||||||||||
| 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. | Yes | https://gerrit.onap.org/r/#/q/project:oom+and+status:open+and+age:36h Finishing the addition of license headers is still open due to merge conflicts. | |||||||||
| Are all the Jenkins jobs successfully passed (verify + merge jobs)? | N/A | Provide link to "Merge job" as evidence in Jenkins project tab | |||||||||
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. | Still waiting on the LF  | Refer to Independent Versioning and Release Process for procedure | |||||||||
| Integration and Testing | Have all CSIT Use Cases (created by each project team) passed? | N/A | Provide link to evidence. As things are moving fast, we want to ensure CSIT are still "green". | ||||||||
| Is there a Docker images available for each repository? | N/A | Provide link to evidence | |||||||||
| Has the project code successfully passed the Daily Build process? | Beijing CD System is here and here | Goal is to ensure the latest project commit has not broken the Integration Daily Build | |||||||||
| Has the OOM deployment passed? | Ensure in Jenkins External Labs all Health Check pass. DCAE and Ext API are reporting fails but DCAE is working some times so this could be a CD system problem. Ext API charts are still being worked. | ||||||||||
| Has the Heat deployment passed? | 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? | 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? | The OOM Documentation is here: http://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_project_description.html There are four documents including a User Guide. There is an open JIRA story for documentation: | ||||||||||
For RC2, for project delivering binaries, has the team populated and validated all the sections of the Release Notestemplate? | Gildas, although OOM is not delivering binaries we have a lot of content for this release. Here is a link to the JIRA release notes: https://jira.onap.org/secure/ReleaseNote.jspa?projectId=10301&version=10341 . | ||||||||||
| For RC2, has the Documentation Team provided the final approval for your project documentation? | I've been working with the documentation team on OOM documentation. There of the OOM docs are linked off the top level onap.readthedocs.io under 'Platform Operations' |
