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? | By using the macro JIRA Issue/Filter, provide a link to JIRA in listing the stories that are implemented in Amsterdam Release. (Example Getting issues... for DCAEGEN2 project) | For each JIRA story that are implemented in Amsterdam Release, you have to setup in JIRA the JIRA fixVersion="Amsterdam Release" | |
| List the Stories that will not be implemented in this current Release. | By using the macro JIRA Issue/Filter, provide a link to JIRA in listing the stories that are NOT implemented in Amsterdam Release. (Example Getting issues... for DCAEGEN2 project) | For each JIRA story that will not be implemented in Amsterdam Release, you have to setup in JIRA the JIRA fixVersion="Beijing Release" | ||
| Are committed Sprint Backlog Stories been coded and marked as "Done" in Jira? | Provide Link to Project backlog | |||
| Are all tasks associated with committed Sprint Backlog Stories been marked as "Done" in Jira? | ||||
| Release Management | Have all issues pertaining to FOSS been addressed? | |||
| Have all findings from previous milestones been addressed? | List previous milestone issues that have not been addressed. | For M2 and M3 Milestones, ensure all findings have been closed. | ||
| Development | Are all Defects of priority Highest and High in status "Done" in Jira? | Provide link to JIRA issue (type bug) of priority Highest and High. | ||
| Is there any binaries (jar, war, tar, gz, gzip, zip files) in Gerrit project repository? | N | Couple of DCAEGEN1 repos (dcae/*) contain binary files. Deprecation of DCAEGEN1 in process. Request to lock all GEN1 repos sent to LF Helpdesk on 09/11, ticket #45671). | Refer to CI Development Best Practices | |
| Is there any pending commit request older than 36 hours in Gerrit? | ||||
| Are all the Jenkins jobs successfully passed (verify + merge jobs)? | Y | Provide link to "Merge job" as evidence in Jenkins project tab | https://jenkins.onap.org/view/dcagen2/job/dcaegen2-analytics-master-merge-java/ https://jenkins.onap.org/view/dcagen2/job/dcaegen2-analytics-tca-master-merge-java/ https://jenkins.onap.org/view/dcagen2/job/dcaegen2-collectors-master-merge-java/ https://jenkins.onap.org/view/dcagen2/job/dcaegen2-collectors-snmptrap-master-merge-java/ https://jenkins.onap.org/view/dcagen2/job/dcaegen2-collectors-ves-master-merge-java/ https://jenkins.onap.org/view/dcagen2/job/dcaegen2-deployments-master-merge-java/ https://jenkins.onap.org/view/dcagen2/job/dcaegen2-master-merge-java/ https://jenkins.onap.org/view/dcagen2/job/dcaegen2-platform-blueprints-master-merge-java/ https://jenkins.onap.org/view/dcagen2/job/dcaegen2-platform-cdapbroker-master-merge-java/ https://jenkins.onap.org/view/dcagen2/job/dcaegen2-platform-cli-master-merge-java/ https://jenkins.onap.org/view/dcagen2/job/dcaegen2-platform-configbinding-master-merge-java/ https://jenkins.onap.org/view/dcagen2/job/dcaegen2-platform-deployment-handler-master-merge-java/ https://jenkins.onap.org/view/dcagen2/job/dcaegen2-platform-inventory-api-master-merge-java/ https://jenkins.onap.org/view/dcagen2/job/dcaegen2-platform-master-merge-java/ https://jenkins.onap.org/view/dcagen2/job/dcaegen2-platform-plugins-master-merge-java/ https://jenkins.onap.org/view/dcagen2/job/dcaegen2-platform-policy-handler-master-merge-java/ https://jenkins.onap.org/view/dcagen2/job/dcaegen2-platform-servicechange-handler-master-merge-java/ https://jenkins.onap.org/view/dcagen2/job/dcaegen2-utils-master-merge-java/ | |
| Are all snapshot binaries available in Nexus? | Y | Provide link to evidence | ||
| Do you have a clear plan to implement the Independent Versioning and Release Process by RC0? | Y | 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? | All jobs pertaining to your project MUST pass | ||
| Is there a Docker images available for your project deliverable? | Y | Provide link to Nexus repos | nexus3.onap.org:10001/onap/org.onap.dcaegen2.collectors.ves.vescollector:1.1-latest nexus3.onap.org:10001/onap/org.onap.dcaegen2.dcaegen2.platformdoc:1.1-latest nexus3.onap.org:10001/onap/org.onap.dcaegen2.deployments.bootstrap:1.1-latest nexus3.onap.org:10001/onap/org.onap.dcaegen2.platform.cdapbroker:1.1-latest nexus3.onap.org:10001/onap/org.onap.dcaegen2.platform.configbinding:1.1-latest nexus3.onap.org:10001/onap/org.onap.dcaegen2.platform.inventory-api:latest nexus3.onap.org:10001/onap/org.onap.dcaegen2.platform.deployment-handler:1.1-latest nexus3.onap.org:10001/onap/org.onap.dcaegen2.platform.policy-handler:1.1-latest nexus3.onap.org:10001/onap/org.onap.dcaegen2.platform.servicechange-handler:1.1-latest | |
| Has the project code successfully passed the Daily Build process? | Goal is to ensure the latest project commit has not broken the Integration Daily Build | |||
| Doc | Has the team created a documentation Template in ReadTheDocs? | Y | 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 pint for someone new withn ONAP. The ReadTheDcos is the ONAP Documentation facade visible to users. Link to Template |
| Is the API documentation section poplulated? | Y | http://onap.readthedocs.io/en/latest/submodules/dcaegen2.git/docs/offeredapis.html | Ensure there is at least a direct link toward the API documentation which may be already existing in the wiki. |