Malcolm Tredinnick wrote:
> Raw statistics like this can be misleading and I think they are in this
> case. Yes, it's slightly disappointing to see the number creep up from
> month to month, but it's not a tragedy. Django still works, it's still
> usable in serious applications.
I agree it's still usable and working (and that my statistics can be
taken quite out of context), my focus was on the littler patches which
often aren't breaking anything. I think that part of the problem is
that Trac does little to determine the eligibility of some of these
patches (without requiring "telepathy" from committers).

> Since about half the tickets filed that have been closed are not
> actually requiring fixes, it's not crazy to think that the average
> carries across in part to the the currently open tickets as well.
Slight correction, 1/3 of closed tickets are marked invalid, wontfix,
duplicate or worksforme. And like you say, I'm not sure you can carry
that average across still opened tickets.

> Thirdly, the "Adrian as owner" measure is really bogus. The bulk of
> components have Adrian as the owner. I've mentioned in the past that I
> wouldn't mind if we had a generic user as the default owner to avoid
> that misperception, but it's hardly a real problem once you're aware of
> it.
I admit this was a bit cheeky to put in. What I was trying to get at by
this number is that these are roughly the number of unassigned tickets
- quite a large number.

> I should pull out some of the GNOME and Fedora bug
> triaging guidelines and tailor them to Django's work practices so that
> more people can start helping out there. A "bug squad" of triagers never
> hurts.
That sounds like a great idea.

Thanks for the reply, Malcom. I'm interested in what other people have
to say on the issue, especially any ideas of any way to streamline the
Django "defect/enhancement -> commit" process.


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to