APPC Dublin RC0 Milestone Checklist Template

DRAFT PROPOSAL FOR COMMENTS

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

Getting issues...



Have all findings from previous milestones been addressed?

N/A

no new findings from M4



Development

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

In Progress

APPC-1576: FileParameters content is wrongly processedClosed reopened, gerrit is ready for submit.

others are delivered or closed (4/30/2019)



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

all APPC's merge + verify jobs all passed

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

83.8% as of 4/26/2019

https://sonar.onap.org/component_measures?id=org.onap.appc%3Aappc&metric=line_coverage

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.

In progress

dublin branch created, docker release in progress (4/30/2019)

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

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?

In Progress

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

In progress

Provide link to evidence



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?

yes

Ensure in Jenkins External Labs all Health Check pass.



Has the project passed the Integration Sanity Tests?

yes

https://jenkins.onap.org/view/integration/ all passed that is what I am seeing.

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

All JIRA ticket related to Documentation will be closed and finished 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 ?

N/A

this is for RC1 question

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

N/A

this is for RC1 question

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?

N/A

this is for RC2 question

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