User Tools

Site Tools


releases:brahmaputra:release_plan:doctor_milestone_e_report

Doctor Milestone E Report

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

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

3. Are your test cases all ready? No, but we already developed and tested in our OpenStack deployment

4. Are your test cases all passing? Not in pharos lab

5. Do you feel you are prepared for code freeze on January 5th? Yes (for feature codes in OpenStack), code freeze for test cases is expected before Jan 12th

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 (issues will be documented by the dudate written in JIRA tickets)

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? No, ci integration is not ready due to testing projects schedules

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

10. Is your documentation complete and checked in? If not, how do you plan to deliver it independent of the release? No, documents (user manuals) will be drafted or merged by Jan 19th

releases/brahmaputra/release_plan/doctor_milestone_e_report.txt · Last modified: 2016/01/05 15:56 by Ryota Mibu