releases:brahmaputra:release_plan:prediction_milestone_e_report
Differences
This shows you the differences between two versions of the page.
|
releases:brahmaputra:release_plan:prediction_milestone_e_report [2015/12/17 20:21] Debra Scott created |
releases:brahmaputra:release_plan:prediction_milestone_e_report [2016/01/06 08:56] (current) Hai Liu |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| Prediction Milestone E Report | Prediction 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? NO |
| + | 2. Have your test cases been run on the feature once deployed in a Pharos lab? NO | ||
| - | 2. Have your test cases been run on the feature once deployed in a Pharos lab? y/n | + | 3. Are your test cases all ready? NO |
| + | 4. Are your test cases all passing? NO | ||
| - | 3. Are your test cases all ready? y/n | + | 5. Do you feel you are prepared for code freeze on January 5th? NO |
| - | + | 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 | |
| - | 4. Are your test cases all passing? y/n | + | 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 | |
| - | 5. Do you feel you are prepared for code freeze on January 5th? 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)?YES |
| - | + | 10. Is your documentation complete and checked in? If not, how do you plan to deliver it independent of the release?YES | |
| - | 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 | + | |
| - | + | ||
| - | 7. Are all known open issues (Jira Tickets) prioritized by severity of impact (critical, high, medium, low) to users?y/n | + | |
| - | + | ||
| - | 8. All known open critical Jira Tickets have been closed or have a workaround in place?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 | + | |
| - | + | ||
| - | 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/prediction_milestone_e_report.1450383673.txt.gz · Last modified: 2015/12/17 20:21 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
