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 Area | Checkpoint | Yes/No | Evidences | How to? |
|---|---|---|---|---|
| Product Management | Have all JIRA Stories supporting the release use case been implemented? | Yes | ||
| List the Stories that will not be implemented in this current Release. | None | |||
| Are committed Sprint Backlog Stories been coded and marked as "Closed" in Jira? | Yes | Getting issues... | ||
| Are all tasks associated with committed Sprint Backlog Stories been marked as "Closed" 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 | 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? | WIP | |||
| Development | Are all Defects of priority Highest and High in status "Closed" in Jira? | WIP | 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) | WIP | 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 | 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. | https://bestpractices.coreinfrastructure.org/en/projects?q=aaf 98% Passing, 2% Silver | 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. | In the case critical known vulnerability are still showing in the report, fill out the Security/Vulnerability Threat Template in your project. https://jenkins.onap.org/view/aaf/job/aaf-authz-maven-clm-master/ https://jenkins.onap.org/view/aaf/job/aaf-cadi-maven-clm-master/ https://jenkins.onap.org/view/aaf/job/aaf-luaplugin-maven-clm-master/ | Ensure the Nexus-IQ report from “Jenkins CLM” shows 0 critical security vulnerability. Open the Nexus-IQ report for the details on each repo. There is 1 Severe error in AAF, which does not impact runtime services. There is 1 Critical error in CADI, but that is for Shiro dependency for Shiro Plugin, only used by Shiro APPs. (in that case, they have larger issues) | ||
| Are all the Jenkins jobs successfully passed (verify + merge jobs)? | Yes | |||
| Have all OOM Staging Healtcheck related to your project passed? | Yes | http://onapci.org/grafana/d/8cGRqBOmz/daily-summary?panelId=9&fullscreen&orgId=1 | ||
| Are all snapshot binaries available in Nexus-staging? | Yes | Provide link to evidence https://nexus.onap.org/#nexus-search;gav~org.onap.aaf.authz~~2.1.2-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? | Yes | https://jenkins.onap.org/view/CSIT/ | |
| Is there a Docker images available for your project deliverable? | Yes | https://nexus3.onap.org/#browse/search=keyword%3Daaf | ||
| 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? | WIP | https://onap.readthedocs.io/en/latest/submodules/aaf/authz.git/docs/index.html https://onap.readthedocs.io/en/latest/submodules/aaf/authz.git/docs/sections/release-notes.html https://onap.readthedocs.io/en/latest/submodules/aaf/sms.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? | WIP | https://onap.readthedocs.io/en/latest/release/repolist.html | Ensure there is at least a direct link toward the API documentation which may be already existing in the wiki. |