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 | 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? | Yes | |||
| 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 | Proofs have been provided for SONAR and CSIT to get the M2 and M3 passed. | 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 | Getting issues... | |
| 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 | 1.0.0 old release branch jobs started failing due to some changes in the Jenkins settings which are meant for long term maintenance. The 1.0.0 is seed code of very first release and the packaged docker images of that initial version work perfectly fine for the community. So, we did not find any reason to spend our resources just to fix the Jenkins jobs (as we do not have any code changes in that old branch). | ||
| Are all snapshot binaries available in Nexus? | Yes | https://nexus.onap.org/#nexus-search;quick~portal/sdk | ||
| Do you have a clear plan to implement the Independent Versioning and Release Process by RC0? | Yes | We use 1.3-STAGING-latest for docker images. Portal-SDK artifacts version 1.3.0 are released. | 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? | In-Progress | 100% tests implemeneted. But, the CSIT tests are failing due to chrome browser and cross domain cookie support issues - LF ticket is opened for help - "ONAP Helpdesk #46086AutoReply: Portal CSIT tests require hostname URL to support cross domain cookies" | |
| Is there a Docker images available for your project deliverable? | No | We don't have any docker image related to integration and testing. | ||
| Has the project code successfully passed the Daily Build process? | In-Progress | Dependent on the browser issue - ONAP Helpdesk #46086 | 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/portal.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 | Portal APIs | Ensure there is at least a direct link toward the API documentation which may be already existing in the wiki. |
