AAF R2 Beijing Release - RC2 Checklist

Product Management

Are all tasks associated with the release been marked as "Done" in Jira?

Yes

Have all findings from previous milestones been addressed?

NA

Paiwise testing is in progress.

Development

Have all Defects of priority Highest and High been in status "Done" in Jira?

Yes

Are all JIRA issues used as a reference in a commit in status "Done" 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.

Yes

https://gerrit.onap.org/r/#/c/33049/

Waiver for non critical commits need not be committed for the release

Are all the Jenkins jobs successfully passed (verify + merge jobs)?

Yes

https://jenkins.onap.org/view/aaf/job/aaf-authz-master-merge-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-verify-java/

https://jenkins.onap.org/view/aaf/job/aaf-sms-master-merge-golang/

https://jenkins.onap.org/view/aaf/job/aaf-sms-master-verify-golang/

Has the team delivered all their release artifacts in Nexus Release or Nexus Staging repo?

There should be at least ONE version of each artifacts available in Nexus Release or Nexus Staging repo.

Yes

https://nexus.onap.org/#nexus-search;quick~org.onap.aaf.authz

Refer to Independent Versioning and Release Process for procedure

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-sms-test-plan/

https://jenkins.onap.org/view/aaf/job/aaf-master-csit-sms-test-plan/

https://jenkins.onap.org/view/aaf/job/aaf-master-verify-csit-aafapi/

Is there a Docker images available for each repository?

Yes

https://nexus3.onap.org/#browse/search=keyword%3Daaf

Has the project code successfully passed the Daily Build process?

Yes

https://jenkins.onap.org/view/Daily-Jobs/job/aaf-authz-master-docker-java-shell-daily/

https://jenkins.onap.org/view/Daily-Jobs/job/aaf-authz-master-release-version-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 OOM deployment passed?

Yes

https://jenkins.onap.org/view/External%20Labs/job/lab-windriver-beijing-oom-deploy/

Has the Heat deployment passed?

Yes

https://jenkins.onap.org/view/External%20Labs/job/lab-tlab-beijing-heat-deploy/

Documentation

For RC0, for project delivering binaries, has the team populated and validated all the sections of either the Platform Component or SDK template?

Yes

http://onap.readthedocs.io/en/latest/submodules/aaf/authz.git/docs/index.html?highlight=aaf

Bootstrapping AAF Components

Client Access to AAF

Most teams have already created the high level file structures in readthedocs, and populated some actual documentation. However, the remaining sections of the appropriate teamplate must be completed.

Platform: A&AI, APP-C, CLAMP, CLI, DCAE, DMaaP, Holmes, MSB, OOM, Policy, Portal, SDN-C SDC, SO, UseCase UI, VFC, VID

SDKs: AAF, CCSDK, External API Framework, Multi VIM/Cloud, VNFSDK

For RC1, has the team addressed any issue (recorded in JIRA) provided by the Documentation team?

NA

No issues Reported

For RC2, for project delivering binaries, has the team populated and validated all the sections of the Release Notes template?

NA

Documentation available in Read the docs, No issues reported by the Documentation team

Documentation provided on wiki

Bootstrapping AAF Components

Client Access to AAF

No Issue raised

For RC2, has the Documentation Team provided the final approval for your project documentation?

Yes

No issues reported by the Documentation team

No Objection or issue raised by the doc team.