On Fri, Feb 22, 2008 at 1:28 PM, A.M. Kuchling email@example.com wrote:
On Fri, Feb 22, 2008 at 01:06:05PM -0800, Brett Cannon wrote:
I think Martin is right that someone needs to take the lead and do a complete review of how issues are handled. That way we can do a change in one big batch to something that works better for Python.
Are we, as a development community, really running into problems with how we handle bugs? There are certainly small cleanups possible, such as dropping the 'postponed' and 'later' resolutions that we don't seem to use very much, but the flow seems reasonably efficient to me.
It's reasonable, but I wonder if it could be better. I am not sure as I have not had that much time to sit down and really think it through. I do know, though, that I like how Django has it structured: http://www.djangoproject.com/documentation/contributing/#ticket-triage .