Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
OVSNFV Milestone E Report

1. Has your feature been executed on an OPNFV deployment in a Pharos lab? 

Yes. But it is currently not functioning correctly.

2. Have your test cases been run on the feature once deployed in a Pharos lab?

No.

3. Are your test cases all ready? 

Yes. We are planning to use a subset of the current FuncTest test suite. Our intention is that these tests will not be modified. If they need to be modified then that is a gap that we will resolve in a future release.

4. Are your test cases all passing?

N/A

5. Do you feel you are prepared for code freeze on January 5th? 

Depends what code freeze is. We are still bug fixing and making small changes and bug fixes. 

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? 

Too early to do this as we are still fixing bugs!

7. Are all known open issues (Jira Tickets) prioritized by severity of impact (critical, high, medium, low) to users?

N/A

8. All known open critical Jira Tickets have been closed or have a workaround in place?

N/A

9. Do all non-critical Jira Tickets have a planned disposition in place (ie. deferred-fix in later release or closed- won't fix)?

N/A

10. Is your documentation complete and checked in? If not, how do you plan to deliver it independent of the release?

Not yet.
Wiki

User Tools

Site Tools

Page Tools
