releases:brahmaputra:release_plan:promise_milestone_e_report
Differences
This shows you the differences between two versions of the page.
|
releases:brahmaputra:release_plan:promise_milestone_e_report [2015/12/17 20:19] Debra Scott created |
releases:brahmaputra:release_plan:promise_milestone_e_report [2016/01/06 02:19] (current) Peter Lee updated with responses |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| Promise Milestone E Report | Promise 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 | + | No, we have yet to complete the installer deployment scripts for Fuel and JOID. We expect to complete this week. |
| - | 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, we have the test cases defined but they are pending execution until completion of the installer scripts as noted above. |
| - | 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, the test cases are ready but we are still working on scripting and validating the test cases. |
| - | 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 | + | No, we still need to validate the test cases on a deployed lab to run all the cases. |
| - | 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? |
| + | |||
| + | Yes, but we expect additional bugfixes to be likely given that we have yet to run through the complete test cases on a Pharos lab deployment. | ||
| + | |||
| + | 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? | ||
| + | |||
| + | Yes. | ||
| + | |||
| + | 7. Are all known open issues (Jira Tickets) prioritized by severity of impact (critical, high, medium, low) to users? | ||
| + | |||
| + | Yes. | ||
| + | |||
| + | 8. All known open critical Jira Tickets have been closed or have a workaround in place? | ||
| + | |||
| + | Yes. | ||
| + | |||
| + | 9. Do all non-critical Jira Tickets have a planned disposition in place (ie. deferred-fix in later release or closed- won't fix)? | ||
| + | |||
| + | Yes, most of remaining open tickets are related to documentation and planned for resolution as part of B release. | ||
| 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? | ||
| + | |||
| + | No, we are planning on finalizing the remaining documentation efforts by mid/late January. | ||
releases/brahmaputra/release_plan/promise_milestone_e_report.1450383591.txt.gz · Last modified: 2015/12/17 20:19 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
