On Sat, Jun 14, 2008 at 6:43 PM, Marc Fargas <[EMAIL PROTECTED]> wrote:
> El mié, 11-06-2008 a las 08:45 +0800, Russell Keith-Magee escribió:
>> Trac contains all the information you need. If a ticket is open and
>> it's not assigned to somebody, then it's a safe bet that nobody is
>> looking at it. If it _is_ assigned to somebody, but there hasn't been
>> any activity (comments/patch uploads etc) recently, it's also a safe
>> bet that nobody is working on it.
>
> I would not be that sure on the last sentence, there are tickets that
> have no activity for a while (i.e. the ones I own can be 5 months
> staled) but they're not really abandoned, they're just waiting to move
> from a state to the other and while the patches do not conflict with
> trunk there are no changes.

My comment was a generalization. A good number of patches that are 5
months old won't apply cleanly to trunk, so they are effectively
abandoned. Of course, there will always be exceptions - but this is
the sort of thing that I would expect a human triager to be able to
identify.

The other thing to keep in mind is that 'activity' on a ticket isn't
just new patches or development comments - it can be as simple as a
user adding themselves as a CC to the ticket. This is one way for the
core developers to identify which tickets have a lot of interest in
the community - For example, #2070 (streaming uploads). #3566
(aggregates), #6095 (m2m intermediates) have fairly regular activity,
even if new patches aren't being uploaded.

> The only issue here is that only core developers can unassign tickets,
> but atleast the pinging step can be performed by other people, thus
> taking off some load from the core developers.

Good suggestion. I'm planning to have a bit of a fiddle with that part
of the docs tonight; I'll roll this suggestion into the mix.

Yours,
Russ Magee %-)

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to