...
RC Release Candidate Milestone overview is available in wiki.
in edit 20181101
| Practice Area | Checkpoint | Yes/No | Evidences | How to? | |||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product Management | Are all tasks associated with the release been marked as "Closed" in Jira? | Yes | Link to JIRA https://jira.onap.org/secure/RapidBoard.jspa?rapidView=53&view=planning&selectedIssue=LOG-146 | ||||||||||||||||||||||||||||||
| Have all findings from previous milestones been addressed? | Yes | Provide link to JIRA findings | |||||||||||||||||||||||||||||||
| Development | Have all Defects of priority Highest and High been in status "Closed" in Jira? | Yes | Provide link to JIRA issue (type bug) of priority Highest and High. | new SO JIRA for filebeat - helping SO team
| |||||||||||||||||||||||||||||
| Are all JIRA issues used as a reference in a commit in status "Closed" in Jira? | Yes | Note about the reverse - there are JIRAs in other projects that are closed but the code is still in review (not submitted) - internal poc worked but ONAP is not finished | 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 | Provide link to "Merge job" as evidence in Jenkins project tab all merge, docker, verify jobs passing | 20181010 update: 1 pomba job pending - waiting on dependency wait for SDNC/apps to be released 20181009 3 pomba release jobs pending https://jenkins.onap.org/view/logging-analytics/ status 20181009:1300EDT - will reupdate wed wait for SDNC/apps to be released in progress (fixing license issue first) working | ||||||||||||||||||||||||||||||
Has the team delivered all their release artifacts in Nexus Release repo? There should be at least ONE version of each artifacts available in Nexus Release repo. | Yes (minus 1 dependency) | 20181010 update - all remaining except the 1 job waiting on an SDNC dependency are released (The last 2 are in an LF mail to release last night) 20181009 a couple pomba 1.3 left due to aai/validation and sdnc dependencies that need to be released details on /wiki/spaces/SV/pages/16089191 logging jars/wars are released as 1.2.2 verifying https://git.onap.org/integration/tree/version-manifest/src/main/resources 20181107 update - all artifacts slated for casablanca are released | Refer to Independent Versioning and Release Process for procedure | ||||||||||||||||||||||||||||||
| Integration and Testing | Have all CSIT Use Cases (created by each project team) passed? | No | Provide link to evidence. As things are moving fast, we want to ensure CSIT are still "green". See use cases essentially the pairwise testing is csit - since no library is exported -
| ||||||||||||||||||||||||||||||
| At RC0, has the Pair Wise testing table been filled out? | PartialYes | Casablanca Pair Wise Testing master page see attached results in
| working with SO under SO-1110 | ||||||||||||||||||||||||||||||
| At RC0, have all OOM Release Healtcheck related to your project passed? | Yes | 20181011 20181107: 1900 status - OK http://jenkins.onap.info/job/oom-cd-master/ http://jenkins.onap.info/job/oom-cd-master/3704/console 16:27:12
| |||||||||||||||||||||||||||||||
| At RC0, is there a Docker image in Nexus Docker-Release repo available for each repository? | Yes | Provide link to evidence pomba logging-analytics (no dockers) | |||||||||||||||||||||||||||||||
| Has the project code successfully passed the Daily Build process? | Yesexcept for the release/docker jobs pending release | see all blue yellow https://jenkins.onap.org/view/logging-analytics/ | Goal is to ensure the latest project commit has not broken the Integration Daily Build | ||||||||||||||||||||||||||||||
| Has the OOM deployment passed? | Yes | Ensure in Jenkins External Labs all Health Check pass. yes see hourly build in http://jenkins.onap.info/job/oom-cd-master/36414399/console and http://kibana.onap.info:5601/app/kibana#/dashboard/AWAtvpS63NTXK5mX2kuS | |||||||||||||||||||||||||||||||
Has the Heat deployment passed? (not a gating item for Casablanca) | N/A | Ensure in Jenkins External Labs all Health Check pass. pomba, clamp and logging are not in heat | |||||||||||||||||||||||||||||||
| 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 | /wiki/spaces/SV/pages/16089191 spring 4.x is insecure - first version that is ok is 5.0.5 - issue is it requires a retrofit of all my libraries including jax-rs 5.0.5 https://gerrit.onap.org/r/#/c/70161/1 - increased 4,2 to 8,5 5.0.9 https://gerrit.onap.org/r/#/c/70188/ decreased 8,5 to 7,3 | 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? | yes |
| |||||||||||||||||||||||||||||||
For RC2, for project delivering binaries, has the team populated and validated all the sections of the Release Notestemplate? | yes | see logging and pomba https://git.onap.org/logging-analytics/tree/docs/release-notes.rst | |||||||||||||||||||||||||||||||
| For RC2, has the Documentation Team provided the final approval for your project documentation? | yes | Doc team code reviewed |