[Zope-dev] Re: [Zope-Coders] Collector Status Meanings

[Chris Withers]

Chris McDonough wrote:
> 
> Maybe your practice... that's not how I've done it.  My understanding of
> the states has always been what Ken showed.

I'm just going on what I saw by reading a shedload of collector entries 
today...

> But needing to wade through a bunch of wontfixes that are just responses
> to bad bugreporting

These should be rejected, not wontfix'ed. And most of the time they now 
are. If I find any wontfix'es like this, I'd reject them, And given I 
went through ALL the wontfix'es today, I don't think there are any like 
this...

> The difference is that some pending items haven't even been looked at in
> earnest.  I usually put things in deferred only after I've spent a
> half-hour or hour or so trying to fix the thing and I've realized that
> it might take, say, a week to actually fix it.  OTOH, if I spent two
> minutes trying to fix something and fail but I still have no idea how
> long it would actually take to fix, I leave it in pending state.

Okay, but other people don't do this, or see the difference.
For me, it's easy enough to page through http://collector.zope.org/Zope 
and see the pending entries and see which ones of those have followups 
and which ones don't...

> I'm not sure I care enough to further argue, but I'll note that you're
> suggesting that we change the meaning of deferred to something other
> than long-term-pending and communicating this decision to all longtime
> collector participants is gonna be hard and the result will probably be
> confusing.

Well, at least there's a wiki page describing what the states mean now. 
I was contemplating linking that from the followup form just below/above 
the radio buttons for slecting the type of followup. Should I?

cheers,

Chris

FWIW: had it been trivial to add a new state, I would have done, it 
wasn't so I didn't :-S

-- 
Simplistix - Content Management, Zope & Python Consulting
            - http://www.simplistix.co.uk