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

Streamline more version numbers for 2.5.

This commit is contained in:
Martin v. Löwis 2006-09-10 17:16:23 +00:00
parent 820378e7c1
commit 986abb0660
1 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
pep-0101.txt
View File

@ -74,9 +74,9 @@ How to Make A Release
before you've made the branch.
Add high level items new to this release. E.g. if we're
releasing 2.2a3, there must be a section at the top of the file
explaining "What's new in Python 2.2a3". It will be followed by
a section entitled "What's new in Python 2.2a2".
releasing 2.5a3, there must be a section at the top of the file
explaining "What's new in Python 2.5a3". It will be followed by
a section entitled "What's new in Python 2.5a2".
Note that you /hope/ that as developers add new features to the
trunk, they've updated the NEWS file accordingly. You can't be
@ -464,7 +464,7 @@ How to Make A Release
% cd .../pydotorg
% cvs -q up -P -d
% cd 2.2
% cd 2.5
% cp index.ht new-index.ht
___ Edit the file for content: usually you can globally replace
@ -500,9 +500,9 @@ How to Make A Release
releases. We keep all old releases, moving them into a "prev"
subdirectory when we have a new release.
So, there's a directory called "2.2" which contains
Python-2.2a2.exe and Python-2.2a2.tgz, along with a "prev"
subdirectory containing Python-2.2a1.exe and Python-2.2a1.tgz.
So, there's a directory called "2.5" which contains
Python-2.5a2.exe and Python-2.5a2.tgz, along with a "prev"
subdirectory containing Python-2.5a1.exe and Python-2.5a1.tgz.
So...
@ -552,7 +552,7 @@ How to Make A Release
___ Send a SourceForge News Item about the release. From the
project's "menu bar", select the "News" link; once in News,
select the "Submit" link. Type a suitable subject (e.g. "Python
2.2c1 released" :-) in the Subject box, add some text to the
2.5c1 released" :-) in the Subject box, add some text to the
Details box (at the very least including the release URL at
www.python.org and the fact that you're happy with the release)
and click the SUBMIT button.
@ -637,7 +637,7 @@ How to Make A Release
indicating that the trunk is going to be moving forward with
development. E.g. the line should look like:
#define PY_VERSION "2.2a2+"
#define PY_VERSION "2.5a2+"
Make sure that the other PY_ version macros contain the
correct values. Commit this change.
@ -686,7 +686,7 @@ What Next?
Final Release Notes
The Final release of any major release, e.g. Python 2.2 final, has
The Final release of any major release, e.g. Python 2.5 final, has
special requirements, specifically because it will be one of the
longest lived releases (i.e. betas don't last more than a couple
of weeks, but final releases can last for years!).