Versions Compared

Key

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

...

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

RC Release Candidate Milestone overview is available in wiki.


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?Yes

Jira Legacy
serverSystem Jira
jqlQueryproject = MULTICLOUD and fixVersion = "Dublin Release" AND status in ("In Progress", Open) AND type = Story ORDER BY priority DESC, updated DESC
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176


Have all findings from previous milestones been addressed?N/AProvide link to JIRA findings
DevelopmentHave all Defects of priority Highest and High been in status "Closed" in Jira?No

Jira Legacy
serverSystem Jira
jqlQueryproject = MULTICLOUD and type=Bug and (priority =High OR priority=Highest ) and resolution = Unresolved order by priority DESC,updated DESC
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176


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.No
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)?Yeshttps://jenkins.onap.org/view/multicloud/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)No

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.

No

Not sure why each project repo can only release 1 artifact , need follow up with LF helpdesk

[ONAP Helpdesk #71309]

Only k8s plugin is not yet releasing the docker imageRefer 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

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

Provide link to evidence. As things are moving fast, we want to ensure CSIT are still "green".

https://jenkins.onap.org/view/multicloud/


At RC0, has the Pair Wise testing table been filled out?YesIntegration Weather Board for Dublin Release
At RC0, have all OOM Release Healtcheck related to your project passed?Yes

At RC0, is there a Docker image in Nexus Docker-Release repo available for each repository?yesYeshttps://nexus3.onap.org/#browse/search=keyword%3Dmulticloud
Has the project code successfully passed the Daily Build process?Yes
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?

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?

No

Will do in RC1

Jira Legacy
serverSystem Jira
jqlQueryproject =Multicloud 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
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

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 ?

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'?

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?


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

...