Skip to end of metadata
Go to start of metadata

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?
Product ManagementHave all JIRA Stories supporting the release use case been implemented?Yes

Getting issues... - Closed User Stories with Resolution Done

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.Yes

Getting issues... - Closed User Stories with Resolution Won't Do

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

Getting issues... - Open User stories (should be 0)




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

Getting issues... - Closed Tasks

Getting issues... - Sanity check for Open Tasks



Release ManagementHave all issues pertaining to FOSS been addressed?N/ANo FOSS issues
Have all findings from previous milestones been addressed?N/A - no previous findingsList previous milestone issues that have not been addressed.For M2 and M3 Milestones, ensure all findings have been closed.

Has the Project Team reviewed and understood the most recent license scan reports from the LF, for both (a) licenses within the codebase and (b) licenses for third-party build time dependencies?

Yes

For both (a) and (b), have all high priority non-Project Licenses been either removed or escalated as likely exception requests?Yes2 License Issues were from ONAP Portal SDK project dependencies
DevelopmentAre all Defects of priority Highest and High in status "Done" in Jira?Yes Getting issues... (should be zero)



Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar)YesGoal: 50% for Incubation project in Beijing

For evidences, provide link(s) to Gerrit repos by providing the URL as shown in this example

Example

Is there any binaries (jar, war, tar, gz, gzip, zip files) in Gerrit project repository?No
Refer to CI Development Best Practices
Is there any pending commit request older than 36 hours in Gerrit?No

Provide the "% Achived" on the CII Best Practices program.100%

https://bestpractices.coreinfrastructure.org/en/projects/1614


As documented in CII Badging Program, teams have to fill out CII Best Practices

Is there any Critical level security vulnerabilities older than 60 days old in the third party libraries used within your project unaddressed?

Nexus-IQ classifies level as the following:

  • Critical is level 7 to 10
  • Severe is level 4 to 6
  • Moderate is level 1 to 3

which is complaint with CVSS V2.0 rating.

No

In the case critical known vulnerability are still showing in the report, fill out the Security/Vulnerability Threat Template - Beijing, Casablanca, Dublin in your project.


Policy R2 Beijing Security/Vulnerability Threat Template

Ensure the Nexus-IQ report from “Jenkins CLM” shows 0 critical security vulnerability. Open the Nexus-IQ report for the details on each repo.
Are all the Jenkins jobs successfully passed (verify + merge jobs)?Yes

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?Yeshttps://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?YesPolicy R2 Beijing 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?Yes

All jobs pertaining to your project MUST pass

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



Is there a Docker images available for your project deliverable?YesProvide link to Nexus repos
Has the project code successfully passed the Daily Build process?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 
DocHas the team created a docs folder and Development and Release Notes documentation templates in Readthedocs?Yeshttp://onap.readthedocs.io/en/latest/submodules/policy/engine.git/docs/index.html

ReadTheDcos shall be considered as a starting point for someone new within ONAP.

The ReadTheDocs is the ONAP Documentation facade visible to users.

Link to Templates

How to setup the template for my project?

Is the API documentation section populated?Yeshttp://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.