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.


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


Have all findings from previous milestones been addressed?in progressReach 50% Unit test coverage
DevelopmentHave all Defects of priority Highest and High been in status "Done" in Jira?In progress

SDC-1273 - Getting issue details... STATUS

SDC-1249 - Getting issue details... STATUS


Are all JIRA issues used as a reference in a commit in status "Done" in Jira?yes

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.Yessdc all repo querey
Are all the Jenkins jobs successfully passed (verify + merge jobs)?yes

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

https://jenkins.onap.org/view/sdc-jtosca/

https://jenkins.onap.org/view/sdc-sdc-distribution/

https://jenkins.onap.org/view/sdc-sdc-titan/

https://jenkins.onap.org/view/sdc-sdc-tosca/

https://jenkins.onap.org/view/sdc-sdc-workflow/

docker base is failing at the moment.

not an issue because release versions have been created.

SDC-1222 - Getting issue details... STATUS


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

the docker relase job is failing

ONAP Helpdesk #55386

Integration and TestingHave all CSIT Use Cases (created by each project team) passed?Yes

https://jenkins.onap.org/view/sdc/job/sdc-master-csit-nightly-testng/233/

https://jenkins.onap.org/view/sdc/job/sdc-master-csit-sanity-testng/596/

https://jenkins.onap.org/view/sdc/job/sdc-master-csit-uiSanity-testng/30/

Is there a Docker images available for each repository?yes
https://nexus3.onap.org/#browse/search=keyword%3Dsdc%20AND%20version%3D1.2-STAGING-latest
Has the project code successfully passed the Daily Build process?N\A


Has the OOM deployment passed?in progressEnsure in Jenkins External Labs all Health Check pass.

latest external deploy did not start the sdc dockers.

based on integration team inputs the sdc starts successfully using heat deployment in windreiver lab sb07.

Has the Heat deployment passed?in progressEnsure in Jenkins External Labs all Health Check pass.

latest external deploy successfully deployed sdc and it started correctly with no intervention.

however it looks like there is a timing issue between when the difrent pods start and the health check is exacuted.

based on integration team inputs the sdc starts successfully using OOM deployment win driver labs sb04.

Documentation

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





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?