|Practice Area||Checkpoint||Yes/No||Evidence - Comment||How to?|
Are all provisional APIs interface (stub) been defined (at beta-quality level)?
Reboot command details available here until readthedocs is updated: R3 API Documents
All other supported APIs available here: API Guide
|Is there a final list of externally consumable APIs available?||Yes||http://onap.readthedocs.io/en/latest/submodules/appc.git/docs/APPC%20LCM%20API%20Guide/APPC%20LCM%20API%20Guide.html|
For all completed Sprints, have Sprint Backlog Stories been marked as "Done" in Jira?
|Yes||APPC Board||Difference between a Product and Sprint Backlog|
Are all tasks associated with the completed Sprint Backlog Stories been marked as "Done" in Jira?
Sprint 0 completed
Sprint 1 active and completes on 7/25
|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).||None defined at this time|
Risks documented here: Casablanca Risks
|What new features or changes to existing features in this project scope need to be communicated to VNF Providers? List the changes in the Evidence tab.||NoN/A|
|If yes to the previous question, have these been communicated to the VNF Requirements project?||N/A|
|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 2018 and existing files modified in 2018 are different)||N/A||Clarification from LF provided that this is not mandatory. Confirmed with Gildas also. However, year is updated as files are updated for development work.|
|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||Guidance for source code file that can't be edited|
|(a) Has the Project Team added appropriate license and copyright notices to all ONAP source code and documentation files, where possible for the particular file format?||Yes|
|(b) Has the Project Team reviewed and understood the most recent license scan reports from the LF, for both (a) licenses within the codebase and (b) licenses for third-party build time dependencies?||Yes|
|For both (a) and (b) questions, have all high priority non-Project Licenses been either removed, planned for removal before code freeze, or escalated as likely exception requests?||Yes|
Have all API projects dependencies been captured?
|Yes||Incoming Dependencies||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|
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||Goal is 50%|
Guidance on Code Coverage and Static Code Analysis
|Is there any binaries (jar, war, tar, gz, gzip, zip files) in Gerrit project repository?||No||Refer to CI Development Best Practices|
|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|
|Is there any pending commit request older than 36 business hours in Gerrit?||No||Note: There are some gerrit's status is draft, which will be done by sprint 2 (8/10/2018)|
|Have all the Jenkins jobs successfully passed (Merge-Jobs)?||NoDue|| to nexus iq plug in issue in Jenkins. and Jenkins server is not stable|
Work in progress to address:
This in an ongoing effort as code is churned, transient failures will be seen depending on when you check Jenkins as project progresses.
|Are all snapshot binaries available in Nexus?||Yes||Provide link to evidence in Nexus project folder|
|Integration and Testing||Have functional test cases been documented in wiki?||Yes||Delivered Original set delivered as part of Amsterdam and documented there; new ones will be added as capacity allowsare being added under: APPC-1091|
|Have you implemented in Jenkins at least 1 functional test case for each of the project repository?||Yes|
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|