DACE R1 RC1 Milestone Checklist
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
Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki.
Fill out the Yes/No column
Provide link to evidence (when necessary)
Practice Area | Checkpoint | Yes/No | Evidences | How to? |
---|---|---|---|---|
Product Management | Are all tasks associated with the release been marked as "Done" in Jira? | N | DCAEGEN2-54: Onboarding HOLMESClosedDCAEGEN2-61: CLAMP integration support for R1 usecaseClosed | Work has been done but not tested yet due to DCAEGEN2-127 and 128. |
Have all findings from previous milestones been addressed? | Y | |||
Development | Have all Defects of priority Highest and High been in status "Done" in Jira? | N | DCAEGEN2-127: DCAE Controller startup not working in dcae2_install.sh ClosedDCAEGEN2-128: fix integration issues for DCAEGEN2Closed DCAEGEN2-175: vFirewall Integration Testing - DCAE sending vnf-name instead of vnf-idClosed | 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? | N | DCAEGEN2-127: DCAE Controller startup not working in dcae2_install.sh ClosedDCAEGEN2-128: fix integration issues for DCAEGEN2Closed | 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)? | Y | |||
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 Testing | Have all CSIT Use Cases (created by each project team) passed? | Y | https://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? | Y | 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 Notes template? | ||||
For RC2, has the Documentation Team provided the final approval for your project documentation? |