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.



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

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = "Active and Available Inventory" and fixVersion = "Casablanca Release" and status != Closed
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

Bugs are all late-breaking issues opened as part of CCVPN testing. The rest are minor related to documentation, no features outstanding.



Have all findings from previous milestones been addressed?Yes


Provide link to JIRA findings


DevelopmentHave all Defects of priority Highest and High been in status "Closed" in Jira?NoProvide link to JIRA issue (type bug) of priority Highest and High. Yes

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = "Active and Available Inventory" and fixVersion = "Casablanca Release" and type = "Bug" and status != Closed and (priority = High or priority = highest)
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176


Are all JIRA issues used as a reference in a commit in status "Closed" in Jira?NoYes
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

Are all the Jenkins jobs successfully passed (verify + merge jobs)?YesProvide link to "Merge job" as evidence in Jenkins project tabMerge Jobs

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.

YesONAP NexusRefer to Independent Versioning and Release Process for procedure
Integration and TestingHave all CSIT Use Cases (created by each project team) passed?Yes

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

Jenkins CSIT


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

Casablanca Pair Wise Testing master page

A&AI Pair Wise Testing for Casablanca 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?YesProvide link to evidenceNexus
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?YesEnsure in Jenkins External Labs all Health Check pass.

Has the Heat deployment passed?

(not a gating item for Casablanca)

YesEnsure in Jenkins External Labs all Health Check pass.
Documentation

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


Yes

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 RC1, has the team addressed any issue (recorded in JIRA) provided by the Documentation team?

N/A

For RC2, for project delivering binaries, has the team populated and validated all the sections of the Release Notestemplate?

WIP

For RC2, has the Documentation Team provided the final approval for your project documentation?