The following items are expected to be completed for the project to Pass the M2 Functionality Freeze Milestone.
M2 Release Functionality Freeze Milestone definition.
| Practice Area | Checkpoint | Yes/No | Evidence - Comment | How to? | |
|---|---|---|---|---|---|
| Product Management | Are all provisional APIs interface (stub) been defined (at beta-quality level)? | Yes | APIs are documented on the following ONAP wiki page : SDNC APIs | ||
| Is there a final list of externally consumable APIs available? | No | API definition is in progress and will probably change before final consumable versionYes | APIs are documented on the following ONAP wiki page : SDNC APIs | ||
For all completed Sprints, have Sprint Backlog Stories been marked as "Done" in Jira? | N/A | First sprint in progress | Difference between a Product and Sprint Backlog | ||
Are all tasks associated with the completed Sprint Backlog Stories been marked as "Done" in Jira? | N/A | ||||
| 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). | No | The plan is to dedicate the first sprint to close up design details and API details for the final implementation | Link to blockers. | ||
| 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 | Was addressed in seed code contribution. | Guidance on year format | ||
| 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 | Main LICENSE.txt available at the root of the project | Guidance for source code file that can't be edited | ||
| Has the project FOSS Table been updated with latest third party code? | Yes | Software Defined Network Controller FOSS page | Your project FOSS table is located under Project FOSS master page | ||
| Do you have a plan to address any issue raised by FOSSology? | N/A | No issue raised by FOSSology (was run internally at AT&T) before publishing the code | |||
Have all API projects dependencies been captured? | Yes | link to the "API Incoming Dependency" section within your project M1 Release Planning deliverable. | 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 | |||
| Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | No | In progress | |||
| 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. | No | As discussed between AT&T Legal & LF council, the removal of trademark and company name is not applicable to AT&T. | |||
| Is there any pending commit request older than 36 business hours in Gerrit? | No | ||||
| Have all the Jenkins jobs successfully passed (Merge-Jobs)? | Yes | ||||
| Are all snapshot binaries available in Nexus? | Yes | link to Nexus project folder | |||
| Integration and Testing | Have functional test cases been documented in wiki? | Yes | SDNC : Beijing Release - M2 : Functional Test cases | ||
| Have you implemented in Jenkins at least 1 functional test case for each of the project repository? | No | In progress | 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 | These are captured in stories in planned sprints |