Promise Milestone E Report
1. Has your feature been executed on an OPNFV deployment in a Pharos lab?
No, we have yet to complete the installer deployment scripts for Fuel and JOID. We expect to complete this week.
2. Have your test cases been run on the feature once deployed in a Pharos lab?
No, we have the test cases defined but they are pending execution until completion of the installer scripts as noted above.
3. Are your test cases all ready?
Yes, the test cases are ready but we are still working on scripting and validating the test cases.
4. Are your test cases all passing?
No, we still need to validate the test cases on a deployed lab to run all the cases.
5. Do you feel you are prepared for code freeze on January 5th?
Yes, but we expect additional bugfixes to be likely given that we have yet to run through the complete test cases on a Pharos lab deployment.
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.
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.
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, most of remaining open tickets are related to documentation and planned for resolution as part of B release.
10. Is your documentation complete and checked in? If not, how do you plan to deliver it independent of the release?
No, we are planning on finalizing the remaining documentation efforts by mid/late January.
