This checklist is expected to be completed for the project to pass the M1 Release Planning Milestone.
M1 Release Planning Milestone definition
Usage
- Use the "Copy" and "Move" options (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 | Evidence - Comment | How to? |
|---|---|---|---|---|
| Security | Has the Release Security/Vulnerability table been filled out in the protected Security Vulnerabilities wiki space? | Yes | /wiki/spaces/SV/pages/16089298 | /wiki/spaces/SV/pages/16089298 |
| Have known vulnerabilities (critical and severe) to address/remove in the release been identified with JIRA ticket? | Yes | JIRA tickets exist for vulnerabilities or the project indicates that there will be no vulnerability library replacement. | Create JIRA tickets | |
| Has the project committed to the release CII badging level? | No | Project plans that include | See https://www.coreinfrastructure.org/programs/badge-program/ | |
| Has the project created their project CII questionnaire and completed the ONAP level CII requirements | No | https://bestpractices.coreinfrastructure.org/en/projects/1579 questionnaire fill in but don't plan to meet Dublin ONAP requirement. | See CII Badging Program | |
| If the project uses java, has the project integrated with the oparent.pom? | No |