...
| Practice Area | Checkpoint | Yes/No | Evidences | How to? | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product Management | Have all JIRA Stories supporting the release use case been implemented? | yes | 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. | yes | 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? | 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? | Done | ||||||||||||||||||||||
| Have all findings from previous milestones been addressed? | Done | 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? | Done | 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? | yes | 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)? | no | one is pending for intergation's helpyes | ||||||||||||||||||||||
| Are all snapshot binaries available in Nexus? | yes | multicloud images | ||||||||||||||||||||||
| Do you have a clear plan to implement the Independent Versioning and Release Process by RC0? | yes | 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? | yes | ||||||||||||||||||||||
| Is there a Docker images available for your project deliverable? | multicloud images | |||||||||||||||||||||||
| Has the project code successfully passed the Daily Build process? | yes | Goal is to ensure the latest project commit has not broken the Integration Daily Build | ||||||||||||||||||||||
| Doc | Has the team created a docs folder and Development and Release Notes documentation templates in Readthedocs? | yes | document is a part of code repo | 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 Templates | ||||||||||||||||||||
| Is the API documentation section populated? | yes | documents | Ensure there is at least a direct link toward the API documentation which may be already existing in the wiki. |