[Zope-dev] Re: [Zope-Coders] Collector Status Meanings
Chris Withers
chris at simplistix.co.uk
Fri Jul 30 13:54:05 EDT 2004
Chris McDonough wrote:
> I don't think deferred is useless. I used deferred to mean "stuff that
> isn't so important that it needs to be fixed now, but stuff that should
> be fixed nonetheless".
Sutff in this state can be left in pending, as most of it is now...
> IOW, deferred to me means it's been looked at,
> it's been determined to be a real problem, but it's just not possible to
> fix given resource constraints.
pending with a comment is how this works in practice...
> "Wontfix" doesn't mean this to me;
> instead it means it just won't get fixed ever.
Yep, but there's nothing stopping people picking up a wontfix if they
want to fix it, it just means it's taken out of the default issue list...
> I don't think it's important to move all issues from pending/deferred to
> a "terminal" state like "wontfix"/"rejected"/"resolved".
I agree, but I don't want them put in a "deferred" state which hides
them and might as well BE terminal...
> It's ok to
> leave some issues pending long-term, and this is what "deferred" is
> for. If that's a "dumping ground", I think it's ok.
They can stay in the pending state then, plenty of issues stay in the
pending state for years, so I see no difference between your use of
deferred and the current use of pending...
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
More information about the Zope-Coders
mailing list