This shows you the differences between two versions of the page.
|
releases:brahmaputra:release_plan:ha_milestone_e_report [2015/12/17 20:49] Debra Scott created |
releases:brahmaputra:release_plan:ha_milestone_e_report [2015/12/18 02:48] (current) Qiao Fu |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| 1. Is your documentation complete and checked in? If not, how do you plan to deliver it independent of the release? | 1. Is your documentation complete and checked in? If not, how do you plan to deliver it independent of the release? | ||
| + | |||
| + | Requirement doc complete. Scenario doc partially still under review. Will finish before Feb. | ||
| 2. Do you feel you are prepared for code freeze on January 5th? y/n | 2. Do you feel you are prepared for code freeze on January 5th? y/n | ||
| + | |||
| + | No code delivered this time. | ||
| 3. 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 | 3. 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 | ||
| + | |||
| + | Yes | ||
| 4. Are all known open issues (Jira Tickets) prioritized by severity of impact (critical, high, medium, low) to users?y/n | 4. Are all known open issues (Jira Tickets) prioritized by severity of impact (critical, high, medium, low) to users?y/n | ||
| + | |||
| + | Yes | ||
| 5. All known open critical Jira Tickets have been closed or have a workaround in place?y/n | 5. All known open critical Jira Tickets have been closed or have a workaround in place?y/n | ||
| + | |||
| + | Yes | ||
| 6. 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 | 6. 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 | ||