...
| Practice Area | Checkpoint | Yes/No | Evidences | How to? | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product Management | Are all tasks associated with the release been marked as "Closed" in Jira? | Yes |
| |||||||||
| Have all findings from previous milestones been addressed? | No | Still one item, will be fixed in El Alto ( non critical )
| ||||||||||
| Development | Have all Defects of priority Highest and High been in status "Closed" in Jira? | Yes |
| |||||||||
| Are all JIRA issues used as a reference in a commit in status "Closed" 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. | No | https://gerrit.onap.org/r/#/q/project:externalapi/nbi+status:open+label:verified+-is:draft+-label:Code-Review%253D-1+AND+-label:Code-Review%253D-2++AND+is:mergeable+age:1week | Gerrit Query: status:open label:verified -is:draft -label:Code-Review=-1 AND -label:Code-Review=-2 AND is:mergeable age:1week | |||||||||
| Are all the Jenkins jobs successfully passed (verify + merge jobs)? | Yes | merge https://jenkins.onap.org/view/externalapi/job/externalapi-nbi-master-merge-java/ verify https://jenkins.onap.org/view/externalapi/job/externalapi-nbi-master-verify-java/ | https://jenkins.onap.org/view/Merge-Jobs/ | |||||||||
| Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | Yes | Unfortunately, we found that sonar was still running on casablanca branch, and by moving to master, with modified pom ( oparent inheritance, test strategy ) code coverage is broken with 0% while on casablanca it was 70%. 77% code coverage https://sonar.onap.org/component_measuresdashboard?id=org.onap.externalapi-nbi%3Anbi-rest-services&metric=coverage Here is the Jira issue
| Guidance on Code Coverage and Static Code Analysis Tools: Sonar | |||||||||
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 | 4.0.0 <dependency> | Refer to Independent Versioning and Release Process for procedure | |||||||||
| Check the certification expiry of your application. It should be valid for the next 9 months after RC0. | NA | No certificate ( TLS planned for El Alto ) | ||||||||||
| Integration and Testing | Have all CSIT Use Cases (created by each project team) passed? It should include at least 1 CSIT that will be run on Lab-xxx-OOM-Daily Jenkins Job | Yes | https://jenkins.onap.org/view/externalapi/job/externalapi-nbi-master-csit-healthcheck/ | |||||||||
| At RC0, has the Pair Wise testing table been filled out? | Yes | ExternalAPI Pair Wise Testing for Dublin Release | ||||||||||
| At RC0, have all OOM Release Healtcheck related to your project passed? | Yes | http://onapci.org/jenkins/job/windriver-release-daily/2/robot/ONAP%20CI/Health-Check/Basic%20External%20API%20NBI%20Health%20Check/ | ||||||||||
| At RC0, is there a Docker image in Nexus Docker-Release repo available for each repository? | Yes | 4.0.0 https://nexus3.onap.org/#browse/browse:docker.release:v2%2Fonap%2Fexternalapi%2Fnbi%2Ftags%2F4.0.0 | ||||||||||
| Has the project code successfully passed the Daily Build process? | Yes | https://jenkins.onap.org/view/externalapi/job/externalapi-nbi-master-docker-version-java-daily/ | 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. | ||||||||||
Has the project passed the Integration Sanity Tests? | Yes | Integration sanity tests in Dublin Release cover:
No test failure reported on http://onapci.org/grafana/d/8cGRqBOmz/daily-summary?orgId=1 No Integration Blocking Issue with no workaround: Dublin Release Integration Test Blocking Issues | ||||||||||
| Documentation | For RC0, does the project team has solved their JIRA Documentation Tickets? If not, what are the risks? | Yes | JIRA Query (Bugs Only) project = "Sandbox Project" AND project != "ONAP TSC" AND project != CI-Management AND (labels = Documentation OR project = Documentation) AND issuetype= Bug AND fixversion = "Dublin Release" AND status != Closed ORDER BY issuetype DESC, fixVersion ASC, status DESC, priority DESC, updated DESC | |||||||||
| For RC1, has the team addressed all the remaining Documentation JIRA tickets ? | Yes | JIRA Query project != "Sandbox Project" AND project != "ONAP TSC" AND project != CI-Management AND (labels=Documentation OR project=Documentation) AND status != Closed ORDER BY fixVersion ASC, status DESC, priority DESC, updated DESC | ||||||||||
| For RC1, is the project prepared for the upcoming 'Ready to review'? | Yes | Documentation related patches should be reviewed by the documentation team to make sure everyone follows style guides. | ||||||||||
| For RC2, has the team addressed all the remaining Documentation JIRA tickets identified during the review? | NA | JIRA Query project != "Sandbox Project" AND project != "ONAP TSC" AND project != CI-Management AND (labels=Documentation OR project=Documentation) AND status != Closed ORDER BY fixVersion ASC, status DESC, priority DESC, updated DESC |
...