[Python-Dev] bug triage
brett at python.org
Wed Jan 6 20:03:32 CET 2010
On Wed, Jan 6, 2010 at 06:57, Brian Curtin <brian.curtin at gmail.com> wrote:
> On Wed, Jan 6, 2010 at 06:57, Nick Coghlan <ncoghlan at gmail.com> wrote:
>> I believe someone (Daniel Diniz, maybe?) did do a pass over those some
>> time in the last 12 months, so most of the obviously irrelevant ones
>> that are that old should already be gone. Not to say it isn't worth
>> doing another pass, just saying not to get disheartened if there aren't
>> many that can be readily closed.
>> There are at least a few still kicking around just because they're
>> difficult to deal with (there's an ancient one to do with one of the
>> ways circular imports can fail that I occasionally go back and reread
>> before moving on to something more tractable).
> On the topic of bugs that can be readily closed (literally), I've recently
> come across a number of issues which appear to be sitting in a patch or
> review stage, but their patches have been committed and the issue remains
> open. What is the best course of action there? I'd just go ahead and close
> the issue myself but I don't have tracker privileges.
If a core developer is willing to step forward and vouch for you to get
tracker privileges then I will give them to you. We are trying to give out
tracker privs w/ less time than required to get commit privileges. So as
long as you have helped out on a few issues in a positive and correct way
that should be enough to get one of the regulars who perform triage to
I'm willing to help out with another Daniel Diniz-esque triage sweep if that
> would help.
> Python-Dev mailing list
> Python-Dev at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Python-Dev