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.
| Practice Area | Checkpoint | Yes/No | Evidences | How to? | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product Management | Have all JIRA Stories supporting the release use case been implemented? | Yes |
| 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? | yes | http://project=so and fixversion="Amsterdam Release" | ||||||||||||
| Are all tasks associated with committed Sprint Backlog Stories been marked as "Done" in Jira? | yes | |||||||||||||
| Release Management | Have all issues pertaining to FOSS been addressed? | yes | ||||||||||||
| Have all findings from previous milestones been addressed? | Yes (Code coverage) | 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? | In Progress | 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 |
https://gerrit.onap.org/r/#/q/status:open+project:sdc
https://gerrit.onap.org/r/#/q/status:open+project:sdc/jtosca
https://gerrit.onap.org/r/#/q/status:open+project:sdc/sdc-distribution-clienthttps://gerrit.onap.org/r/#/q/status:open+project:sdc/sdc-docker-base
https://gerrit.onap.org/r/#/q/status:open+project:sdc/sdc-titan-cassandra
https://gerrit.onap.org/r/#/q/status:open+project:sdc/sdc-tosca
https://gerrit.onap.org/r/#/q/status:open+project:sdc/sdc-workflow-designer
| Are all the Jenkins jobs successfully passed (verify + merge jobs)? | yes | https://jenkins.onap.org/view/ |
| so/ | ||||
| Are all snapshot binaries available in Nexus? | Yes (Listed under the Ecomp folder) | Provide link to evidence | ||
| Do you have a clear plan to implement the Independent Versioning and Release Process by RC0? | Yes | Integrated with the oparent already. | 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 | There are some |
| Is there a Docker images available for your project deliverable? | Yes | Provide link to Nexus repos | ||
| 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 | Is in progress... Checkin is done | 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 | SO R1 Interfaces | Ensure there is at least a direct link toward the API documentation which may be already existing in the wiki. |