releases:brahmaputra:release_plan:sfqm_milestone_e_report
Differences
This shows you the differences between two versions of the page.
|
releases:brahmaputra:release_plan:sfqm_milestone_e_report [2015/12/17 20:15] Debra Scott created |
releases:brahmaputra:release_plan:sfqm_milestone_e_report [2016/01/04 15:16] (current) Maryam Tahhan |
||
|---|---|---|---|
| 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 | ||
| + | |||
| + | N | ||
| 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 | ||
| + | |||
| + | N/A we upstream our changes directly to DPDK. | ||
| 3. Are your test cases all ready? y/n | 3. Are your test cases all ready? y/n | ||
| + | |||
| + | Y. They have been upstreamed to DPDK. | ||
| 4. Are your test cases all passing? y/n | 4. Are your test cases all passing? y/n | ||
| + | |||
| + | Y. | ||
| 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 | ||
| + | |||
| + | Y. All features have been adopted as part of DPDK. | ||
| 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 | ||
| + | |||
| + | Y. | ||
| 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 | ||
| + | |||
| + | Y. | ||
| + | |||
| 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 | ||
| + | |||
| + | |||
| + | Y. | ||
| 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 | ||
| + | |||
| + | |||
| + | Y. | ||
| 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? | ||
| + | |||
| + | |||
| + | Y. | ||
releases/brahmaputra/release_plan/sfqm_milestone_e_report.1450383327.txt.gz ยท Last modified: 2015/12/17 20:15 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
