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

Change Management use case has been implemented APPC-1169 - Getting issue details... STATUS APPC-1170 - Getting issue details... STATUS APPC-1171 - Getting issue details... STATUS

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.

N/A


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?Yes131 issues
Are all tasks associated with committed Sprint Backlog Stories been marked as "Done" in Jira?Yes134 Issues
Release ManagementHave all issues pertaining to FOSS been addressed?Yes

Have all findings from previous milestones been addressed?N/ANo FindingsFor 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

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

Yes

Currently at 57.4%

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

However, there are some commits in Draft status - which are for R4.


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.

Yes

Casablanca APPC Security/Vulnerability ReportEnsure the Nexus-IQ report from “Jenkins CLM” shows 0 critical security vulnerability. Open the Nexus-IQ report for the details on each repo.
Provide the "% Achived" on the CII Best Practices program.95%https://bestpractices.coreinfrastructure.org/en/projects/1579As documented in CII Badging Program, teams have to fill out CII Best Practices
Are all the Jenkins jobs successfully passed (verify + merge jobs)?Yes

Are all snapshot binaries available in Nexus?Yeshttps://nexus.onap.org/content/repositories/snapshots/org/onap/appc/
Do you have a clear plan to implement the Independent Versioning and Release Process by RC0?Yes
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?Yes



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

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

Documentation has been update; however, further updates will continue to be make. Release Notes will be done closer to release.


APPC Documentation

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?YesAPPC DocumentationEnsure there is at least a direct link toward the API documentation which may be already existing in the wiki.