Skip to end of metadata
Go to start of metadata

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 "Done" in Jira?Yes

Getting issues... - Closed Tasks

Getting issues... - Sanity check for Open Tasks

The remaining tasks are for documentation and release planning purposes.

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 "Done" in Jira?Yes

Getting issues... (should be zero)

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

Are all the Jenkins jobs successfully passed (verify + merge jobs)?Yes

Has the team delivered all their release artifacts in Nexus Release or Nexus Staging repo?

There should be at least ONE version of each artifacts available in Nexus Release or Nexus Staging repo.

YesDelivered v1.2.0 artifactsRefer to Independent Versioning and Release Process for procedure
Integration and TestingHave all CSIT Use Cases (created by each project team) passed?Yes

Is there a Docker images available for each repository?Yes

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

We released v1.2.0 last week.

When we upgrade our SNAPSHOT to 1.2.1 then our release jobs will fail due to dependencies between repos that require released artifacts.

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 Heat deployment passed?YesEnsure in Jenkins External Labs all Health Check pass.

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


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?


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


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