Versions Compared

Old Version 1

changes.mady.by.user Gildas Lanilis

Saved on

compared with

New Version Current

changes.mady.by.user Catherine Lefevre

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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.


Info
titleUsage
  1. Use the "Copy and Paste this template in the wiki Space along with your Release Planning document" 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
Closed" in Jira?
Link to Jira
Are all tasks associated with committed Product Backlog Stories been marked as "
Done
Closed" in Jira?
Link to Jira
Provide the project features list under the form of a bulleted list.
Link to evidence

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




Release ManagementHave all issues pertaining to FOSS been addressed?


Have all findings from previous milestones been addressed?
Provide link to JIRA findings
Development
Is there any pending commit request older than 24 hours in Gerrit?
Are all the Jenkins jobs successfully passed (verify + merge jobs)?

https://jenkins.onap.org/view/Merge-Jobs/
Are all binaries available in Nexus Release repository?
Provide link to evidence
Are all Docker images available In Nexus?
Provide link to evidence
Are the Java and Docker manifest updated with the same version as in Nexus Release repository?


OOM to Tag Release + Version in Helm Chart


Integration and Testing

Have all CSIT Use Cases (created by each project team) passed?

Provide link to evidenceHas your project completed the end-to-end CSIT Use Case?Provide link to evidence


It should include at least 1 CSIT that will be run on


Lab-xxx-OOM-Daily Jenkins Job


Provide link to evidence
Is there a Docker images available for each repository?
Goal is to incease our confidence the latest commit did not break the major functionality. Jenkins CSIT Jobs
Has the project code successfully passed the Daily Build process?
Provide link to evidenceGoal is to ensure the latest project commit has not broken the Integration Daily Build 
Have you checked with Integration Team if your project's deliverable have successfully passed the Community Lab
Has the project passed the Integration Sanity Tests

Integration sanity tests in Dublin Release cover:

  • ONAP deployment
  • All components health check
  • VNF onboarding and service creation for vFW use case
  • Model distribution for vFW
  • vFW instantiation
  • vFW closed loop
  • vFW deletion

No test failure reported on http://onapci.org/grafana/d/8cGRqBOmz/daily-summary?orgId=1

No Integration Blocking Issue with no workaround: Dublin Release Integration Test Blocking Issues

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




Documentation

Has your team

contributed and completed work in the following 3 documentations:

completed (reviewed, submitted and cherry picked) all documentation planned for the Dublin Release?

  1. Release Notes
  2. Project Documentation
  3. No remaining Documentation tickets

Provide Link to ReadTheDocs Release Notes

Provide Link to ReadTheDocs Project Documentation

JIRA Query

project != "Sandbox Project" AND project != "ONAP TSC" AND project != CI-Management AND (labels=Documentation OR project=Documentation) AND status != Closed ORDER BY fixVersion ASC, status DESC, priority DESC, updated DESC
  • Mercury Release Notes
  • Mercury Tarball Installation
    • Mercury Docker Installation