...
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 |
| |||||||||||
| Have all findings from previous milestones been addressed? | No | Still working M4 code coverage on aai-sparky-be | Jira Legacy | | |||||||||||
| server | System Jira | |||||||||||||
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution | |||||||||||||
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 | key | AAI-429Yes||||||||||||
| 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? | No | There have been multiple commits on this story, still working to get sparky-be to 30% code coverage (at 21.8%)
| Some commits are pending that are blocked by the documentation project | 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/Merge-Jobs/ | ||||||||||||
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 | ESR is pending commit on producing the STAGING artifact | 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/CSIT/ | |||||||||||
| Is there a Docker images available for each repository? | Yes | https://nexus.onap.org:10001/ | ||||||||||||
| Has the project code successfully passed the Daily Build process? | Yes | https://jenkins.onap.org/view/aai/ | 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? | In progress | Gerit doc repo . We have converted our wiki documentation to rst format. We are working to get it to appear on readthedocs. We are also working to convert our swagger documentation for the API from html format. | 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? | ||||||||||||||
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? |