...
| Practice Area | Checkpoint | Yes/No | Evidences | How to? | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product Management | Have all JIRA Stories supporting the release use case been implemented? | TBD | By using the macro JIRA Issue/Filter, provide a link to JIRA in listing the stories that are implemented in Amsterdam Release. (Example
| 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. | TBD | By using the macro JIRA Issue/Filter, provide a link to JIRA in listing the stories that are NOT implemented in Amsterdam Release. (Example
| 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? | TBD | Provide Link to Project backlog | ||||||||||||||||||||||
| Are all tasks associated with committed Sprint Backlog Stories been marked as "Done" in Jira? | TBD | |||||||||||||||||||||||
| Release Management | Have all issues pertaining to FOSS been addressed? | YES | ||||||||||||||||||||||
| Have all findings from previous milestones been addressed? | YES | M3 CSIT test cases was not addressed, and been resolved and passed M3 | 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? | YES | 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? | NO | Refer to CI Development Best Practices | ||||||||||||||||||||||
| Is there any pending commit request older than 36 hours in Gerrit? | NO | |||||||||||||||||||||||
| Are all the Jenkins jobs successfully passed (verify + merge jobs)? | YES | https://jenkins.onap.org/view/cli/job/cli-master-merge-java/ | ||||||||||||||||||||||
| Are all snapshot binaries available in Nexus? | https://nexus.onap.org/#nexus-search;quick~org.onap.cli | |||||||||||||||||||||||
| Do you have a clear plan to implement the Independent Versioning and Release Process by RC0? | YES | 1.1.0 | 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? | TBD | https://jenkins.onap.org/view/cli/job/cli-master-verify-csit-sanity-check/ | |||||||||||||||||||||
| Is there a Docker images available for your project deliverable? | YES | https://nexus3.onap.org/#browse/search=keyword%3Dcli | ||||||||||||||||||||||
| Has the project code successfully passed the Daily Build process? | YES | https://jenkins.onap.org/view/cli/job/cli-master-release-version-java-daily/ | 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? | YES | http://onap.readthedocs.io/en/latest/submodules/cli.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? | TBD | Link to evidence | Ensure there is at least a direct link toward the API documentation which may be already existing in the wiki. |