Re: Issue sweep
From: Julian Foad <julianfoad_at_btopenworld.com>
Date: Thu, 19 Feb 2015 15:31:16 +0000
Bert Huijben wrote:
Here they are, for easier reference:
>> * Bulk reassign every 1.-consider issue to 'unscheduled'. If we
Yes, but I am suggesting it makes more sense to do something different.
In the meantime, I have bumped them to 1.10-consider, and now we have the following stats:
1.6.x 1 (1 defect) REVIEW
1.7.x 4 (4 defect) REVIEW
1.8.1 2 (2 defect) REVIEW
1.9.0 1 (1 defect)
1.10-consider 110 (43 defect)
I suggest that there is little reason why an issue now marked '1.10-consider' should be treated differently from one marked 'unscheduled'. All it means is somebody, sometime in the past, thought this issue should ideally be fixed in the 'next' release (at that time) rather than in any future release when we got around to it. But now we know that the issue was *not* fixed in that next release (at the time), what reason do we have to think it should *now* be prioritized over the other (unscheduled) issues?
> Can somebody with more privileges on Tigris create the right targets?
I have added 1.9.x and 1.10.0, and 1.10-consider is already there.
This is an archived mail posted to the Subversion Dev mailing list.