Paul Burba wrote: > Whenever we approach a release we always face the question: Which of > our open issues are blockers for the upcoming release? Obviously as > we approach 1.8, anything with a target milestone of 1.8.0 is > (supposedly) a blocker. But what about all the issues with the '---' > target milestone? Very old issues (e.g. something filed in say 2007) > are almost certainly not blockers, whereas more recently filed issues > may be. > > Unfortunately we currently have 131 issues with a target milestone of > '---', though given the age of many of these I'm fairly confident they > are *not* blockers for 1.8 as they have already seen one or more > releases pass by. > > Recall how we claim to use the target milestone: [...] > In the interests of sanity I propose we bulk assign all issues filed > before some arbitrary point in time to the 'unscheduled' milestone. I > suggest using the date 1.7.0 was tagged as that point, under the > assumption that any issues filed prior were not considered 1.7.0 > blockers, so shouldn't be considered 1.8.0 blockers either. That > would leave 24 "newer" issues which I'm happy to review and assign an > initial milestone to. > > Thoughts?
+1, and I can't think of any date better that your suggestion of 1.7.0 tag date. - Julian
