This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients Alexander.Belopolsky, belopolsky, georg.brandl, lavajoe, r.david.murray
Date 2012-04-18.21:05:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1334783120.28.0.255077393481.issue10941@psf.upfronthosting.co.za>
In-reply-to
Content
I see Alexander is going to take care of this.  But to clarify what I suggested for your information:

In an ideal world it would be a committer doing the patch review, followed by a checkin.  But in the real world there aren't enough of us with enough time to get to all the bugs with patches.  You asked how to move it along and I suggested one way: get someone else to do a review.  I wouldn't say that the submitter recruiting a reviewer was a "normal" process, but it is a way to get bugs unstuck.  And we get reviews from non-committers frequently (it is a step along the path to becoming a committer...quality reviews are as important as quality patches).

I don't think there's anything in the devguide about this particular nuance.
History
Date User Action Args
2012-04-18 21:05:20r.david.murraysetrecipients: + r.david.murray, georg.brandl, belopolsky, Alexander.Belopolsky, lavajoe
2012-04-18 21:05:20r.david.murraysetmessageid: <1334783120.28.0.255077393481.issue10941@psf.upfronthosting.co.za>
2012-04-18 21:05:19r.david.murraylinkissue10941 messages
2012-04-18 21:05:19r.david.murraycreate