...
Info |
---|
|
- 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 | Evidences | How to? |
---|
Product Management | Are committed Product Backlog Stories been coded and marked as "Done" in Jira? | Yes |
Link to Jira Jira |
---|
server | ONAP JIRA |
---|
jqlQuery | project = POLICY AND issuetype = Story AND status = Closed AND resolution = Done AND fixVersion = "Beijing Release" |
---|
count | true |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
|
|
Are all tasks associated with committed Product Backlog Stories been marked as "Done" in Jira? | Yes |
| Jira |
---|
server | ONAP JIRA |
---|
jqlQuery | project = POLICY AND issuetype = Sub-task AND status = Closed AND fixVersion = "Beijing Release" |
---|
count | true |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
|
Link to Jira |
|
Provide the project features list under the form of a bulleted list. |
Link to evidence | Yes | - >50% code coverage (as reported by Sonar on 6/4/2018)
- S3P Functionality
- HPA Use Case implemented
|
|
Summarize any functionalities that were planned at Release planning and not delivered at Release Sign-Off | Yes | - Integration with SDC Service Distribution
- Policy Developer Template/Rule/Policy Environment
- Beijing Policy template that would support Operational Control Loop Drools Policies as injected facts vs new java artifacts (NOTE: Template will itself be renamed to Casablanca template and may be altered to support new Lifecycle API)
|
|
Release Management | Have all issues pertaining to FOSS been addressed? | Yes |
|
|
Have all findings from previous milestones been addressed? | Yes |
Provide link to JIRA findings |
|
|
Development | Are all the Jenkins jobs successfully passed (verify + merge jobs)? | Yes | NOTE: Verify/Merge jobs are only for master branch. Beijing branch will not be instituted unless a maintenance release is necessary. |
|
Are all binaries available in Nexus Release repository? | Yes |
Provide link to evidenceProvide link to evidenceProvide link to evidenceNOTE: CSIT are only enabled for master branch. CSIT for beijing branch will not be instituted unless a maintenance release is necessary. | Goal is to incease our confidence the latest commit did not break the major functionality. Jenkins CSIT Jobs |
Has the project code successfully passed the Daily Build process? | Yes |
Provide link to evidenceNOTE: Daily Build Jobs are disabled after the release of Beijing. Release jobs for Beijing will only be instituted if a maintenance release is necessary. | Goal is to ensure the latest project commit has not broken the Integration Daily Build |
Has the project done the integration testing with related dependent projects? | Yes |
|
|
Documentation | Has your team contributed and completed work in the following documentations in ReadTheDocs: - Release Notes
- Project Documentation
| Yes |
Provide Link to Provide Link to ReadTheDocs Project DocumentationReadTheDocs Release Notes |