Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Practice AreaCheckpointYes/NoEvidencesHow to?
Product ManagementAre all tasks associated with the release been marked as "Done" in Jira?Link to JiraYes


Have all findings from previous milestones been addressed?Provide link to JIRA findingsin progressReach 50% Unit test coverageCurrent status 43% due to other priorities expected from the SDC team i.e. DM Certification, support use cases testing etc. Please note that the Beijing code is at 50% but additional investment will be performed to increase test coverage related to 'seed code' (prior Beijing). Waiver is requested for Beijing.
DevelopmentHave all Defects of priority Highest and High been in status "Done" in Jira?Provide link to JIRA issue (type bug) of priority Highest and High. Yes

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDC-1336

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDC-1332

Are all JIRA issues used as a reference in a commit in status "Done" in Jira?Very often, some JIRA issue remains in status "Todo" in JIRA while the commit they are referenced to is successful.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.Yes
commits pending sign off
Are all the Jenkins jobs successfully passed (verify + merge jobs)?Provide link to "Merge job" as evidence in Jenkins project tabYes

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/


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
Refer to Independent Versioning and Release Process for procedure
Integration and TestingHave all CSIT Use Cases (created by each project team) passed?Provide link to evidence. As things are moving fast, we want to ensure CSIT are still "green".Yes

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

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

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

Is there a Docker images available for each repository?Provide link to evidenceYes
https://nexus3.onap.org/#browse/search=keyword%3Dsdc%20AND%20version%3D1.2-STAGING-latest
Has the project code successfully passed the Daily Build process?Goal is to ensure the latest project commit has not broken the Integration Daily Build Yes

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




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?

In progresss

For RC2, has the Documentation Team provided the final approval for your project documentation?N/ADocumentation team does not provide approval for our documentation; I'm not aware of new documentation requirements in Beijing.


sdc all repo querey