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:armband_milestone_e_report [2016/01/05 20:10] Joe Kidder |
releases:brahmaputra:release_plan:armband_milestone_e_report [2016/01/05 20:12] (current) Joe Kidder |
||
---|---|---|---|
Line 3: | Line 3: | ||
1. Has your feature been executed on an OPNFV deployment in a Pharos lab? yes | 1. Has your feature been executed on an OPNFV deployment in a Pharos lab? yes | ||
Running with Arno SR1 level components (Fuel 6.1, Juno, ODL Lithium) we have installed OPNFV on ARM servers in a Pharos lab. | Running with Arno SR1 level components (Fuel 6.1, Juno, ODL Lithium) we have installed OPNFV on ARM servers in a Pharos lab. | ||
+ | We intend to up-level during the last month to Fuel 8 and Liberty. | ||
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? no | ||
Line 19: | Line 20: | ||
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. | 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. | ||
- | We are investigating and planning to close a number of x86 dependencies; any deviations or exceptions will be documented in the release notes or referred by release notes to an external public page. | + | We are investigating and planning to close a number of x86 dependencies. |
+ | Any deviations or exceptions will be documented in the release notes or referred by release notes to an external public page. | ||
7. Are all known open issues (Jira Tickets) prioritized by severity of impact (critical, high, medium, low) to users? Yes | 7. Are all known open issues (Jira Tickets) prioritized by severity of impact (critical, high, medium, low) to users? Yes |