releases:brahmaputra:release_plan:pharos_milestone_e_report
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
releases:brahmaputra:release_plan:pharos_milestone_e_report [2016/01/04 19:54] Trevor Cooper |
releases:brahmaputra:release_plan:pharos_milestone_e_report [2016/01/06 06:23] (current) Trevor Cooper |
||
|---|---|---|---|
| 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.a. | + | n.a. Pharos is responsible for providing resources for development, CI and testing |
| - | + | ||
| - | Pharos is responsible for providing the CI and test infrastructure | + | |
| 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 | ||
| Line 19: | Line 17: | ||
| 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 | ||
| + | We have not been using Jira for lab ops / issues ... we are working on a scheme to implement this. Lab resource allocation and status is available here https://wiki.opnfv.org/pharos_rls_b_labs | ||
| - | 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 |
| + | Jira tasks are not explicitly prioritized | ||
| - | 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 |
| + | n | ||
| + | Most critical are operational issues ... providing resources and support for all testing needs. Once scenarios are agreed we will review a plan for shared resources. | ||
| 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 | ||
| + | n | ||
| + | Need to scrub Jira tickets to review/allocated deferred/later milestones | ||
| 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? | ||
| + | No, documentation needs updating and some new documents need to be generated. Planning to work on documentation next week. | ||
releases/brahmaputra/release_plan/pharos_milestone_e_report.1451937261.txt.gz · Last modified: 2016/01/04 19:54 by Trevor Cooper
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
