DCAE R1 M2 (Functionality Freeze) Check List
- Lusheng Ji
Practice Area | Checkpoint | Yes/No | Evidence - Comment | How to? |
|---|---|---|---|---|
Product Management | Are all provisional APIs interface (stub) been defined (at beta-quality level)? | Y | ||
Is there a final list of externally consumable APIs available? | Y | |||
For all completed Sprints, have Sprint Backlog Stories been marked as "Done" in Jira? | Y | https://jira.onap.org/browse/DCAEGEN2-12?jql=text%20~%20%22backlog%22 | ||
Are all tasks associated with the completed Sprint Backlog Stories been marked as "Done" in Jira? | Y | https://jira.onap.org/browse/DCAEGEN2-12?jql=text%20~%20%22backlog%22 | ||
If applicable to your project, has your team been able to clear the project' blockers? If not provide status on the plan to close the blocker(s). | All but 1 (B30 Pypi) | We responded to blockers that can be cleared. Some we cannot because these blockers are blocked by other teams. (blockers B25-B27) | ||
Release Management | Have all source code files been updated with License Apache 2 header? | Yes | Specific rules and instruction are available in ONAP wiki. | |
Has the year format in copyright header of all source code files been updated? (Rules for new files created in 2017 and existing files modified in 2017 are different) | Yes | |||
In case source code can't be edited, has a "License.txt" file been placed at the root directory for which the license is applicable? | Yes | |||
Has the project FOSS Table been updated with latest third party code? | Y | Your project FOSS table is located under Project FOSS master page | ||
Do you have a plan to address any issue raised by Fossology? | Y | option 1: remove offending text if possible; option 2: replace copyleft dependencies with open source friendly equivalents; option 3: design packaging methods so that the questionable dependencies are only installed at end-user deployment time | ||
Have all API projects dependencies been captured? | Yes | The source of information for the API dependency is the "API Incoming Dependency" of the M1 Release Planning deliverable. Please update the source accordingly, and let The Release Manager aware of the changes. | ||
Development | For new projects approved for this release, have all defined repositories source code been placed into Gerrit? | Yes | We are in the process of cleaning company specific logo/keyword, etc. | For evidences, provide link(s) to Gerrit repos by providing the URL as shown in this example |
Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | Yes (Updated 08/23: no for dcaegen2 code due to integration issues between mvn and python) | Goal: 30-50% for Incubation project | ||
Is there any binaries (jar, war, tar, gz, gzip, zip files) in Gerrit project repository? | Yes. | There are a number of data files under the dcae/demo/startup/message-router repo. But since for R1 DMaaP project will take over this part of the code, this repo will be deprecated. We will delete the data files after transitioning to DMaaP project is complete. | ||
Could you ensure that all proprietary trademarks, logos, product names, company name, etc. have been removed? All ONAP deliverables must comply with this rule and be agnostic of any proprietary symbols. | Yes | With the exception that company name remains in copy right statement, and trademark (ECOMP, OpenECOMP) and service mark statement. | ||
Is there any pending commit request older than 36 business hours in Gerrit? | No | |||
Have all the Jenkins jobs successfully passed (Merge-Jobs)? | Yes | https://jenkins.onap.org/view/dcae/ | ||
Are all snapshot binaries available in Nexus? | Yes | https://nexus.onap.org/content/repositories/snapshots/org/openecomp/dcae/ | ||
Integration and Testing | Have functional test cases been documented in wiki? | Yes | ||
Have you implemented in Jenkins at least 1 functional test case for each of the project repository? | No | As an evidence, provide a link to Jenkins (CSIT Jobs) that shows a sample test case implemented (1 job for each repo). | As an example (provided by Integration Team) | |
Has the project code successfully passed the Build process? | Yes | Goal is to ensure your project latest commits have not broken the build. | ||
Documentation | Has the team identified and outlined the set of documentations to be delivered in this Release? | Yes |