Versions Compared

Key

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

...

Info
titleUsage
  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 all tasks associated with the release been marked as "Closed" in Jira?
Link to Jira

Have all findings from previous milestones been addressed?
Provide link to JIRA findings
DevelopmentHave all Defects of priority Highest and High been in status "Closed" in Jira?
Provide link to JIRA issue (type bug) of priority Highest and High. 
Are all JIRA issues used as a reference in a commit in status "Closed" in Jira?

Very often, some JIRA issue remains in status "Todo" in JIRA while the commit they are referenced to is successful.
Is there any pending commit related to Highest and High priority issues older than 36 hours in Gerrit? In case there are messages going back and forth between authors and reviewers, it is acceptable to be above 36 hours.

Gerrit Query: status:open label:verified -is:draft -label:Code-Review=-1 AND -label:Code-Review=-2  AND is:mergeable age:1week
Are all the Jenkins jobs successfully passed (verify + merge jobs)?
Provide link to "Merge job" as evidence in Jenkins project tabhttps://jenkins.onap.org/view/Merge-Jobs/
Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar)

Sonar

Guidance on Code Coverage and Static Code Analysis

Tools: Sonar

Has the team delivered all their release artifacts in Nexus Release repo?

There should be at least ONE version of each artifacts available in Nexus Release repo.



Refer to Independent Versioning and Release Process for procedure
Integration and Testing

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


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


Lab-xxx-OOM-Daily Jenkins Job


Provide link to evidence. As things are moving fast, we want to ensure CSIT are still "green".
At RC0, has the Pair Wise testing table been filled out?
Casablanca Pair Wise Testing master page
At RC0, have all OOM Release Healtcheck related to your project passed?


At RC0, is there a Docker image in Nexus Docker-Release repo available for each repository?
Provide link to evidence
Has the project code successfully passed the Daily Build process?

Goal is to ensure the latest project commit has not broken the Integration Daily Build 
Has the OOM deployment passed?
Ensure in Jenkins External Labs all Health Check pass.

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

Documentation

For RC0, for project delivering binaries, has the team populated and validated all the sections of either the Platform Component or SDK template?




Most teams have already created the high level file structures in readthedocs, and populated some actual documentation. However, the remaining sections of the appropriate teamplate must be completed.

Platform: A&AI, APP-C, CLAMP, CLI, DCAE, DMaaP, Holmes, MSB, OOM, Policy, Portal, SDN-C SDC, SO, UseCase UI, VFC, VID

SDKs: AAF, CCSDK, External API Framework, Multi VIM/Cloud, VNFSDK

For RC0, does the project team has solved their JIRA Documentation Tickets considered as "Bugs"?

Jira Query (Bugs Only)

project != "Sandbox Project" AND project != "ONAP TSC" AND project != CI-Management AND (labels = Documentation OR project = Documentation) AND issuetype= Bug AND  fixversion = "Dublin Release" AND status != Closed ORDER BY issuetype DESC, fixVersion ASC, status DESC, priority DESC, updated DESC

For RC0, Does the project team has any risk to close all the Release documents by RC1?


For RC1, has the team addressed

any issue (recorded in JIRA) provided by the Documentation team?

all the remaining Documentation JIRA tickets ?



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

For RC2, for project delivering binaries, has the team populated and validated all the sections of the Release Notestemplate i.e. Code merge on the Master then cherry picked on the Release.




For RC2, has the team addressed all the remaining Documentation JIRA tickets identified during the review with the Documentation project?

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
For RC2, has the Documentation Team provided the final approval for your project documentation?