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.
| Practice Area | Checkpoint | Yes/No | Evidences | How to? |
|---|---|---|---|---|
| Product Management | Are all tasks associated with the release been marked as "Closed" in Jira? | Yes |
| Jira query: project=CLAMP AND issuetype!= Bug AND fixVersion ="Dublin Release" AND status != Closed ORDER BY fixVersion ASC, status DESC, priority DESC, updated |
| Have all findings from previous milestones been addressed? | Yes | No findings | ||
| Development | Have all Defects of priority Highest and High been in status "Closed" in Jira? | Yes |
| Jira query: project=CLAMP and (priority="High" or priority="Highest") AND issuetype= Bug AND fixVersion ="Dublin Release" AND status != Closed ORDER BY fixVersion ASC, status DESC, priority DESC, updated |
| 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 | 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 | Jenkins project tab | 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 | Goal: 55% for Incubation project in the current release CLAMP is at more than 65% | 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 | Nexus project folder | 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. | Yes | |||
| 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 | but we didn't have time to integrate to OOM Lab test (see risk raised on this topic on the Dublin risk page) | |
| At RC1, has the Pair Wise testing table been filled out? | Yes | Dublin Pair Wise Testing master page | ||
| At RC1, have all OOM Release Healtcheck related to your project passed? | Yes | |||
| At RC1, is there a Docker image in Nexus Docker-Release repo available for each repository? | Yes | Nexus project folder | ||
| Has the project code successfully passed the Daily Build process? | Yes | Jenkins project tab | 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 RC1, has the team addressed all the remaining Documentation JIRA tickets ? | Yes | bugs:
| JIRA Query ((labels=Documentation AND project=CLAMP) OR (labels=CLAMP AND project=Documentation)) AND fixVersion ="Dublin Release" AND status != Closed ORDER BY fixVersion ASC, status DESC, priority DESC, updated DESC Jira Query (Bugs Only) ((labels=Documentation AND project=CLAMP) OR (labels=CLAMP AND 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, 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. |