Talk:Handling trackers

Using "pending" status for issues solved in CVS

Dimitry suggested we could use "pending" status of an item to mark issues solved in CVS. Currently all pending issues are automatically closed after 60 days, but this setting can be changed.

1. Con: It violates the definition of "pending" used by SourceForge[1], according to which "pending" is a synonym to "author action needed", meaning that the author of the item should provide further information so that the team can solve the problem.
2. Pro: It enables developers to quickly filter issues solved in CVS from those not solved at all. SourceForge does not provide any other suitable state, the other ones being "open", "closed", "deleted".
3. Con: New users coming to see the trackers see only open items, not those pending, as I have just verified. Those using the stable version will thus post duplicate entries; presumably many of them will use the stable version.

--Danielpolansky 03:16, 14 Jul 2007 (PDT)

Tracker system should first help the developers to manage issues so that the product quality can be insured. Easy filtering of solved and to-be-solved issues on the status is very important. That's why already solved issues should not remain "open". --DimitriPolivaev 03:31, 14 Jul 2007 (PDT)

I have modified my original post above to emphasize your point of view. I understand your answer as saying that you value the pro of 2 more than the con 1 and con 3. I am not sure I share this preference. Finding a solution that has fewer cons would be better. Developers are not the only users of the tracker system, so their requirements should not be per default put above the requirements of those who post the issues, IMO. --Danielpolansky 03:49, 14 Jul 2007 (PDT)