The following items are expected to be completed for the project to Pass the M4 Code Freeze Milestone.
M4 Release Code Freeze Milestone overview is available in wiki.
Usage
- Use the "Copy" option (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 | Have all JIRA Stories supporting the release use case been implemented? | No | 1 story remains - Increasing test coverage
Getting issues...
| 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 |
Getting issues...
| 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? | No | |||
| Are all tasks associated with committed Sprint Backlog Stories been marked as "Done" in Jira? | Yes | Getting issues... | ||
| Release Management | Have all issues pertaining to FOSS been addressed? | Yes | ||
| Have all findings from previous milestones been addressed? | Yes | https://sonar.onap.org/overview?id=46017 inno - 43.1% https://sonar.onap.org/overview?id=54083 Authz - 32.6% https://sonar.onap.org/overview?id=45529 Cadi - 32.2% | 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/aaf/job/aaf-authz-docker-master-merge-properties-java/ https://jenkins.onap.org/view/aaf/job/aaf-authz-master-merge-java/ https://jenkins.onap.org/view/aaf/job/aaf-cadi-master-merge-java/ https://jenkins.onap.org/view/aaf/job/aaf-inno-master-merge-java/ | ||
| Are all snapshot binaries available in Nexus? | Yes | https://nexus.onap.org/#nexus-search;quick~aaf | ||
| 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 | https://jenkins.onap.org/view/aaf/job/aaf-master-verify-csit-aafapi/ | |
| Is there a Docker images available for your project deliverable? | Yes | https://nexus3.onap.org/#browse/search=keyword%3Daaf | ||
| Has the project code successfully passed the Daily Build process? | Yes | https://jenkins.onap.org/view/Daily-Jobs/ | 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/aaf/authz.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? | Yes | AAF API | Ensure there is at least a direct link toward the API documentation which may be already existing in the wiki. |
1 Comment
Keong Lim
Christopher McCray why is there an edit on an Amsterdam release page?
Maybe it was intended for the Dublin M4 page instead? AAF R4 - M4 Deliverable for Code Freeze Milestone Checklist