Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Practice AreaCheckpointYes/NoEvidencesHow to?
Product ManagementAre all tasks associated with the release been marked as "Done" in Jira?YesNo

Jira Legacy
serverSystem Jira
jqlQueryproject = POLICY AND issuetype = Sub-task AND status = Closed AND fixVersion = "Beijing Release"
counttrue
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
- Closed Tasks

Jira Legacy
serverSystem Jira
jqlQueryproject = POLICY AND issuetype = Sub-task AND status != Closed AND fixVersion = "Beijing Release"
counttrue
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
- Sanity check for Open Tasks

The remaining tasks are for documentation and release planning purposes.




Have all findings from previous milestones been addressed?N/AProvide link to JIRA findings
DevelopmentHave all Defects of priority Highest and High been in status "Done" in Jira?No

Jira Legacy
serverSystem Jira
jqlQueryproject="Policy" and issueType="Bug" and fixVersion="Beijing Release" and Status != "Closed" AND Priority in (High, Highest)
counttrue
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
(should be zero)




Are all JIRA issues used as a reference in a commit in status "Done" in Jira?

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

Are all the Jenkins jobs successfully passed (verify + merge jobs)?No - policy engine WIPYes

https://jenkins.onap.org/view/policy/job/policy-common-master-merge-java/

https://jenkins.onap.org/view/policy/job/policy-drools-applications-master-merge-java/

https://jenkins.onap.org/view/policy/job/policy-engine-master-merge-java/

https://jenkins.onap.org/view/policy/job/policy-drools-pdp-master-merge-java/


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.

YesWe have released 1.2.0 (We are hoping to release 1.2.1 ASAP)Refer to Independent Versioning and Release Process for procedure
Integration and TestingHave all CSIT Use Cases (created by each project team) passed?Yes

https://jenkins.onap.org/view/policy/job/policy-master-csit-health/


Is there a Docker images available for each repository?Yes

https://nexus3.onap.org/#browse/browse:docker.release:v2%2Fonap%2Fpolicy-drools%2Fmanifests%2F1.2.0

https://nexus3.onap.org/#browse/browse:docker.release:v2%2Fonap%2Fpolicy-pe%2Fmanifests%2F1.2.0

We are hoping to release 1.2.1 ASAP



Has the project code successfully passed the Daily Build process?No - engine is having some JUnit intermittent issues. We are actively working on this.Yes

https://jenkins.onap.org/view/policy/job/policy-common-master-release-version-java-daily/

https://jenkins.onap.org/view/policy/job/policy-drools-pdp-master-docker-java-version-shell-daily/

https://jenkins.onap.org/view/policy/job/policy-drools-applications-master-release-version-java-daily/

https://jenkins.onap.org/view/policy/job/policy-engine-master-docker-java-version-shell-daily/



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 Heat deployment passed?YesEnsure in Jenkins External Labs all Health Check pass.
Documentation

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


N/A

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?

Yes

Documentation team provided no JIRA's for us. We communicated via email and made fixes that were identified.

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


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

N/A

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