Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Practice AreaCheckpointYes/NoEvidencesHow to?
Product ManagementAre committed Product Backlog Stories been coded and marked as "Done" in Jira?Yes

Sprint View

Jira Legacy
serverSystem Jira
jqlQueryproject = AAF AND issuetype = Story AND fixVersion = "Beijing Release" AND status = "done"
counttrue
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176


Are all tasks associated with committed Product Backlog Stories been marked as "Done" in Jira?Yes

Jira Legacy
serverSystem Jira
jqlQueryproject = AAF AND issuetype = task AND fixVersion = "Beijing Release" AND status = "done"
counttrue
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176


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 ManagementHave all issues pertaining to FOSS been addressed?Yes

Have all findings from previous milestones been addressed?N/AProvide link to JIRA findings
DevelopmentAre 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?Yeshttps://nexus.onap.org/#nexus-search;quick~org.onap.aaf.authz ( Latest version : 2.1.1 )
Are all Docker images available In Nexus?Yeshttps://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

https://git.onap.org/integration/tree/version-manifest/src/main/resources/docker-manifest.csv?h=beijing

( 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?

YesAAF Pair Wise Testing for Beijing Release
Documentation

Has your team contributed and completed work in the following documentations in ReadTheDocs:

  1. Release Notes
  2. Project Documentation
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