[Python-checkins] devguide: #16868: mention that you can "ping" issues before writing to python-dev.

ezio.melotti python-checkins at python.org
Wed Jan 9 08:35:26 CET 2013


http://hg.python.org/devguide/rev/3f2637a6fbfa
changeset:   585:3f2637a6fbfa
user:        Ezio Melotti <ezio.melotti at gmail.com>
date:        Wed Jan 09 09:35:00 2013 +0200
summary:
  #16868: mention that you can "ping" issues before writing to python-dev.

files:
  patch.rst |  8 +++++---
  1 files changed, 5 insertions(+), 3 deletions(-)


diff --git a/patch.rst b/patch.rst
--- a/patch.rst
+++ b/patch.rst
@@ -139,9 +139,11 @@
 than there are people capable of reviewing your patch. Getting your patch
 reviewed requires a reviewer to have the spare time and motivation to
 look at your patch (we cannot force anyone to review patches). If your patch has
-not received any notice from reviewers (i.e., no comment made) after a
-substantial amount of time then you may
-email python-dev at python.org asking for someone to take a look at your patch.
+not received any notice from reviewers (i.e., no comment made) after one
+month, first "ping" the issue on the `issue tracker`_ to remind the nosy list
+that the patch needs a review.  If you don't get a response within a few days
+after pinging the issue, then you can try emailing python-dev at python.org asking
+for someone to review your patch.
 
 When someone does manage to find the time to look at your patch they will most
 likely make comments about how it can be improved (don't worry, even core

-- 
Repository URL: http://hg.python.org/devguide


More information about the Python-checkins mailing list