Skip to end of metadata
Go to start of metadata


The following items are expected to be completed for the project to Pass  Release Sign-Off Milestone.

Release Sign-Off Milestone overview is available in wiki.


  1. Use the "Copy" and "Move" options (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 ManagementAre committed Product Backlog Stories been coded and marked as "Done" in Jira?YesLink to Jira
Are all tasks associated with committed Product Backlog Stories been marked as "Done" in Jira?YesLink to Jira
Provide the project features list under the form of a bulleted list.YesLink to evidence
  • Retrieve service specification available (to build product accordingly) or get detailed catalog information on a service specification,
  • Send service order to ONAP in order to fulfill customer productOrder (BSS make product-service decomposition), order could very simple a more complex with multiple requests & dependencies,
  • Have update on these orders (retrieve order status for example),
  • Retrieve service assets for a customer (of from another available criteria),
  • Get all information of a service asset.

Summarize any functionalities that were planned at Release planning and not delivered at Release Sign-Off


Only 'nice to have' feature not delivered:

  • Notification management
Release ManagementHave all issues pertaining to FOSS been addressed?Yes

Have all findings from previous milestones been addressed?YesProvide link to JIRA findings
DevelopmentAre all the Jenkins jobs successfully passed (verify + merge jobs)?Yes

Are all binaries available in Nexus Release repository?YesProvide link to evidence
Are all Docker images available In Nexus?YesProvide link to evidence
Are the Java and Docker manifest updated with the same version as in Nexus Release repository?Yes

Integration and Testing

Have all CSIT Use Cases (created by each project team) passed?YesProvide link to evidence

Goal is to increase our confidence the latest commit did not break the major functionality. Jenkins CSIT Jobs

Has the project code successfully passed the Daily Build process?YesProvide link to evidenceGoal is to ensure the latest project commit has not broken the Integration Daily Build 

Has the project done the integration testing with related dependent projects?



Has your team contributed and completed work in the following documentations in ReadTheDocs:

  1. Release Notes
  2. Project Documentation

Provide Link to ReadTheDocs Release Notes

Provide Link to ReadTheDocs Project Documentation

releases notes:

Project documentation: