Skip to end of metadata
Go to start of metadata

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 AreaCheckpointYes/NoEvidencesHow to?
Product ManagementAre all tasks associated with the release been marked as "Done" in Jira?NoThe current sprint has not finished yet thus not all tasks are marked as done. But things are going smoothly as planned.

Have all findings from previous milestones been addressed?NANo findings were found except for the vulnerability issues mentioned in Holmes Security/Vulnerability Threat Impact Analysis
DevelopmentHave all Defects of priority Highest and High been in status "Done" in Jira?Yes

Getting issues...


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)?Yeshttps://jenkins.onap.org/view/Merge-Jobs/

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.

YesHolmes ArtifactsRefer to Independent Versioning and Release Process for procedure
Integration and TestingHave all CSIT Use Cases (created by each project team) passed?YesProvide link to evidence. As things are moving fast, we want to ensure CSIT are still "green".
Is there a Docker images available for each repository?YesHolmes Dockers
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?NAHolmes has no OOM deployment approach. So this item is not applicable for Holmes
Has the Heat deployment passed?NAHolmes is deployed as a DCAE app. Its health check is done within DCAE. In the Intel lab, the health check done by DCAE Consul is OK. Helen is working with the DCAE team, trying to set up a health check thread for Holmes. But no feedback has been heard from her yet.
Documentation

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?