releases:brahmaputra:release_plan:opnfvdocs_milestone_e_report
Differences
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:opnfvdocs_milestone_e_report [2016/01/05 09:23] Christopher Price |
releases:brahmaputra:release_plan:opnfvdocs_milestone_e_report [2016/01/05 13:59] (current) Christopher Price |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| 1. Is your tool & process infrastructure established such that other projects are able to submit their documentation? | 1. Is your tool & process infrastructure established such that other projects are able to submit their documentation? | ||
| - | No, composite documentation tooling is still under development. | + | No, composite documentation tooling is still being fine-tuned. |
| Patch https://gerrit.opnfv.org/gerrit/#/c/5557/ contains the necessary composite | 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 | 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 | 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. | + | 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 | 2. Have your test cases been run on the feature once deployed in a Pharos lab? y/n | ||
| Line 31: | Line 32: | ||
| 7. Are all known open issues (Jira Tickets) prioritized by severity of impact (critical, high, medium, low) to users?y/n | 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 | 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 | 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? | 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. | 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. | ||
releases/brahmaputra/release_plan/opnfvdocs_milestone_e_report.1451985808.txt.gz · Last modified: 2016/01/05 09:23 by Christopher Price
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
