[Python-checkins] peps: Twice now I've assumed that release.py --bump would check in its

[larry.hastings]

http://hg.python.org/peps/rev/8880eba377c2
changeset:   5101:8880eba377c2
user:        Larry Hastings <larry at hastings.org>
date:        Sat Sep 07 23:33:30 2013 +1200
summary:
  Twice now I've assumed that release.py --bump would check in its
changes, and scotched the release.  Changing PEP 101 to hopefully
prevent this for 3.4.0a3.

files:
  pep-0101.txt |  3 ++-
  1 files changed, 2 insertions(+), 1 deletions(-)


diff --git a/pep-0101.txt b/pep-0101.txt
--- a/pep-0101.txt
+++ b/pep-0101.txt
@@ -192,7 +192,8 @@
       content of this file.  You should only need to review the text for
       sanity, and update the release date with today's date.
 
-      Commit the changes once you have reviewed them.
+  ___ Make sure all changes have been committed.  (``release.py --bump``
+      doesn't check in its changes for you.)
 
   ___ Check the years on the copyright notice.  If the last release
       was some time last year, add the current year to the copyright

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