...
M2 Release Functionality Freeze Milestone definition.
| Practice Area | Checkpoint | Yes/No | Evidence - Comment | How to? |
|---|
Product | Product Management | Are all provisional APIs interface (stub) been defined (at beta-quality level)? |
|
|
|
| Is there a final list of externally consumable APIs available? |
| Provide link to evidence |
|
For all completed Sprints, have Sprint Backlog Stories been marked as "Done" in Jira? |
| Provide Link to Project backlog |
Policy R1 Deliverables for Functionality Freeze Milestone Checklist TemplateHas all Product Backlog not implemented in current release been scoped for next release? | Provide link to issue scoped for next release |
|
|
|
|
|
|
|
Release Management
| Have all source code files been updated with License Apache 2 header? |
Definition of Source code file |
|
|
|
| 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) |
|
| 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? |
|
| Guidance for source code file that can't be edited |
| Has the project FOSS Table been updated with latest third party code? |
| Provide link to evidence |
|
| Do you have a plan to address any issue raised by Fossology? |
|
|
|
| Development | For new projects approved for this release, have all defined repositories source code been placed into Gerrit? |
| Provide link to evidence | For evidences, provide link(s) to Gerrit repos by providing the URL as shown in this example Example |
| Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) |
| Goal: 30-50% for Incubation project | Guidance on Code Coverage and Static Code Analysis Tools: Sonar |
| Is there any binaries (jar, war, tar, gz, gzip, zip files) in Gerrit project repository? |
Policy R1 Deliverables for Functionality Freeze Milestone Checklist Template ensure | ensure that all proprietary trademarks, logos, product names, company name, etc. have been removed? All |
OPEN-O | ONAP deliverables must comply with this rule and be agnostic of any proprietary symbols. |
|
|
|
| Is there any pending commit request older than |
24 Are
|
|
|
| Have all the Jenkins jobs successfully passed (Merge-Jobs)? |
| Provide link |
to "Merge job" in Jenkins has two types of Jobs "Verify" and "Merge". The question covers the "Merge-Jobs". |
|
| Are all snapshot binaries available in Nexus? |
| Provide link to evidence in Nexus project folder |
|
| Integration and Testing | Have |
Continuous System Integration Testing (CSIT) Use Cases been | functional test cases been documented in wiki? |
| Provide link to evidence |
Template is available in wiki |
|
| Have you implemented in Jenkins at least 1 |
CSIT | functional test case for each of the project repository? |
| 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 |
Daily | Build process? |
|
| Goal is to ensure your project latest commits have not broken the |
Integration Daily Build.You have to check that the latest Integration Daily Build was not broken by your project.build. |
| Documentation | Has the team identified and outlined the set of documentations to be delivered in this Release? |
|
|
|