[Zope-Coders] Re: Collector Status Meanings
Chris Withers
chris at simplistix.co.uk
Mon Aug 9 19:29:17 EDT 2004
Tres Seaver wrote:
>
> That is effectively the meaning of "deferred".
The only use I saw was "I wanna work on this sometime, so I'm doing to
accept it." Then it gets deferred the next day and never touched again.
"Wontfix" means (to me,
> anyway) that the requested change, while addressing a legitimate
> problem, would cause more damage than good.
I think I covered this with:
- Changes that would be sensible to make, but would impact on
backwards compatability in a way that's not acceptable.
Should I tweak that to:
- Changes that would be sensible to make, but would cause more
damage than good.
?
> "Deferred" means that
> somebody looked at it, didn't reject it as invalid, didn't judge that it
> was a "wontfix" issue, but that nobody was available to work on it.
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.
Deferred wasn't a powerful enough message to tempt that to happen, but
just resulted in the issues beign forgotten about.
> I undid a couple of Friday's "wontfix" changes on this basis (one I
> rejected, beacuse it was really a Python issue; the other I left
> pending, with a patch).
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 ;-)
cheers,
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
More information about the Zope-Coders
mailing list