The following items are expected to be completed for the project to Pass the Release Candidate Milestone.

This template must be filled out for every Release Candidate Milestone (RC0, 1, 2, x)

RC Release Candidate Milestone overview is available in wiki.


Practice AreaCheckpointYes/NoEvidencesHow to?
Product ManagementAre all tasks associated with the release been marked as "Closed" in Jira?yes

Key Summary Reporter Status
Loading...
Refresh


Have all findings from previous milestones been addressed?yes

(warning) Resolution of outstanding vulnerabilities (inherited from PORTAL) deferred to El Alto

VID-471 - Getting issue details... STATUS


DevelopmentHave all Defects of priority Highest and High been in status "Closed" in Jira?yes

Getting issues...


Are all JIRA issues used as a reference in a commit in status "Closed" in Jira?yes
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.no2 pending commits are for non-Dublin branch.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)?yes

https://jenkins.onap.org/view/vid/job/vid-master-verify-java/

https://jenkins.onap.org/view/vid/job/vid-master-merge-java/

https://jenkins.onap.org/view/Merge-Jobs/
Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar)yes

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.

yeshttps://nexus.onap.org/content/repositories/releases/org/onap/vid/vid-parent/4.2.0/Refer to Independent Versioning and Release Process for procedure
Check the certification expiry of your application. It should be valid for the next 9 months after RC0.yes

Certificate valid until: March 12, 2020 (11 months)


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

yes

https://jenkins.onap.org/view/vid/job/vid-master-csit-healthCheck/

Build 1203 was a momentary hiccup in cloud.onap.org.


At RC0, has the Pair Wise testing table been filled out?yesVID Pair Wise Testing for Dublin Release
At RC0, have all OOM Release Healthcheck related to your project passed?yes

At RC0, is there a Docker image in Nexus Docker-Release repo available for each repository?yes

https://nexus3.onap.org/#browse/...


Has the project code successfully passed the Daily Build process?yes

(green star) Mitigation plan activated, thus reverted the Global-jjb maven migration changes.

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

Has the project passed the Integration Sanity Tests?

yes

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, does the project team has solved their JIRA Documentation Tickets?

If not, what are the risks?

yes

Pending closure:

Key Summary Reporter Status
Loading...
Refresh

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 RC1, has the team addressed all the remaining Documentation JIRA tickets ?yes
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 RC1, is the project prepared for the upcoming 'Ready to review'?yes
Documentation related patches should be reviewed by the documentation team to make sure everyone follows style guides.
For RC2, has the team addressed all the remaining Documentation JIRA tickets identified during the review?yes


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