Hi, currently we have 35 open bugs with 2.1.3 milestone. None of them will be fixed for 2.1.3, since the release is frozen, so these bugs need to be retargeted soon. Many of these bugs were already retargeted for several times (like 2.1.0 -> 2.1.1 -> 2.1.2 -> 2.1.3). This somehow renders the milestone a bit useless, since a milestone does not really mean that a bug gets fixed for that release. IMHO we should rethink our bug targeting practice, and I would propose the following:
Only set a fixed milestone (like 2.1.4 or 2.2.0) if a) somebody is actively working on a fix or b) the bug is so severe that it would block the release if it is not fixed. If a bug is important, but nobody is working on it, and it is no shostopper, use a milestone like 2.1.x or 2.2.x. For all other bugs, do not set a milestone at all. I believe that such a policy would make the milestones more useful, both for users and developers, and that they would show a more realistic picture (not too many bugs get fixed with a small number of developers). It would also reduce the number of milestone changes. What do you think? Georg
