R. David Murray <rdmur...@bitdance.com> added the comment: 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. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue10941> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
