iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Some relatively minor, er, micro changes. Python 2.1.2 is technically 

a micro release of the Python 2.1 branch.

Shortened the title.
This commit is contained in:
Barry Warsaw 2002-01-10 16:10:18 +00:00
parent a547266a01
commit a5b04739df
1 changed files with 17 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
pep-0102.txt
View File

@ -1,11 +1,13 @@
PEP: 102
Title: Doing Python Releases 102 - The Minor Releases
Title: Doing Python Micro Releases
Version: $Revision$
Last-Modified: $Date$
Author: barry@zope.com (Barry A. Warsaw), guido@python.org (Guido van Rossum), anthony@interlink.com.au (Anthony Baxter)
Author: anthony@interlink.com.au (Anthony Baxter)
barry@zope.com (Barry A. Warsaw)
guido@python.org (Guido van Rossum)
Status: Active
Type: Informational
Created: 22-Aug-2001 (edited down on 9-Jan-2002 to become pep-0102)
Created: 22-Aug-2001 (edited down on 9-Jan-2002 to become PEP 102)
Post-History:
@ -16,9 +18,11 @@ Abstract
Until recently, most -- if not all -- of that burden was borne by
Guido himself. But several recent releases have been performed by
other folks, so this PEP attempts to collect, in one place, all
the steps needed to make a Python bugfix release. The major Python
release process is covered in PEP 101 - this PEP is just 101, trimmed
down to only include the bits that are relevant for minor releases.
the steps needed to make a Python bugfix release.
The major Python release process is covered in PEP 101 - this PEP
is just PEP 101, trimmed down to only include the bits that are
relevant for micro releases, a.k.a. patch, or bug fix releases.
It is organized as a recipe and you can actually print this out and
check items off as you complete them.
@ -40,12 +44,12 @@ How to Make A Release
steps.
We use the following conventions in the examples below. Where a
release number is given, it is of the form X.Y.MaA, e.g. 2.1.2rc1 for
Python 2.1.2 release candidate 1, where "a" == alpha, "b" == beta,
"rc" == release candidate. Final releases are tagged with "releaseXYZ"
in CVS. The minor releases are made from the maintenance branch of the
major release, e.g. Python 2.1.2 is made from the release21-maint
branch.
release number is given, it is of the form X.Y.MaA, e.g. 2.1.2c1
for Python 2.1.2 release candidate 1, where "a" == alpha, "b" ==
beta, "c" == release candidate. Final releases are tagged with
"releaseXYZ" in CVS. The micro releases are made from the
maintenance branch of the major release, e.g. Python 2.1.2 is made
from the release21-maint branch.
___ Send an email to python-dev@python.org indicating the release is
about to start.
@ -89,7 +93,7 @@ How to Make A Release
verify with Tim Peters about changes on Windows, and Jack Jansen
about changes on the Mac.
This command should help you:
This command should help you (but substitute the correct -r tag!):
% cvs log -rr22a1: | python Tools/scripts/logmerge.py > /tmp/news.txt