We have the following open issues that have a target milestone set. 1.6.x 1 (1 defect) REVIEW
1.7.x 4 (4 defect) REVIEW 1.7-consider 23 (13 defect) 1.8.1 2 (2 defect) REVIEW 1.8.x 1 (1 defect) REVIEW 1.8-consider 24 (22 defect) 1.9.0 1 (1 defect) 1.9.x 0 1.9-consider 52 (1 defect) 1.10-consider 11 (7 defect) I suggest we should: * Review each of the eight issues marked 'REVIEW' above to see if the milestone still should be set to a specific old release series. If not, change it to 'unscheduled'. * Bulk reassign every 1.[789]-consider issue to 'unscheduled'. If we didn't fix it for 1.7 or 1.8 or 1.9 there is no particular reason why we should *automatically* prioritize it over any other unscheduled issue for the 1.10 development period. Thoughts? Volunteers? - Julian
