AAF R2 Beijing Release - Release Sign-Off Milestone Checklist
- Sai Gandham
Practice Area | Checkpoint | Yes/No | Evidences | How to? |
|---|---|---|---|---|
Product Management | Are committed Product Backlog Stories been coded and marked as "Done" in Jira? | Yes | Getting issues... | |
Are all tasks associated with committed Product Backlog Stories been marked as "Done" in Jira? | Yes | Getting issues... | ||
Provide the project features list under the form of a bulleted list. |
| |||
Summarize any functionalities that were planned at Release planning and not delivered at Release Sign-Off | ||||
Release Management | Have all issues pertaining to FOSS been addressed? | Yes | ||
Have all findings from previous milestones been addressed? | N/A | Provide link to JIRA findings | ||
Development | Are all the Jenkins jobs successfully passed (verify + merge jobs)? | Yes | https://jenkins.onap.org/view/aaf/job/aaf-authz-master-verify-java/ https://jenkins.onap.org/view/aaf/job/aaf-authz-master-release-version-java-daily/ https://jenkins.onap.org/view/aaf/job/aaf-authz-master-merge-java/ https://jenkins.onap.org/view/aaf/job/aaf-authz-master-docker-java-shell-daily/ https://jenkins.onap.org/view/aaf/job/aaf-authz-maven-clm-master/ | |
Are all binaries available in Nexus Release repository? | Yes | https://nexus.onap.org/#nexus-search;quick~org.onap.aaf.authz ( Latest version : 2.1.1 ) | ||
Are all Docker images available In Nexus? | Yes | https://nexus3.onap.org/#browse/search=keyword%3Daaf ( Latest version : 2.1.1 ) | ||
Are the Java and Docker manifest updated with the same version as in Nexus Release repository? | Yes.Created a ticket to move the docker image to the Nexus Release repository | ( Latest version : 2.1.1 ) | ||
Integration and Testing | Have all CSIT Use Cases (created by each project team) passed? | Yes | https://jenkins.onap.org/view/aaf/job/aaf-master-verify-csit-aafapi/ https://jenkins.onap.org/view/aaf/job/aaf-master-verify-csit-sms-test-plan/ | Goal is to incease our confidence the latest commit did not break the major functionality. Jenkins CSIT Jobs |
Has the project code successfully passed the Daily Build process? | Yes | https://jenkins.onap.org/view/Daily-Jobs/job/aaf-authz-master-release-version-java-daily/ https://jenkins.onap.org/view/Daily-Jobs/job/aaf-authz-master-docker-java-shell-daily/ https://jenkins.onap.org/view/Daily-Jobs/job/aaf-sms-master-aaf-sms-client-release-java-daily/ https://jenkins.onap.org/view/Daily-Jobs/job/aaf-sms-master-docker-golang-shell-daily/ | Goal is to ensure the latest project commit has not broken the Integration Daily Build | |
Has the project done the integration testing with related dependent projects? | Yes | |||
Documentation | Has your team contributed and completed work in the following documentations in ReadTheDocs:
| Yes | Provide Link to ReadTheDocs Release Notes http://onap.readthedocs.io/en/latest/submodules/aaf/authz.git/docs/index.html?highlight=aaf https://onap.readthedocs.io/en/beijing/submodules/aaf/authz.git/docs/sections/release-notes.html |