releases:brahmaputra:release_plan:lsoapi_milestone_e_report
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
releases:brahmaputra:release_plan:lsoapi_milestone_e_report [2015/12/17 19:58] Debra Scott created |
releases:brahmaputra:release_plan:lsoapi_milestone_e_report [2016/01/05 22:50] (current) Kevin Luehrs |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ARMband Milestone E Report | + | LSOAPI 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? y/n | ||
| + | No, not that we are aware of. | ||
| 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. We have reached out to the Pharos group to inquire about doing this but it has not been arranged yet. | ||
| 3. Are your test cases all ready? y/n | 3. Are your test cases all ready? y/n | ||
| + | Unit tests were created and are part of the LSOAPI code base. | ||
| 4. Are your test cases all passing? y/n | 4. Are your test cases all passing? y/n | ||
| + | Yes, our test cases are passing in our local environment. This is not a full OPNFV installation but does include a full OpenDaylight installation. | ||
| 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 has been tested successfully in a local environment and current code is posted in the project Git repo. | ||
| 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 | ||
| + | Yes | ||
| 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 | ||
| + | N/A. No open issues remain for Brahmaputra release. | ||
| 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? | ||
| + | Yes it is complete and checked in but some reformatting may be needed. | ||
releases/brahmaputra/release_plan/lsoapi_milestone_e_report.1450382333.txt.gz · Last modified: 2015/12/17 19:58 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
