| Practice Area | Checkpoint | Yes/No | Evidences | How to? | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product Management | Have all JIRA Stories supporting the release use case been implemented? | Yes |
Some stories are about the docs and deployment problems rather than the functionality codes. For the functionalities, all stories are done. | 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 |
| 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? | NoWIP | Some non-function stories are not finished yet. | ||||||||||||
| Are all tasks associated with committed Sprint Backlog Stories been marked as "Done" in Jira? | NoWIP | Some tasks depend on the upstream system (DCAE). | ||||||||||||
| Release Management | Have all issues pertaining to FOSS been addressed? | Yes | ||||||||||||
| Have all findings from previous milestones been addressed? | Yes | 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 |
| |||||||||||
| 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 | Holmes Jenkins Jobs | ||||||||||||
| Are all snapshot binaries available in Nexus? | Yes | Holmes Binaries | ||||||||||||
| Do you have a clear plan to implement the Independent Versioning and Release Process by RC0? | Yes | This is supposed to be done by RC0. | 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 | All jobs pertaining to your project MUST pass | |||||||||||
| Is there a Docker images available for your project deliverable? | Yes | ONAP Docker Repo | ||||||||||||
| Has the project code successfully passed the Daily Build process? | Yes | Sometimes they may fail due to the environment failures of the CI/CD platform, not actually caused by the Holmes team. | 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? | No | The directories are created. The API documents are converted as required by the doc team. But now we are not able to find our page on http://onap.readthedocs.io. Still woring with the doc team to chech what the problem is. But generally speaking, the doc process is now under control and we'll catch up very soon. | 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 | See above. | Ensure there is at least a direct link toward the API documentation which may be already existing in the wiki. |
Page History
Overview
Content Tools