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.
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 | Evidences | How to? |
|---|---|---|---|---|
| Product Management | Are committed Product Backlog Stories been coded and marked as "Done" in Jira? | Yes | Getting issues... | |
| Are all tasks associated with committed Product Backlog Stories been marked as "Done" in Jira? | Yes | Getting issues... | ||
| Provide the project features list under the form of a bulleted list. | Yes |
| ||
Summarize any functionalities that were planned at Release planning and not delivered at Release Sign-Off | Yes |
| ||
| Release Management | Have all issues pertaining to FOSS been addressed? | Yes | ||
| Have all findings from previous milestones been addressed? | Yes | |||
| Development | Are all the Jenkins jobs successfully passed (verify + merge jobs)? | Yes | NOTE: Verify/Merge jobs are only for master branch. Beijing branch will not be instituted unless a maintenance release is necessary. | |
| Are all binaries available in Nexus Release repository? | Yes | https://nexus.onap.org/content/repositories/releases/org/onap/policy/ v1.2.3 artifacts | ||
| Are all Docker images available In Nexus? | Yes | 2 Docker images: https://nexus3.onap.org/#browse/browse:docker.release:v2%2Fonap%2Fpolicy-drools%2Fmanifests%2F1.2.3 https://nexus3.onap.org/#browse/browse:docker.release:v2%2Fonap%2Fpolicy-pe%2Fmanifests%2F1.2.3 | ||
| Are the Java and Docker manifest updated with the same version as in Nexus Release repository? | Yes | |||
| Integration and Testing | Have all CSIT Use Cases (created by each project team) passed? | Yes | NOTE: CSIT are only enabled for master branch. CSIT for beijing branch will not be instituted unless a maintenance release is necessary. | 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? | Yes | NOTE: Daily Build Jobs are disabled after the release of Beijing. Release jobs for Beijing will only be instituted if a maintenance release is necessary. | 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? | Yes | |||
| Documentation | Has your team contributed and completed work in the following documentations in ReadTheDocs:
| Yes | ReadTheDocs Release Notes: https://onap.readthedocs.io/en/beijing/submodules/policy/engine.git/docs/release-notes.html ReadTheDocs Project Documentation: https://onap.readthedocs.io/en/beijing/submodules/policy/engine.git/docs/index.html |