DRAFT PROPOSAL FOR COMMENTS
The following items are expected to be completed for the project to Pass Release Sign-Off Milestone.
Release Sign-Off Milestone overview is available in wiki.
| Info | ||
|---|---|---|
| ||
|
| Practice Area | Checkpoint | Yes/No | Evidences | How to? |
|---|---|---|---|---|
| Product Management | Are committed Product Backlog Stories been coded and marked as "Done" in Jira? | Y | Link to Jira | |
| Are all tasks associated with committed Product Backlog Stories been marked as "Done" in Jira? | Y | Link to Jira | ||
| Provide the project features list under the form of a bulleted list. | Please see the "new features" section of release notes | Link to evidence |
Summarize any functionalities that were planned at Release planning and not delivered at Release Sign-Off | None | |||
| Release Management | Have all issues pertaining to FOSS been addressed? | Y | ||
| Have all findings from previous milestones been addressed? | Y | Provide link to JIRA findings | ||
| Development | Are all the Jenkins jobs successfully passed (verify + merge jobs)? | Y | ||
| Are all binaries available in Nexus Release repository? |
| WIP | Provide link to evidence (under verification) https://nexus.onap.org/content/repositories/releases/org/onap/ |
| Are all Docker images available In Nexus? | Y | Provide link to evidence |
nexus3.onap.org:10002/onap/org.onap.dcaegen2.deployments.bootstrap:v1.1.0
nexus3.onap.org:10002/onap/org.onap.dcaegen2.platform.cdapbroker:v4.0.0
nexus3.onap.org:10002/onap/org.onap.dcaegen2.platform.configbinding:v1.2.0
nexus3.onap.org:10002/onap/org.onap.dcaegen2.platform.deployment-handler:v1.1.0
nexus3.onap.org:10002/onap/org.onap.dcaegen2.platform.inventory-api:v1.2.0
nexus3.onap.org:10002/onap/org.onap.dcaegen2.platform.policy-handler:v1.1.0
nexus3.onap.org:10002/onap/org.onap.dcaegen2.platform.servicechange-handler:v1.0.0
https://jenkins.onap.org/view/dcagen2/job/dcaegen2-master-verify-csit-testsuites/
| Goal is to incease our confidence the latest commit did not break the major functionality. Jenkins CSIT Jobs | ||
| Has the project code successfully passed the Daily Build process? | Y | Provide link to evidence |
| Goal is to ensure the latest project commit has not broken the Integration Daily Build | |||
Has the project done the integration testing with related dependent projects? | Y | ||
| Documentation | Has your team contributed and completed work in the following documentations in ReadTheDocs:
| Y | Provide Link to ReadTheDocs Release Notes |
Provide Link to ReadTheDocs Project Documentation |