releases:brahmaputra:release_plan:nvf-kvm_milestone_e_report
Differences
This shows you the differences between two versions of the page.
|
releases:brahmaputra:release_plan:nvf-kvm_milestone_e_report [2015/12/17 20:05] Debra Scott created |
releases:brahmaputra:release_plan:nvf-kvm_milestone_e_report [2016/01/06 21:19] (current) Raghuveer Reddy |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| 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? y/n | ||
| + | No. We never run on Pharos lab. We have not integrated with CI framework. | ||
| 2. Have your test cases been run on the feature once deployed in a Pharos lab? y/n | 2. Have your test cases been run on the feature once deployed in a Pharos lab? y/n | ||
| + | No. | ||
| 3. Are your test cases all ready? y/n | 3. Are your test cases all ready? y/n | ||
| + | Yes. All tests have been completed locally. | ||
| 4. Are your test cases all passing? y/n | 4. Are your test cases all passing? y/n | ||
| + | No. The test cases have been created on Yardstick but have not been run yet. | ||
| 5. Do you feel you are prepared for code freeze on January 5th? y/n | 5. Do you feel you are prepared for code freeze on January 5th? y/n | ||
| + | Yes. Code freeze will be completed on 6th. Testing on test frame bed has not started yet. | ||
| 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 | 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 | ||
| + | All documentation is made available on wiki page. | ||
| 7. Are all known open issues (Jira Tickets) prioritized by severity of impact (critical, high, medium, low) to users?y/n | 7. Are all known open issues (Jira Tickets) prioritized by severity of impact (critical, high, medium, low) to users?y/n | ||
| + | Yes. We do not have any open known issues. | ||
| 8. All known open critical Jira Tickets have been closed or have a workaround in place?y/n | 8. All known open critical Jira Tickets have been closed or have a workaround in place?y/n | ||
| + | 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)?y/n | 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 | ||
| + | Yes | ||
| 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? | ||
| + | ?? | ||
releases/brahmaputra/release_plan/nvf-kvm_milestone_e_report.1450382743.txt.gz · Last modified: 2015/12/17 20:05 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
