releases:brahmaputra:release_plan:ovno_milestone_e_report
Differences
This shows you the differences between two versions of the page.
|
releases:brahmaputra:release_plan:ovno_milestone_e_report [2015/12/17 20:11] Debra Scott created |
releases:brahmaputra:release_plan:ovno_milestone_e_report [2016/01/06 14:47] (current) Stuart Mackie |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| OVNO Milestone E Report | OVNO 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? Not yet. It's aligned with the various installers, which themselves are not yet running OpenContrail in Pharos. Deployment with JOID is happening outside Pharos. |
| - | 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? No. There is a test suite running through Jenkins in an Orange pod that is not part of Pharos |
| - | 3. Are your test cases all ready? y/n | + | 3. Are your test cases all ready? Yes - though likely to add more for completeness |
| - | 4. Are your test cases all passing? y/n | + | 4. Are your test cases all passing? Yes |
| - | 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? The OpenContrail code itself is frozen. There are changes required to scripts in installers for Liberty support. |
| - | 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? No issues against the project itself at this time. |
| - | 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? Tracked in installers - none against the project itself. |
| - | 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? Tracked in installers - none against the project itself. |
| - | 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)? Tickets in the project are references to support in each installer. Will close when each installer reports successful deployment and functest. |
| - | 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? Documentation for OpenContrail is supplied as part of its own installation. Installers will provide their own documentation. |
releases/brahmaputra/release_plan/ovno_milestone_e_report.1450383092.txt.gz ยท Last modified: 2015/12/17 20:11 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
