DRAFT PROPOSAL FOR COMMENTSThis checklist is expected to be completed for the project to pass the M1 Release Planning Milestone.
M1 Release Planning Milestone definition
| Info |
|---|
|
- 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? |
|---|
| Doc | Has the team created a docs folder and Development and Release Notes documentation templates in Readthedocs? |
| Add a link to your project documentation in ReadTheDocs. | 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? |
| Security | Has the Release Security/Vulnerability table been filled out in the protected Security Vulnerabilities wiki space? |
| Table in the protected Security Vulnerabilities wiki space corresponds to the latest NexusIQ scan | PTL reviews the NexusIQ scans for their project repos and fills out the vulnerability review table
|
| Have known vulnerabilities (critical and severe) to address/remove in the release been identified with JIRA ticket? |
| 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? |
| Project plans that include | See https://www.coreinfrastructure.org/programs/badge-program/ or CII Badging Program |
| Has the project created their project CII questionnaire and completed the ONAP level CII requirements |
|
| See CII Badging Program |
| If the project uses java, has the project integrated with the oparent.pom? |
| Oparent.pom included in the project |
|
| Product Management | Are Product Backlog Epics entered in Jira? |
YesOpen-O JIRA| System Jira | | jqlQuery | project=holmes and issuetype=epic and fixVersion = "Beijing Release" |
|---|
| count | true |
|---|
| serverId |
|---|
|
|
103a0e9afe8334c7be1e60de28d6afc1YesOpen-O JIRA| System Jira | | jqlQuery | project=holmes and issuetype=story and fixVersion = "Beijing Release" |
|---|
| count | true |
|---|
| serverId |
|---|
|
|
103a0e9afe8334c7be1e60de28d6afc1YesHolmes Yes perform for Story | Stories (for coming Sprint) in Product backlog? |
YesYesIs Member | Members willing to create Tasks and associate them with Stories in Jira? |
YesYes | Deliverables for Planning Milestone |
| Release Planning Template |
|
| Has the Platform Maturity Table been updated with current status and Release goal? |
|
| For each Release, there is a Platform Maturity table created for PTLs to record their goals and achievements at M4 (Example: Casablanca Release Platform Maturity). |
| Have all the "Release Components Name" been defined in Resources and Repositories (Deprecated) for your project? (this includes all Sub-Components Names, Sub-Components Repositories Names, Maven Group ID, Sub-Components Description) |
YesYesYes | Yes | Integration and Testing |
|
|
|
| Integration and Testing | Has the Integration Team defined the vendor equipment list? |
| Link to evidence |
|
| Has the project passed the Integration Sanity Tests? |
|
| Integration sanity tests in Dublin Release cover: - ONAP deployment
- All components health check
- VNF onboarding and service creation for vFW use case
- Model distribution for vFW
- vFW instantiation
- vFW closed loop
- vFW deletion
No test failure reported on http://onapci.org/grafana/d/8cGRqBOmz/daily-summary?orgId=1 No Integration Blocking Issue with no workaround |
| Has the Integration Team defined the End 2 End Release Test Case? |
| Link to evidence |
|
Development
| Is the Project Team committed to |
automate Yes | Is the
|
|
|
| Has the Project Team put in place an Automated Unit Test infrastructure |
in placeYes project team | Project Team committed to create Continuous System Integration Testing (CSIT) test case? |
Yes | Development project team | Project Team committed to perform Scrum ceremonies? |
Yes project team member | Project Team members aware of Continuous Integration Principles (don't break the build, Fix the build,...)? |
Yes the project team | the Project Team a clear understanding on the Code Coverage expectations? |
Yes project team | Project Team understand the Free and Open Source Software (FOSS) process? |
Yes project team | Project Team willing to fill out accordingly the FOSS table? |
Yes project team aware of Yes project team Yes project team Yessection related to Guidelines