[Tracker-discuss] [issue16] Automatic issue expiration
Daniel (ajax) Diniz
ajaksu at gmail.com
Mon Apr 6 02:41:59 CEST 2009
Stephen J. Turnbull wrote:
> "Martin v. Löwis" writes:
>
> > It means that whoever looked at the issue thinks it should be closed,
> > but on the off-chance that somebody might object, sets it to pending
> > only. No developer is interested anymore - it's about to be closed.
>
> Sorry for the confusion.
>
> But what's the point of "pending", then? It seems something that
> would be rarely useful.
Here's a sample of how I use it: http://tinyurl.com/ajaksu-pending
(BTW, it seems I've misused it by setting some issues to pending
without a warning or call for feedback). In the set of all pending
issues (http://tinyurl.com/all-pending ), some look like clickos
('closed' intended) and others look like different interpretations of
'pending' (e.g. http://bugs.python.org/issue4751 ).
> Somebody with presumably good judgment has
> decided it's not interesting,
Given my usual lack of good judgment, pending is a nice crutch :)
> and people who know they care about the
> issue will be in the nosy list in "most" cases.
Ah, but some of these bugs are six years old, so setting them to
pending bumps them to the top of the activity queue with (supposedly)
a 'this is being considered for closing, voice your opposition if you
care about it' message.
> If you must keep it,
> then it should be renamed as Tennessee says.
+0. I'd rather have a tooltip explaining it a bit more, as "pending
closure" isn't that clear to my non-native eyes. +1 on something
unambiguous that makes the tooltip unnecessary :)
> Something like "resolved" would be fine. At least native speakers who
> ask "what's the difference between 'resolved' and 'closed'?" who are
> told "resolved issues are displayed in lists by default, closed issues
> are hidden" should never need to ask again. I bet most non-natives
> will catch on to that distinction quickly, too.
-1, IMO 'pending' is almost 'pending a more correct status, tending to
close': if nobody cares (or someone strongly wants the issue closed),
the correct status is closed, if someone opposes, the status should be
open. See:
http://bugs.python.org/issue1569040 - interested party is nosy
http://bugs.python.org/issue1542544 - interested party isn't nosy
http://bugs.python.org/issue5608 - interested party isn't nosy, knows
it should be closed
> But I would just nuke the whole status as an unnecessary complexity.
-1, that would force everyone to change their tracker use and add
stronger meanings to e.g. stage :)
Best regards,
Daniel
More information about the Tracker-discuss
mailing list