releases:brahmaputra:release_plan:parser_milestone_e_report
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
releases:brahmaputra:release_plan:parser_milestone_e_report [2015/12/17 20:27] Debra Scott created |
releases:brahmaputra:release_plan:parser_milestone_e_report [2016/01/05 00:33] (current) Zhipeng (Howard) Huang |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| Parser Milestone E Report | Parser Milestone E Report | ||
| - | 1. Has your feature been executed on an OPNFV deployment in a Pharos lab? y/n | + | 1. Has your feature been executed on an OPNFV deployment in a Pharos lab? y/n |
| + | |||
| + | //no// | ||
| 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 | ||
| + | |||
| + | //no// | ||
| 3. Are your test cases all ready? y/n | 3. Are your test cases all ready? y/n | ||
| + | |||
| + | //yes// | ||
| 4. Are your test cases all passing? y/n | 4. Are your test cases all passing? y/n | ||
| + | |||
| + | //yes// | ||
| 5. Do you feel you are prepared for code freeze on January 5th? y/n | 5. Do you feel you are prepared for code freeze on January 5th? y/n | ||
| + | |||
| + | //all development related codes are able to be frozen on Jan 5th, there might be some testing code coming in the following 2 - 3 days// | ||
| 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 | 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 | ||
| + | |||
| + | //Documentation are partially done, still lack of a general description document.// | ||
| 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 | ||
| + | |||
| + | //yes// | ||
| 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 | ||
| + | |||
| + | //all are addressed but haven't been closed yet// | ||
| 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 | ||
| + | |||
| + | //yes// | ||
| 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? | ||
| + | |||
| + | //still working on a general description document// | ||
releases/brahmaputra/release_plan/parser_milestone_e_report.1450384043.txt.gz · Last modified: 2015/12/17 20:27 by Debra Scott
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
