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 JiraN

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-54
Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-61

Work has been done but not tested yet due to DCAEGEN2-127 and 128.

Have all findings from previous milestones been addressed?Provide link to JIRA findingsY

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. N

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-127
Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-128

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-175

127 and 128 have been taking long to resolve because of the Designate availability issue.

175 is delivered, but waiting to be tested, which needs an environment that is blocked by 127 and 128.

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 successfulN

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-127
Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-128

Because these two bug tickets have not been resolved yet. These two issues have not been closed.
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.N

Are all the Jenkins jobs successfully passed (verify + merge jobs)?Yhttps://jenkins.onap.org/view/dcagen2/

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.

Y

curl -s https://nexus.onap.org/service/local/repositories/raw/content/ |grep "<text>org.onap.dcaegen2"

Result:

      <text>org.onap.dcaegen2.deployments</text>

      <text>org.onap.dcaegen2.platform.blueprints</text>

      <text>org.onap.dcaegen2.analytics</text>

      <text>org.onap.dcaegen2.platform.plugins</text>

      <text>org.onap.dcaegen2.utils</text>

Refer to Independent Versioning and Release Process for procedure
Integration and TestingHave all CSIT Use Cases (created by each project team) passed?Yhttps://jenkins.onap.org/view/CSIT/job/dcaegen2-master-csit-testsuites/
Is there a Docker images available for each repository?Y

curl -X GET https://nexus3.onap.org:10001/v2/_catalog | python -m json.tool |grep dcaegen2

Result:

        "onap/org.onap.dcaegen2.collectors.ves.vescollector",

      "onap/org.onap.dcaegen2.dcaegen2.platformdoc",

        "onap/org.onap.dcaegen2.deployments.bootstrap",

        "onap/org.onap.dcaegen2.platform.cdapbroker",

        "onap/org.onap.dcaegen2.platform.configbinding",

        "onap/org.onap.dcaegen2.platform.deployment-handler",

        "onap/org.onap.dcaegen2.platform.inventory-api",

        "onap/org.onap.dcaegen2.platform.policy-handler",

        "onap/org.onap.dcaegen2.platform.servicechange-handler",


Has the project code successfully passed the Daily Build process?Yhttps://jenkins.onap.org/view/dcagen2/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?




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?

Y

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?