Versions Compared

Key

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

The following items are expected to be completed for the project to Pass the M4 Code Freeze Milestone.

M4 Release Code Freeze Milestone overview is available in wiki.


Practice AreaCheckpointYes/NoEvidencesHow to?

By using the macro JIRA Issue/Filter, provide a link to JIRA in listing the stories that are implemented in Amsterdam Release. (Example 86 issues for AAI project, edit for your project)

For each JIRA story that are implemented in Amsterdam Release, you have to setup in JIRA the JIRA fixVersion="Amsterdam Release"In ProgressYes

By using the macro JIRA Issue/Filter, provide a link to JIRA in listing the stories that are implemented in Amsterdam Release. (Example 86 issues for AAI project, edit for your project)


Jira Legacy
serverSystem Jira
jqlQueryproject="Policy" and issueType="Story" and fixVersion="Amsterdam Release"
counttrue
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176


For each JIRA story that are implemented in Amsterdam Release, you have to setup in JIRA the JIRA fixVersion="Amsterdam Release"
List the Stories that will not be implemented in this current Release.In ProgressYes

By using the macro JIRA Issue/Filter, provide a link to JIRA in listing the stories that are NOT implemented in Amsterdam Release. (Example 3 issues for AAI project, edit for your project)

Jira Legacy
serverSystem Jira
jqlQueryproject="Policy" and issueType="Story" and fixVersion="Beijing Release"
counttrue
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176


For each JIRA story that will not be implemented in Amsterdam Release, you have to setup in JIRA the JIRA fixVersion="Beijing Release"

Are committed Sprint Backlog Stories been coded and marked as "Done" in Jira?Yes

https://jira.onap.org/secure/RapidBoard.jspa?projectKey=POLICY&rapidView=15&view=planning



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

Release ManagementHave all issues pertaining to FOSS been addressed?Yes

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPOLICY-218


Have all findings from previous milestones been addressed?In Progress

Yes

All blockers were removed from Policy Team. I don't have any JIRA's associated with them.

Code Coverage is >30% in all projects:

https://sonar.onap.org/overview/coverage?id=org.onap.policy.common%3Acommon-modules

https://sonar.onap.org/overview/coverage?id=org.onap.policy.drools-applications%3Adrools-pdp-apps

https://sonar.onap.org/overview/coverage?id=org.onap.policy.drools-pdp%3Adrools-pdp

https://sonar.onap.org/overview/coverage?id=org.onap.policy.engine%3APolicyEngineSuite

*TODO functional testsFunctional Tests:

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

For M2 and M3 Milestones, ensure all findings have been closed.
DevelopmentAre all Defects of priority Highest and High in status "Done" in Jira?Provide link to JIRA issue (type bug) of priority Highest and High. Yes

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject="Policy" and issueType="Bug" and fixVersion="Amsterdam Release" and Status != "Closed"
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176


Is there any binaries (jar, war, tar, gz, gzip, zip files) in Gerrit project repository?No

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPOLICY-231

Refer to CI Development Best Practices
Is there any pending commit request older than 36 hours in Gerrit?No

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

Provide link to "Merge job" as evidence in Jenkins project tab

TODO

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/



Are all snapshot binaries available in Nexus?YesProvide link to evidencehttps://nexus.onap.org/content/repositories/snapshots/org/onap/policy/
Do you have a clear plan to implement the Independent Versioning and Release Process by RC0?In ProgressYesPolicy R1 Amsterdam Independent Versioning And Release Process PlanContact the upstream teams to make sure they will release their artifacts (in Nexus Release repo) so you can build by depending on these released artifacts by RC0.
Integration and TestingHave 100% of Continuous System Integration Testing (CSIT) Use Cases been implemented successfully in Jenkins?All jobs pertaining to your project MUST passYes

Is there a Docker images available for your project deliverable?YesProvide link to Nexus repos

https://nexus3.onap.org/#browse/browse/components:docker.snapshot:912d0fe7b8192392f3b0ad02bd26dced

https://nexus3.onap.org/#browse/browse/components:docker.snapshot:7f6379d32f8dd78ffdf17976461242e1

https://nexus3.onap.org/#browse/browse/components:docker.snapshot:22b3686a9064fa3dddc47beba31ae843

https://nexus3.onap.org/#browse/browse/components:docker.snapshot:c60bc6b9612f47d39ea75aee38903174


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 
DocHas the team created a documentation Template in ReadTheDocs?In ProgressYeshttp://onap.readthedocs.io/en/latest/submodules/policy/engine.git/docs/index.html

Documentation Team is using ReadTheDocs for documenting user facing documentation.

ReadTheDcos shall be considered as a starting pint for someone new withn ONAP.

The ReadTheDcos is the ONAP Documentation facade visible to users.

Link to Template

How to setup the template for my project?

Is the API documentation section poplulated?In ProgressLink to evidenceYeshttp://onap.readthedocs.io/en/latest/submodules/policy/engine.git/docs/platform/offeredapis.htmlEnsure there is at least a direct link toward the API documentation which may be already existing in the wiki.