DCAE R3 M4 Code Freeze Milestone Checklist
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? |
---|---|---|---|---|
Product Management | Have all JIRA Stories supporting the release use case been implemented? | Yes | Getting issues... | For each JIRA story that are implemented in Amsterdam Release, you have to setup in JIRA the JIRA fixVersion="Beijing Release" |
List the Stories that will not be implemented in this current Release. | Yes | Getting issues... | For each JIRA story that will not be implemented in Amsterdam Release, you have to setup in JIRA the JIRA fixVersion="Casablanca Release" | |
Are committed Sprint Backlog Stories been coded and marked as "Done" in Jira? | Yes | https://jira.onap.org/secure/RapidBoard.jspa?rapidView=49&view=planning.nodetail&epics=visible | ||
Are all tasks associated with committed Sprint Backlog Stories been marked as "Done" in Jira? | Yes | Getting issues... | ||
Release Management | Have all issues pertaining to FOSS been addressed? | Yes | ||
Have all findings from previous milestones been addressed? | Yes | 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 | |||
Development | Are all Defects of priority Highest and High in status "Done" 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 Casablanca dcaegen2/analytics/tca https://sonar.onap.org/dashboard?id=org.onap.dcaegen2.analytics.tca%3Adcae-analytics 75.8% dcaegen2/collectors/snmptrap https://sonar.onap.org/dashboard?id=org.onap.dcaegen2.collectors%3Asnmptrap 52.3% dcaegen2/collectors/ves https://sonar.onap.org/dashboard?id=org.onap.dcaegen2.collectors.ves%3AVESCollector 60.8% dcaegen2/platform/configbinding https://sonar.onap.org/dashboard?id=org.onap.dcaegen2.platform%3Aconfigbinding 79.4% dcaegen2/platform/plugins https://sonar.onap.org/dashboard?id=org.onap.dcaegen2.platform%3Aplugins 51% dcaegen2/platform/inventory-api https://sonar.onap.org/dashboard?id=org.onap.dcaegen2.platform%3Ainventory-api 50.8% dcaegen2/platform/policy-handler https://sonar.onap.org/dashboard?id=org.onap.dcaegen2.platform%3Apolicy-handler 75.7% dcaegen2/platform/cli https://sonar.onap.org/dashboard?id=org.onap.dcaegen2.platform.cli%3Acli 75.7% dcaegen2/utils https://sonar.onap.org/dashboard?id=org.onap.dcaegen2.utils%3Autils 78.9% dcaegen2/services/heartbeat https://sonar.onap.org/dashboard?id=org.onap.dcaegen2.platform%3Aheartbeat 59.3% dcaegen2/services/mapper https://sonar.onap.org/dashboard?id=org.onap.dcaegen2.services.mapper%3Amapper 62.2% dcaegen2/services/prh https://sonar.onap.org/dashboard?id=org.onap.dcaegen2.services%3Aprh 71.5% dcaegen2/collectors/hv-ves - 60% (kotlin not supported) dcaegen2/collectors/datafile - https://sonar.onap.org/dashboard?id=org.onap.dcaegen2.collectors%3Adatafile - 62.8% dcaegen2/analytics/tca-gen2 - https://sonar.onap.org/dashboard?id=org.onap.dcaegen2.analytics.tca-gen2%3Atca-gen2-parent - 53.4% | For evidences, provide link(s) to Gerrit repos by providing the URL as shown in this example | |
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. | 94% | https://bestpractices.coreinfrastructure.org/en/projects/1718 | 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:
which is complaint with CVSS V2.0 rating. | Yes | 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. | Ensure the Nexus-IQ report from “Jenkins CLM” shows 0 critical security vulnerability. Open the Nexus-IQ report for the details on each repo. | |
Have all OOM Staging Healtcheck related to your project passed? | Yes | Pending OOM charts to be merged - https://gerrit.onap.org/r/#/c/66865/ |
| |
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/dcagen2/ | ||
Are all snapshot binaries available in Nexus-staging? | Yes | Provide link to evidence https://nexus.onap.org/content/repositories/snapshots/org/onap/dcaegen2/1.2.1-SNAPSHOT/ | ||
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 Testing | Have 100% of Continuous System Integration Testing (CSIT) Use Cases been implemented successfully in Jenkins? | No | Most recent run below job failed; being analyzed | |
Is there a Docker images available for your project deliverable? | Yes | onap/org.onap.dcaegen2.platform.configbinding.app-app:2.2.3 | ||
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 | ||
Doc | Has the team created a docs folder and Development and Release Notes documentation templates in Readthedocs? | Yes | Add a link to your project documentation in ReadTheDocs. http://onap.readthedocs.io/en/latest/submodules/dcaegen2.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. |
Is the API documentation section populated? | Yes | Link to evidence http://onap.readthedocs.io/en/latest/submodules/dcaegen2.git/docs/sections/offeredapis.html | Ensure there is at least a direct link toward the API documentation which may be already existing in the wiki. |