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

Update for 2.6a2 and 3.0a4 releases.

This commit is contained in:
Barry Warsaw 2008-04-04 01:19:32 +00:00
parent 9480accad2
commit cd375f860c
2 changed files with 5 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
pep-0101.txt
View File

@ -54,14 +54,12 @@ How to Make A Release
streamlined procedures used to release Python 2.6 (including the streamlined procedures used to release Python 2.6 (including the
alphas and betas). alphas and betas).
We recommend that you use the welease tool, from We recommend that you use the release tool, from
http://svn.python.org/projects/sandbox/trunk/welease/ http://svn.python.org/projects/sandbox/trunk/release/
It helps verifying that certain (not yet all) mechanic editing This helps by performing several automatic editing steps, and guides you
has not been forgotten, and invokes svn and tar commands to perform some manual editing steps.
automatically. This guide will indicate which steps are supported
by welease.
___ Impose a check-in freeze. Send a message to ___ Impose a check-in freeze. Send a message to
python-dev@python.org telling people not to make any check-ins python-dev@python.org telling people not to make any check-ins

2
pep-0361.txt
View File

@ -52,7 +52,7 @@ Release Schedule
unfolds. The minimal schedule is: unfolds. The minimal schedule is:
Feb 29 2008: Python 2.6a1 and 3.0a3 are released Feb 29 2008: Python 2.6a1 and 3.0a3 are released
Apr 02 2008: Python 2.6a2 and 3.0a4 planned Apr 02 2008: Python 2.6a2 and 3.0a4 are released
May 07 2008: Python 2.6a3 and 3.0a5 planned May 07 2008: Python 2.6a3 and 3.0a5 planned
Jun 04 2008: Python 2.6b1 and 3.0b1 planned Jun 04 2008: Python 2.6b1 and 3.0b1 planned
Jul 02 2008: Python 2.6b2 and 3.0b2 planned Jul 02 2008: Python 2.6b2 and 3.0b2 planned