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 | ||
| Have all findings from previous milestones been addressed? | N/A | |||
| 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 | Dublin Closed Issues | 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 | https://jenkins.onap.org/view/aaf/ | 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) | No. | 42.5% (up from previous 40.4% RC1) Goal: Improvement, with Happy Path being 55% in the current release... HOWEVER: We stated at the beginning of Dublin that we did not have enough resources to make this goal, and did best effort (assigned 1/2 of our resources) | Guidance on Code Coverage and Static Code Analysis There were not enough resources or time to complete 55% for Dublin. However, we improved by about 7.5%... 42.5% | |
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 | https://nexus.onap.org/#nexus-search;quick~org.onap.aaf.authz https://nexus.onap.org/content/repositories/releases/org/onap/aaf/authz/ | 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 | https://jenkins.onap.org/view/aaf/ | ||
| 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/CSIT/ | |
| At RC2, has the Pair Wise testing table been filled out? | Yes | Integration Weather Board for Dublin Release | ||
| At RC2, have all OOM Release Healtcheck related to your project passed? | Yes | See OOM Approval Note , 5/1 | ||
| At RC2, 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 RC0, does the project team has solved their JIRA Documentation Tickets? If not, what are the risks? | Yes | https://onap.readthedocs.io/en/latest/submodules/aaf/authz.git/docs/index.html https://onap.readthedocs.io/en/latest/submodules/aaf/authz.git/docs/sections/release-notes.html https://onap.readthedocs.io/en/latest/submodules/aaf/sms.git/docs/index.html
| |
| For RC1, has the team addressed all the remaining Documentation JIRA tickets ? | Yes | https://onap.readthedocs.io/en/latest/submodules/aaf/authz.git/docs/index.html https://onap.readthedocs.io/en/latest/submodules/aaf/authz.git/docs/sections/release-notes.html https://onap.readthedocs.io/en/latest/submodules/aaf/sms.git/docs/index.html
| ||
| For RC1, is the project prepared for the upcoming 'Ready to review'? | Yes | https://onap.readthedocs.io/en/latest/submodules/aaf/authz.git/docs/index.html https://onap.readthedocs.io/en/latest/submodules/aaf/authz.git/docs/sections/release-notes.html https://onap.readthedocs.io/en/latest/submodules/aaf/sms.git/docs/index.html
| ||
For RC2, does the project team has solved their JIRA Documentation Tickets? If not, what are the risks? | Yes | https://onap.readthedocs.io/en/latest/submodules/aaf/authz.git/docs/index.html https://onap.readthedocs.io/en/latest/submodules/aaf/authz.git/docs/sections/release-notes.html https://onap.readthedocs.io/en/latest/submodules/aaf/sms.git/docs/index.html
|