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? | No | All stories the OOM Team agreed to completing for Casablanca, during M3 architecture review, have either been closed or patches are up for review and remaining stories will be closed after patches are merged. JIRA stories not related to those stories are still being worked. Progress can been seen here: https://jira.onap.org/projects/OOM/versions/10443 or with Jira Issues not closed | 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. | We intend to finish during the integration period | For each JIRA story that will not be implemented in Casablanca Release, you have to setup in JIRA the JIRA fixVersion="Dublin Release" | ||
| Are committed Sprint Backlog Stories been coded and marked as "Closed" in Jira? | Not all stories are done | https://jira.onap.org/secure/RapidBoard.jspa?projectKey=OOM&rapidView=41&view=planning | ||
| Are all tasks associated with committed Sprint Backlog Stories been marked as "Closed" in Jira? | Not all tasks are done | |||
| 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 | |||
| Development | Are all Defects of priority Highest and High in status "Done" in Jira? | No | More defects are expected during the integration phase | |
| Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | N/A | Goal: 50% for Incubation project in Beijing | 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? | https://gerrit.onap.org/r/#/q/project:oom+and+status:open+and+age:36h | |||
| Provide the "% Achived" on the CII Best Practices program. | 100% | https://bestpractices.coreinfrastructure.org/en/projects/1631 | 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:
which is complaint with CVSS V2.0 rating. | No | 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. | |
| Are all the Jenkins jobs successfully passed (verify + merge jobs)? | Yes | https://jenkins.onap.org/view/oom/job/oom-master-merge-helm/ | ||
| Are all snapshot binaries available in Nexus? | Yes | Staging, Snapshot and Release Helm Charts are now available in Nexus: https://nexus.onap.org/content/sites/ | ||
| Do you have a clear plan to implement the Independent Versioning and Release Process by RC0? | ? | There was a meeting with the LF and Integration to determine if independent versioning is feasable for OOM helm charts in Casablanca and it was determined that it is not. Once Helm Chart ownership has transferred to the project teams in Dublin OOM-1242 - Getting issue details... STATUS , it will then be possible to implement such a process. | 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 | |
| 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? | N/A | 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 | http://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_project_description.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? | N/A | Ensure there is at least a direct link toward the API documentation which may be already existing in the wiki. |