Skip to end of metadata
Go to start of metadata

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

  1. Use the "Copy" option (available under the ..., top right of this page) to duplicate this template into your project wiki.
  2. Fill out the Yes/No column
  3. Provide link to evidence (when necessary)
Practice AreaCheckpointYes/NoEvidencesHow to?
Product ManagementHave 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.



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


Sprint View

Getting issues...



Are all tasks associated with committed Sprint Backlog Stories been marked as "Done" in Jira?

Yes



Release ManagementHave all issues pertaining to FOSS been addressed?Yes

Have all findings from previous milestones been addressed?YesFor M2 and M3 Milestones, ensure all findings have been closed.
DevelopmentAre all Defects of priority Highest and High in status "Done" in Jira?YesProvide 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
Are all snapshot binaries available in Nexus?Yeshttps://nexus.onap.org/index.html#view-repositories;snapshots~browsestorage~/org/onap/dmaap/messagerouter
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 TestingHave 100% of Continuous System Integration Testing (CSIT) Use Cases been implemented successfully in Jenkins?Yes

https://jenkins.onap.org/view/dmaap/job/dmaap-master-csit-mrpubsub/1/console


Is there a Docker images available for your project deliverable?Yeshttps://nexus3.onap.org/#browse/search=keyword%3Ddmaap:c60bc6b9612f47d3dc659d59cfa199b9
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 
DocHas the team created a documentation Template in ReadTheDocs?Yeshttp://onap.readthedocs.io/en/latest/submodules/dmaap/messagerouter/messageservice.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

How to setup the template for my project?

Is the API documentation section poplulated?Yes

DMaaP API

http://onap.readthedocs.io/en/latest/submodules/dmaap/messagerouter/messageservice.git/docs/index.html

Ensure there is at least a direct link toward the API documentation which may be already existing in the wiki.