From ca9ed7bb153e7f9d9055436dbc76184776841560 Mon Sep 17 00:00:00 2001 From: Benjamin Peterson Date: Fri, 26 Jun 2009 12:48:55 +0000 Subject: [PATCH] update release candidate shorthand --- pep-0101.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pep-0101.txt b/pep-0101.txt index 52c3b6231..8d65e7665 100644 --- a/pep-0101.txt +++ b/pep-0101.txt @@ -66,7 +66,7 @@ How to Make A Release We use the following conventions in the examples below. Where a release number is given, it is of the form X.YaZ, e.g. 2.6a3 for Python 2.6 alpha - 3, where "a" == alpha, "b" == beta, "c" == release candidate. + 3, where "a" == alpha, "b" == beta, "rc" == release candidate. Final releases are named "releaseXY". The branch tag is "releaseXY-maint" because this will point to the long lived maintenance branch. The fork