releases:brahmaputra:release_plan:octopus_milestone_e_report
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
releases:brahmaputra:release_plan:octopus_milestone_e_report [2015/12/17 20:37] Debra Scott created |
releases:brahmaputra:release_plan:octopus_milestone_e_report [2016/01/05 16:26] (current) Ulrich Kleber |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| Octopus Milestone E report | Octopus Milestone E report | ||
| + | |||
| + | Status: Red | ||
| + | * unclear how to do the release testing when scenarios are not clarified | ||
| + | * not enough hardware resources to execute CI for the scenarios. | ||
| 1. Has Functest test framework been executed against a deployed OPNFV platform on your infrastructure? | 1. Has Functest test framework been executed against a deployed OPNFV platform on your infrastructure? | ||
| + | |||
| + | Not applicable | ||
| 2. Has Yardstick test framework been executed against a deployed OPNFV platform on your infrastructure? | 2. Has Yardstick test framework been executed against a deployed OPNFV platform on your infrastructure? | ||
| + | |||
| + | Not applicable | ||
| 3. Have all test framework & deployment tool combinations been run against each lab? | 3. Have all test framework & deployment tool combinations been run against each lab? | ||
| + | |||
| + | Not applicable | ||
| 4. Are all target Brahmaputra test configurations available & functioning in the labs? | 4. Are all target Brahmaputra test configurations available & functioning in the labs? | ||
| + | |||
| + | Not applicable | ||
| 5. Do all labs meet the agreed upon criteria for "stable"? | 5. Do all labs meet the agreed upon criteria for "stable"? | ||
| + | |||
| + | Not applicable | ||
| 6. Have all known test issues (Jira tickets against your project) been documented and that documentation either integrated into the release or made available on a public page and pointed to through documents that are integrated into the release? | 6. Have all known test issues (Jira tickets against your project) been documented and that documentation either integrated into the release or made available on a public page and pointed to through documents that are integrated into the release? | ||
| + | |||
| + | Jira content needs some polishing. | ||
| 7. Are all known issues (open Jira Tickets) been prioritized by severity of impact (critical, high, medium, low) to users? | 7. Are all known issues (open Jira Tickets) been prioritized by severity of impact (critical, high, medium, low) to users? | ||
| + | |||
| + | Jira content needs some polishing. | ||
| 8. Do all known critical Jira Tickets have a workaround in place? | 8. Do all known critical Jira Tickets have a workaround in place? | ||
| + | |||
| + | Jira content needs some polishing. | ||
| 9. Do all non-critical Jira Tickets have a planned disposition in place (ie. deferred-fix in later release or closed- won't fix)? | 9. Do all non-critical Jira Tickets have a planned disposition in place (ie. deferred-fix in later release or closed- won't fix)? | ||
| + | |||
| + | Jira content needs some polishing. | ||
| 10. Is your documentation complete and checked in? If not, how do you plan to deliver it independent of the release? | 10. Is your documentation complete and checked in? If not, how do you plan to deliver it independent of the release? | ||
| + | |||
| + | Not applicable | ||
releases/brahmaputra/release_plan/octopus_milestone_e_report.1450384674.txt.gz · Last modified: 2015/12/17 20:37 by Debra Scott
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
