Blueprint assignments for “trunk”
This listing shows the assignment of work for blueprints currently associated with trunk. The drafter is responsible for getting the specification correctly written up and approved. The approver is usually the person who would sign off on the specification.
| 1 → 6 of 6 specifications | First • Previous • Next • Last |
| Priority | Name | Definition | Delivery | Assignee | Drafter | Approver |
|---|---|---|---|---|---|---|
| 4 High | MySAR Needs a Name Change | 0 Approved | 7 Good progress | seattlegaucho | seattlegaucho | seattlegaucho |
| 3 Medium | Use perldoc for documentation | 0 Approved | 7 Good progress | seattlegaucho | seattlegaucho | seattlegaucho |
| 3 Medium | Purge old data to keep table size in check | 0 Approved | 7 Good progress | seattlegaucho | seattlegaucho | seattlegaucho |
| 3 Medium | Record snapshots from remote server on a local repository | 0 Approved | 1 Not started | seattlegaucho | seattlegaucho | seattlegaucho |
| 3 Medium | Record the process list to cross check w/ server status | 0 Approved | 7 Good progress | seattlegaucho | seattlegaucho | seattlegaucho |
| 3 Medium | Record a Snapshot of the SHOW SLAVE STATUS output | 0 Approved | 7 Good progress | seattlegaucho | seattlegaucho | seattlegaucho |
| 1 → 6 of 6 specifications | First • Previous • Next • Last |
