User Tools

Site Tools


releases:brahmaputra:release_plan:parser_milestone_e_report

Parser Milestone E Report

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

no

3. Are your test cases all ready? y/n

yes

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

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

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

yes

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

yes

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.txt · Last modified: 2016/01/05 00:33 by Zhipeng (Howard) Huang