DRAFT PROPOSAL FOR COMMENTS
The following items are expected to be completed for the project to Pass the M2 Functionality Freeze Milestone.
M2 Release Functionality Freeze Milestone definition.
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 | Evidence - Comment | How to? |
|---|---|---|---|---|
| Product Management | Are all provisional APIs interface (stub) been defined (at beta-quality level)? | Yes | AAF API | |
| Is there a final list of externally consumable APIs available? | Yes | AAF API | ||
For all completed Sprints, have Sprint Backlog Stories been marked as "Done" in Jira? | Yes | Difference between a Product and Sprint Backlog | ||
Are all tasks associated with the completed Sprint Backlog Stories been marked as "Done" in Jira? | Yes | https://jira.onap.org/secure/RapidBoard.jspa?rapidView=69&view=planning&selectedIssue=AAF-37&versions=visible&epics=visible | ||
| 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). | N/A | Link to blockers. | ||
| Release Management | Have all source code files been updated with License Apache 2 header? | Yes | https://gerrit.onap.org/r/#/admin/projects/aaf/authz | 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 | 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 | Guidance for source code file that can't be edited | ||
| Has the project FOSS Table been updated with latest third party code? | Yes | Application Authorization Framework | ||
| Do you have a plan to address any issue raised by Fossology? | N/A | No issue raised by FOSSology. Fossology was run internally at AT&T before publishing the code | ||
Have all API projects dependencies been captured? | N/A | AAF does not depend on any other project. | N/A | |
| Development | For new projects approved for this release, have all defined repositories source code been placed into Gerrit? | Yes | http://gerrit.onap.org/r/aaf/authz | |
| Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | Work in progress. | Once Jenkins job is set up with Sonar, we will update % coverage. | ||
| 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? | Yes. | We have one commit which has to be reviewed. | ||
| Have all the Jenkins jobs successfully passed (Merge-Jobs)? | No. Work in Progress | We pushed Jenkins Job Builder file to gerrit-repo. It needs to be reviewed by ci-management team. | ||
| Are all snapshot binaries available in Nexus? | No. Work in Progress | Once jenkins job is setup, we will work on releasing artifacts to Nexus. | ||
| Integration and Testing | Have functional test cases been documented in wiki? | Yes | AAF R1 Amsterdam Release - M2 Functional Test cases | |
| Have you implemented in Jenkins at least 1 functional test case for each of the project repository? | No | It is planned as part of M3 (50%)/M4 (100%) milestone | As an example (provided by Integration Team) | |
| Has the project code successfully passed the Build process? | No.In Progress | We pushed Jenkins Job Builder file to gerrit-repo. It needs to be reviewed by ci-management team. | 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 | AAF-55 - Getting issue details... STATUS |