MySAR

Blueprint assignments for “MySAR”

This listing shows the assignment of work for blueprints currently associated with MySAR. 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 → 14 of 14 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
3 Medium Register additional information besides STATUS & VARIABLES 5 New 1 Not started seattlegaucho seattlegaucho seattlegaucho
3 Medium Query the information_schema 5 New 0 Unknown seattlegaucho seattlegaucho seattlegaucho
3 Medium Take Snapshots of the information_schema 5 New 0 Unknown seattlegaucho seattlegaucho
3 Medium Snapshot the InnoDB status information 5 New 0 Unknown seattlegaucho seattlegaucho seattlegaucho
3 Medium Take snapshots of data from the mysql schema 5 New 0 Unknown seattlegaucho seattlegaucho
3 Medium Extend default purge to 90 days and use ARCHIVE to keep old data 5 New 0 Unknown seattlegaucho seattlegaucho
2 Low Installation Script 5 New 0 Unknown seattlegaucho seattlegaucho
2 Low Series' Naming Convention 5 New 0 Unknown seattlegaucho seattlegaucho seattlegaucho
1 → 14 of 14 specifications First • Previous • Next • Last