releases:brahmaputra:release_plan:ovsnfv_milestone_e_report
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
releases:brahmaputra:release_plan:ovsnfv_milestone_e_report [2015/12/17 20:07] Debra Scott created |
releases:brahmaputra:release_plan:ovsnfv_milestone_e_report [2016/01/04 13:37] (current) Mark D. Gray |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| OVSNFV Milestone E Report | OVSNFV Milestone E Report | ||
| - | 1. Has your feature been executed on an OPNFV deployment in a Pharos lab? y/n | + | 1. Has your feature been executed on an OPNFV deployment in a Pharos lab? |
| - | 2. Have your test cases been run on the feature once deployed in a Pharos lab? y/n | + | Yes. But it is currently not functioning correctly. |
| - | 3. Are your test cases all ready? y/n | + | 2. Have your test cases been run on the feature once deployed in a Pharos lab? |
| - | 4. Are your test cases all passing? y/n | + | No. |
| - | 5. Do you feel you are prepared for code freeze on January 5th? y/n | + | 3. Are your test cases all ready? |
| - | 6. Have all known open 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? y/n | + | Yes. We are planning to use a subset of the current FuncTest test suite. Our intention is that these tests will not be modified. If they need to be modified then that is a gap that we will resolve in a future release. |
| - | 7. Are all known open issues (Jira Tickets) prioritized by severity of impact (critical, high, medium, low) to users?y/n | + | 4. Are your test cases all passing? |
| - | 8. All known open critical Jira Tickets have been closed or have a workaround in place?y/n | + | N/A |
| - | 9. Do all non-critical Jira Tickets have a planned disposition in place (ie. deferred-fix in later release or closed- won't fix)?y/n | + | 5. Do you feel you are prepared for code freeze on January 5th? |
| + | |||
| + | Depends what code freeze is. We are still bug fixing and making small changes and bug fixes. | ||
| + | |||
| + | 6. Have all known open 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? | ||
| + | |||
| + | Too early to do this as we are still fixing bugs! | ||
| + | |||
| + | 7. Are all known open issues (Jira Tickets) prioritized by severity of impact (critical, high, medium, low) to users? | ||
| + | |||
| + | N/A | ||
| + | |||
| + | 8. All known open critical Jira Tickets have been closed or have a workaround in place? | ||
| + | |||
| + | N/A | ||
| + | |||
| + | 9. Do all non-critical Jira Tickets have a planned disposition in place (ie. deferred-fix in later release or closed- won't fix)? | ||
| + | |||
| + | N/A | ||
| 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 yet. | ||
releases/brahmaputra/release_plan/ovsnfv_milestone_e_report.1450382838.txt.gz · Last modified: 2015/12/17 20:07 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
