Logging Casablanca M4 Deliverable for Code Freeze Milestone Checklist Template

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

Use the "Copy" option (available under the ..., top right of this page) to duplicate this template into your project wiki.
Fill out the Yes/No column
Provide link to evidence (when necessary)

Practice Area	Checkpoint	Yes/No	Evidences	How to?

Practice Area	Checkpoint	Yes/No	Evidences	How to?
Product Management	Have all JIRA Stories supporting the release use case been implemented?	Yes	By using the macro JIRA Issue/Filter, provide a link to JIRA in listing the stories that are implemented in Amsterdam	For each JIRA story that are implemented in Casablanca Release, you have to setup in JIRA the JIRA fixVersion="Casablanca Release"
	List the Stories that will not be implemented in this current Release.		By using the macro JIRA Issue/Filter, provide a link to JIRA in listing the stories that are NOT implemented in all of Logging Casablanca Scope moving to Logging Dublin Scope	For each JIRA story that will not be implemented in Casablanca Release, you have to setup in JIRA the JIRA fixVersion="DublinRelease"
	Are committed Sprint Backlog Stories been coded and marked as "Closed" in Jira?	Yes	Provide Link to Project backlog we don't use a sprint this release - it is just myself and @Luke Parker on the code with help from @Lorraine A. Welch, and additional merges from @jh245g@att.com https://jira.onap.org/secure/RapidBoard.jspa?rapidView=143
	Are all tasks associated with committed Sprint Backlog Stories been marked as "Closed" in Jira?	Yes
Release Management	Have all issues pertaining to FOSS been addressed?	Yes
	Have all findings from previous milestones been addressed?	Yes	List 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?	Yes	LOG-628: POMBA remove restricted license from tosca zip Closed
Development	Are all Defects of priority Highest and High in status "Closed" in Jira?	yes	Provide link to JIRA issue (type bug) of priority Highest and High.
	Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar)	yes	Goal: 50% for Incubation project in Beijing we have 85/100+% https://sonar.onap.org/dashboard?id=org.onap.logging-analytics%3Alogging-analytics	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	except the known LOG-628: POMBA remove restricted license from tosca zip Closed	Refer to CI Development Best Practices
	Is there any pending commit request older than 36 hours in Gerrit?	no
	Provide the "% Achieved" on the CII Best Practices program.	yes	Provide link to your project CII Best Practices page. https://bestpractices.coreinfrastructure.org/en/projects/1578 98%	As documented in CII Badging Program, teams have to fill out CII Best Practices
	Is there any Critical and Severe 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.	n/a	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. all logging vulnerabilities are being worked on - some through oparent 1.2.1 all of our vulnerabilities are deployed as demo code - and not deployed through onap R3 Logging 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	Provide link to "Merge job" as evidence in Jenkins project tab https://jenkins.onap.org/view/logging-analytics/job/logging-analytics-master-merge-java/
	Have all OOM Staging Healtcheck related to your project passed?	Yes	log-kibana, log-elasticsearch, log-logstash for some time now - as we have not changed the ELK stack for a month passing http://jenkins.onap.info/job/oom-cd-master/3495/console `04:32:39 Basic Log Elasticsearch Health Check \| PASS \| 04:32:39 ------------------------------------------------------------------------------ 04:32:39 Basic Log Kibana Health Check \| PASS \| 04:32:39 ------------------------------------------------------------------------------ 04:32:39 Basic Log Logstash Health Check \| PASS \|`
	Are all snapshot binaries available in Nexus-staging?	yes	Provide link to evidence https://nexus.onap.org/service/local/repositories/snapshots/content/org/onap/logging-analytics/logging-slf4j/1.2.2-SNAPSHOT/
	Do you have a clear plan to implement the Independent Versioning and Release Process by RC0?	n/a	we have no api or docker container	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 Testing	Have 100% of Continuous System Integration Testing (CSIT) Use Cases been implemented successfully in Jenkins?	n/a	All jobs pertaining to your project MUST pass we don't have a consumable API LOG-245: Logging library CSIT testingClosed
	Is there a Docker images available for your project deliverable?	n/a	Provide link to Nexus repos
	Has the project code successfully passed the Daily Build process?	Yes	the 3 failing jobs are related to the fact we do not publish our demo docker container on nexus first 5 jobs are for logging https://jenkins.onap.org/view/logging-analytics/ https://jenkins.onap.org/view/logging-analytics/job/logging-analytics-master-verify-java/ and CI/CD deployment OK http://jenkins.onap.info/job/oom-cd-master/3495/console	Goal is to ensure the latest project commit has not broken the Integration Daily Build
Doc	Has the team created a docs folder and Development and Release Notes documentation templates in Readthedocs?	Yes	Modified spec: ONAP Application Logging Specification v1.2 (Casablanca) and wiki doc Cloud Native Deployment ONAP Development Logging Developer Guide unchanged https://onap.readthedocs.io/en/latest/submodules/logging-analytics.git/docs/index.html	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?
Doc	Is the API documentation section populated?	n/A	Link to evidence	Ensure there is at least a direct link toward the API documentation which may be already existing in the wiki.