From cf1d1a9571436dcd91dc86b3e51d56b49af6445c Mon Sep 17 00:00:00 2001
From: Benjamin Peterson <benjamin@python.org>
Date: Mon, 5 Sep 2016 11:29:00 -0700
Subject: [PATCH] update pep 101 for release repo move

---
 pep-0101.txt | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/pep-0101.txt b/pep-0101.txt
index 3f6ff1d8a..b265c22e2 100644
--- a/pep-0101.txt
+++ b/pep-0101.txt
@@ -90,7 +90,7 @@ How to Make A Release
     As much as possible, the release steps are automated and guided by the
     release script, which is available in a separate repository:
 
-        https://hg.python.org/release/
+        https://github.com/python/release-tools
 
     We use the following conventions in the examples below.  Where a release
     number is given, it is of the form X.Y.ZaN, e.g. 3.3.0a3 for Python 3.3.0
@@ -187,7 +187,7 @@ How to Make A Release
 
   ___ Bump version numbers via the release script.
 
-      $ .../release/release.py --bump X.Y.ZaN
+      $ .../release-tools/release.py --bump X.Y.ZaN
 
       Reminder: X, Y, Z, and N should be integers.
       a should be one of "a", "b", or "rc" (e.g. "3.4.3rc1").
@@ -232,7 +232,7 @@ How to Make A Release
 
   ___ Tag the release for X.Y.ZaN.
 
-      $ .../release/release.py --tag X.Y.ZaN
+      $ .../release-tools/release.py --tag X.Y.ZaN
 
       NOTE: when forward, i.e. "null" merging your changes to newer branches,
       e.g. 2.6 -> 2.7, do *not* revert your changes to the .hgtags file or you
@@ -250,7 +250,7 @@ How to Make A Release
 
       ___ First, set the original trunk up to be the next release.
 
-          $ .../release/release.py --bump 3.3a0
+          $ .../release-tools/release.py --bump 3.3a0
 
           ___ Edit all version references in the README
 
@@ -368,7 +368,7 @@ How to Make A Release
   ___ Use the release script to create the source gzip and xz tarballs,
       documentation tar and zip files, and gpg signature files.
 
-      $ .../release/release.py --export X.Y.ZaN
+      $ .../release-tools/release.py --export X.Y.ZaN
 
       This can take a while for final releases, and it will leave all the
       tarballs and signatures in a subdirectory called 'X.Y.ZaN/src', and the
@@ -594,7 +594,7 @@ How to Make A Release
 
   ___ Do the guided post-release steps with the release script.
 
-      $ .../release/release.py --done X.Y.ZaN
+      $ .../release-tools/release.py --done X.Y.ZaN
 
       Review and commit these changes.