I would put my $0.02 for a 'tested' state, entered from Resolved. So from resolved you could 'resubmit' back to pending or accepted, or go to tested. This because it does happen, that someone *thinks* they have fixed something, but didn't test it thoroughly (there are usually way to many combinations for one person to do so), and it wasn't really fixed. On Friday, July 30, 2004, at 10:01 AM, Chris Withers wrote:
Hi All,
Apologies for the cross-posting, but I think this is relevent to all these lists.
I've summarised the meaning of the various collector states here:
http://dev.zope.org/CVS/CollectorStatuses
Please let me know if you disagre with any of that, although I'm pretty sure they're right and will argue with anyone who thinks otherwise ;-)
The only real change is that Deferred now means "we asked the user for more information and we'll reject the issue unless they give it to us within a month"
I went through all the issues which WERE deferred and "dealt" with them. I'm trying to avoid having states where issues end up that aren't definitive and so get forgotten about.
The "wontfix" stuff now has a definitve meaning, but it may still be good to go through them all once a year or so to check that none of them have been solved in other ways. I found quite a few of the "deferred" ones that really should have been "wontfix" had been addressed and could now be marked as resolved :-)
cheers,
Chris
-- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk _______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )