Versions Compared

Old Version 2

changes.mady.by.user ChrisC

Saved on

compared with

New Version Current

changes.mady.by.user ChrisC

Saved on

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/NoEvidences
How to?
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

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

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

, only remaining ones are about documentation that we plan to complete before Beijing 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
JIRA Backlog for Beijing Release

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

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

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

Release ManagementHave all issues pertaining to FOSS been addressed?Yes
Have all findings from previous milestones been addressed?YesNo Specific
findings.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?YesNexus IQ report
DevelopmentAre all Defects of priority Highest and High in status "Done" in Jira?Yes

Remaining High and Highest Defects :

Jira Legacy
serverSystem Jira

columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionmaximumIssues20

jqlQueryproject = Clamp and (priority = high or priority = highest) and status = open
counttrue
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

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
linkFor evidences, provide
link
(s) to Gerrit repos by providing the URL as shown in this exampleExample
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.98%
CLAMP CII Best Practices page.

Image Added

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

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.

Yes

Nexus IQ report


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

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

Jenkins CLAMP Tab

Being fixed today

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

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

Read the docs RLN link to be added

Documentation Team is using Readthedocs for documenting user facing 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 http://onap.readthedocs.io/en/latest/guides/onap-developer/how-to-use-docs/include-documentation.html#templates-and-examples

How to setup the template for my project?

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

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