Versions Compared

Version Old Version 2 New Version Current
Changes made by

Pamela Dragosh

Pamela Dragosh

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Clarification from Gildas at PTL meeting

...

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 AreaCheckpointYes/NoEvidencesHow to?
Product ManagementAre all tasks associated with the release been marked as "Done" in Jira?
Link to JiraRelease Management(For RC0 only) As the project team identified the reduced set of Committers who will proceed with Code Merge after RC0?Provide the name of committers. Recommendation is 3 committers max per project (1 per geographic area)?
No - In Progress

Jira Legacy
serverSystem Jira
jqlQueryproject="Policy" and issueType="Task" and fixVersion="Amsterdam Release" and status="Closed" and resolution!="Unresolved"
counttrue
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
- These are all the Tasks marked as Closed and Resolved

Jira Legacy
serverSystem Jira
jqlQueryproject="Policy" and issueType="Task" and fixVersion="Amsterdam Release" and (status!="Closed" or resolution="Unresolved")
counttrue
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
- These are all the Tasks marked as NOT Closed or Unresolved

  • We have closed by EOB Wednesday  most tasks that we were doing for RC0
  • We still have open tasks related to integration testing that is currently still happening.


Have all findings from previous milestones been addressed?
Provide link to JIRA findings
Yes

DevelopmentHave all Defects of priority Highest and High been in status "Done" in Jira?
Provide link to JIRA issue (type bug) of priority Highest and High. 
Yes

Jira Legacy
serverSystem Jira
jqlQueryproject="Policy" and issueType="Bug" and fixVersion="Amsterdam Release" and priority in ("Highest", "High") and Resolution != "Unresolved" and Status = "Closed"
counttrue
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
- These are all the bugs of highest/high priority that are marked as Closed and Resolved

Jira Legacy
serverSystem Jira
jqlQueryproject="Policy" and issueType="Bug" and fixVersion="Amsterdam Release" and priority in ("Highest", "High") and ( Resolution = "Unresolved" or Status != "Closed")
counttrue
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
- These are all the bugs of highest/high priority that are NOT marked as Closed or Unresolved

  • This bug is APPC - will verify it and close it 10-11-2017



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
request 
related to Highest and High priority issues older than
24
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.Nohttps://gerrit.onap.org/r/#/q/status:open+projects:policy
Are all the Jenkins jobs successfully passed (verify + merge jobs)?
Provide link to "Merge job" as evidence in Jenkins project tabProvide link to evidence
Yes

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

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

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

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

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

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

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

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


Has the team delivered all their release artifacts in Nexus Releases repo?

There should be at least ONE version of each artifacts available in Nexus Releases repo.

YesStaging artifacts were available.Refer to Independent Versioning and Release Process for procedure
Integration and TestingHave all CSIT Use Cases (created by each project team) passed?
Provide link to evidencHave all end-to-end CSIT (created by Integration Team) been identified (for RC0) and passed (for RC1)?
Yeshttps://jenkins.onap.org/view/policy/job/policy-master-csit-health/
Is there a Docker images available for each repository?
Provide link to evidence
YesDocker staging images were available.
Has the project code successfully passed the Daily Build process?Yes
Goal is to ensure the latest project commit has not broken the Integration Daily Build 
Documentation

For RC0, for project delivering binaries, has the team populated and validated all the sections

in the Documentation template? These information must be useful for installation, configuration, and usage.

of either the Platform Component or SDK template?


Yes

There are only a subset of the suggested Platform Component list that are applicable to policy:

http://onap.readthedocs.io/en/latest/submodules/policy/engine.git/docs/index.html


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
to
any issue (recorded in JIRA) provided by the Documentation team?n/a

For RC2,
have all remaining issues been addressed?
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?
Documentation Team is using ReadTheDocs for documenting user facing documentation.
n/a