OOF Dublin RC1 Milestone Checklist

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.



Usage

  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 Area

Checkpoint

Yes/No

Evidences

How to?

Practice Area

Checkpoint

Yes/No

Evidences

How to?

Product Management

Are all tasks associated with the release been marked as "Closed" in Jira?

Yes

https://jira.onap.org/projects/OPTFRA/versions/10463



Have all findings from previous milestones been addressed?

Yes

We have addressed the coverage issue with optf/cmso, which is above 55% now

https://sonar.onap.org/dashboard?id=org.onap.optf.cmso%3Acmso



Development

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

No 

Getting issues...
  

Team is working towards fixing these. 



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

Yes

https://jenkins.onap.org/view/Merge-Jobs/

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

All repos are over 55% mark. 

optf-cmso: 56.4%

optf-has: 56.2%

optf-osdf: 65.0%

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.

Yes

HAS and OSDF have released version 1.3.0

CMSO 2.0.0 is progress with LF

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





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

All repos have at least 1 csit running on the OOM. 

OPTFRA-422: Move OOF projects' CSIT to run on OOM Closed



At RC0, has the Pair Wise testing table been filled out?

Yes

Integration Weather Board for Dublin Release

OOF Pair Wise Testing for Dublin Release

Our pairwise testing is blocked by the high priority defects listed above. 



At RC0, have all OOM Release Healtcheck related to your project passed?

Yes

T



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

Yes





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?

Not sure if the external lab job is running

Ensure in Jenkins External Labs all Health Check pass.



Has the project passed the Integration Sanity Tests?

No

This is blocked by the high priority defects listed above. 

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?

WIP

Likely to not complete by RC0, Plan to finish it by RC1

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 ?

WIP

Likely to not complete by RC1 due to other high priority RC0 leftovers, Plan to finish it by RC2

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

No



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