[Zope-Coders] Re: Collector Status Meanings

[Chris Withers]

Tres Seaver wrote:
>>     - Changes that would be sensible to make, but would cause more
>>       damage than good.
>>
> You could elaborate ( 'e.g., would break backward compatibility, would
> make testing hard / impossible, etc.').

How does the current version look?

>> That's also a Wontfix for me. Because in all practical terms, it means 
>> it won't get fixed, unless someone gets bored or has a point to prove 
>> and drags it out... Wontfix'ing something is also usually provokative 
>> enough that if someone sees something being Wontfix'ed on ZCM and the 
>> ydon't like it, they step in and do something.
> 
> You can't argue from "this is how we have behaved" to "this is what it 
> should mean". 

Not sure I follow you...

> "Wontfix" should be an intentionally *permanent* state; 

Says / said who? ;-)

> "deferred" means exactly what it says:  "later". 

Yeah, "no action in a month, this gets booted" ;-)

> It exists deliberately 
> to allow distinguishing between "never looked at" and "passes at least 
> initial muster".

All I see this doing is obscuring issues from the casual browser who 
glances through the pending list...

> So work on fixing that, instead of hiding the dirt under a different rug.

I'm trying to get as few a rugs as possible. I'd like Wontfix to be the 
generic rug, and have Deferred be used for something we need in the 
absence of new Collector functionality: an indication that an issue is 
on it's last warning...

>> Well, both of those fall into my definition of Wontfix. The patch is 
>> cute, but if no-one had stepped up, it wouldn't have mattered. The 
>> other one, well, Wontfix and Reject are both "end states" for me, so 
>> either has the same effect ;-)
> 
> Nope, neither fits "wontfix".

It appears we disagree ;-)

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