OPNFV Docs Milestone E Report
1. Is your tool & process infrastructure established such that other projects are able to submit their documentation?
No, composite documentation tooling is still being fine-tuned. Patch https://gerrit.opnfv.org/gerrit/#/c/5557/ contains the necessary composite docs tooling which is under testing now. This should not block creation of content as we have instructions in the wiki under https://wiki.opnfv.org/documentation/configguide however editing will be difficult until the composite document toolchain is complete and there may be minor template changes.
2. Have your test cases been run on the feature once deployed in a Pharos lab? y/n
N/A
3. Are your test cases all ready? y/n
N/A
4. Are your test cases all passing? y/n
N/A
5. Do you feel you are prepared for code freeze on January 5th? y/n
No, some tooling work and validation required to get to code complete.
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
No
7. Are all known open issues (Jira Tickets) prioritized by severity of impact (critical, high, medium, low) to users?y/n
n
8. All known open critical Jira Tickets have been closed or have a workaround in place?y/n
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
10. Is your documentation complete and checked in? If not, how do you plan to deliver it independent of the release?
No, work in progress. Review and updating ongoing. Awaiting definitions of scenario's and associated test suites in order to begin to document the general platform configuration and other central documentation.
