[Python-Dev] bug triage
brett at python.org
Thu Jan 7 02:28:26 CET 2010
On Wed, Jan 6, 2010 at 17:22, R. David Murray <rdmurray at bitdance.com> wrote:
> On Wed, 06 Jan 2010 11:03:32 -0800, Brett Cannon wrote:
> > On Wed, Jan 6, 2010 at 06:57, Brian Curtin <brian.curtin at gmail.com>
> > > On the topic of bugs that can be readily closed (literally), I've
> > > 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
> > > open. What is the best course of action there? I'd just go ahead and
> > > 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
> > 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
> > notice.
> > -Brett
> I've done a quick scan of issues Brian is nosy on to refresh my
> memory, and I'd say he's definitely been making positive contributions.
> I'm willing to volunteer to keep an eye on his triage work for a while
> if you grant him tracker privs.
Done for the username brian.curtin (email doesn't match the one Brian
emailed from so do let me know, Brian if this is the right username).
> Brian, I assume you'll be cognizant of Antoine's advice about making
> sure a bug really should be closed before closing it :) Hanging out in
> #python-dev on freenode while working on issues can be helpful, as well,
> since you can quickly ask whoever is there for second opinions on
> particular bugs.
> R. David Murray www.bitdance.com
> Business Process Automation - Network/Server Management - Routers/Firewalls
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Python-Dev