Talk:Handling trackers: Difference between revisions

From FreeMind
Jump to navigationJump to search
No edit summary
 
Line 1: Line 1:
==Using "pending" status for issues solved in CVS==
==Using "pending" status for issues solved in CVS==


Dimitry suggested we could use "pending" status of an item to mark 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.


# ''Con:'' It violates the definition of "pending" used by SourceForge[http://sourceforge.net/docman/display_doc.php?docid=24202&group_id=1#issue_status], 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.
# ''Con:'' It violates the definition of "pending" used by SourceForge[http://sourceforge.net/docman/display_doc.php?docid=24202&group_id=1#issue_status], 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.

Revision as of 10:17, 14 July 2007

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 helps to distinguish 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 will probably see only open items, not those pending (really?). 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)