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.


Usage

  1. Use the "Copy" option (available under the ..., top right of this page) to duplicate this template into your project wiki.
  2. Fill out the Yes/No column
  3. Provide link to evidence (when necessary)
Practice AreaCheckpointYes/NoEvidencesHow to?
Product ManagementHave all JIRA Stories supporting the release use case been implemented?No

Getting issues... User Stories closed with Resolution Done and status in Done and implemented.

Getting issues... User stories that are in progress or TODO. They are primarily either stretch goals for R2 or the Platform Maturity requirements that are work in progress.


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

While we don't have any user stories that we are not implementing the current release, we may have to move some of our stretch goals to this list or move it to the next release.

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... marked done.

Note: Issues listed as TODO or In-Progress in the first row is still open.


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

Getting issues... marked done.

Getting issues... are yet to be done - some of these are stretch goals, Platform Maturity related tasks.


Release ManagementHave all issues pertaining to FOSS been addressed?YesNo FOSS items have been flagged for OOF.
Have all findings from previous milestones been addressed?YesThe functional tests have been pushed to the integration project since last milestone.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?Yes

DevelopmentAre all Defects of priority Highest and High in status "Done" in Jira?Yes

Getting issues...


Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar)Yes

OSDF: https://sonar.onap.org/dashboard?id=org.onap.optf.osdf%3Aoptf-osdf

HAS: https://sonar.onap.org/dashboard?id=org.onap.optf.has%3Aoptf-has

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% on the passing badge.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

https://nexus-iq.wl.linuxfoundation.org/assets/index.html#/reports/optf-has/ebdd5bafe94246cd8603240a7bec92b0

https://nexus-iq.wl.linuxfoundation.org/assets/index.html#/reports/optf-osdf/c6b63f373fc04b5783210586ae7c27eb

However, please note that we are a pure Python project, and there was a concern on these reports being inaccurate for Python.

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)?Yeshttps://jenkins.onap.org/view/optf/
Are all snapshot binaries available in Nexus?Yeshttps://nexus.onap.org/content/repositories/snapshots/org/onap/optf/
Do you have a clear plan to implement the Independent Versioning and Release Process by RC0?YesThis is work in progress. We are currently working with Policy, AAI and MultiCloud to identify the Nexus repo artifacts.Contact 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?No

One repo has 100% completed, another repo is WIP as of 03/27.

HAS: https://jenkins.onap.org/view/optf/job/optf-has-master-csit-has/

OSDF: WIP

Test Implementation Details:

OOF Beijing (R2) Functional Testing planning

Is there a Docker images available for your project deliverable?Yes

https://nexus3.onap.org/repository/docker.snapshot/v2/onap/optf-has/manifests/latest



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 docs folder and Development and Release Notes documentation templates in Readthedocs?Yes

OSDF: https://onap.readthedocs.io/en/latest/submodules/optf/osdf.git/docs/index.html

HAS: https://onap.readthedocs.io/en/latest/submodules/optf/has.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?Yes

OSDF:

HAS

Ensure there is at least a direct link toward the API documentation which may be already existing in the wiki.