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

CLAMP was not involved in specific Beijing committed use case, but focused on Maturity improvements. All of the committed Maturity improvements have been delivered as well as other improvements.

Release Content

List the Stories that will not be implemented in this current Release.Yes

All committed stories are implemented.

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

Getting issues...

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

Getting issues...

Release ManagementHave all issues pertaining to FOSS been addressed?Yes
Have all findings from previous milestones been addressed?YesNo Specific findings.

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?

For both (a) and (b), have all high priority non-Project Licenses been either removed or escalated as likely exception requests?YesNexus IQ report
DevelopmentAre all Defects of priority Highest and High in status "Done" in Jira?Yes

Remaining High and Highest Defects : Getting issues...

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 is achieved : sonar link
Is there any binaries (jar, war, tar, gz, gzip, zip files) in Gerrit project repository?No
Is there any pending commit request older than 36 hours in Gerrit?No
Provide the "% Achived" on the CII Best Practices program.98%

The only item not passed is the fix of severe and high security issues of which only the severe have been fixed or documented in the security issue page of CLAMP

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.


Nexus IQ report

Only Jackson Databind is left in CLAMP, which has been addressed, see the security issue page of CLAMP

Are all the Jenkins jobs successfully passed (verify + merge jobs)?YesJenkins CLAMP Tab
Are all snapshot binaries available in Nexus?Yeslink to evidence
Do you have a clear plan to implement the Independent Versioning and Release Process by RC0?Yes
Integration and TestingHave 100% of Continuous System Integration Testing (CSIT) Use Cases been implemented successfully in Jenkins?Yes

Jenkins CLAMP Tab

Is there a Docker images available for your project deliverable?YesNexus 3 Docker repo
Has the project code successfully passed the Daily Build process?YesJenkins CLAMP Tab
DocHas the team created a docs folder and Development and Release Notes documentation templates in Readthedocs?Yes

An updated Release note is ready in Read the docs, we still plan to further improve the release documentation in the coming weeks.

Release Note link

CLAMP ReadtheDocs link

Is the API documentation section populated?Yes

CLAMP Documentation

API doc included in Online doc

Note that CLAMP is now integrated with SWAGGER and MSB