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

Not clear what the scope of this question is. The features planned for the release have been submitted, but we still have some tasks to track and complete activities that need to be done for the release. Can you Clarify the scope of the question?




Have all findings from previous milestones been addressed?YesProvide link to JIRA findings
DevelopmentHave all Defects of priority Highest and High been in status "Done" in Jira?In-Progress

Provide link to JIRA issue (type bug) of priority Highest and High. 

Jira Legacy
serverSystem Jira
columnskey,summary,type

,created

,

updated,due,

assignee

,reporter

,priority,status

,resolution

maximumIssues20
jqlQueryproject = APPC AND issuetype = Bug AND status in (Open, "In Progress", REOPENED, Submitted, Delivered) AND priority in (Highest, High)
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176


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

Provide link to "Merge job" as evidence in Jenkins project tab

The daily, verify, and merge jobs pass successfully.

There is one job for javadocs that has dependency on CCSDK issue resolution to build successfully. Being tracked under: APPC-266


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.

Yes (to staging)
Refer 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".

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


Is there a Docker images available for each repository?Yes

Provide link to evidence

https://nexus3.onap.org/#browse/browse/components:docker.public:c60bc6b9612f47d36dd8785b970c3679:cf606f82560ea906419de3052fbb1cf5


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

Yes

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?