More updates from Sean.
This commit is contained in:
parent
2dffac39e1
commit
758bca047f
24
pep-0101.txt
24
pep-0101.txt
|
@ -139,6 +139,30 @@ How to Make A Release
|
|||
to change the PY_VERSION macro, and one or several of the
|
||||
version subpart macros just above PY_VERSION, as appropriate.
|
||||
|
||||
___ Change the "%define version" line of Misc/RPM/python-2.3.spec to
|
||||
the same string as PY_VERSION was changed to above. E.g.
|
||||
|
||||
%define version 2.3.1
|
||||
|
||||
The following line, "%define libvers", should reflect the
|
||||
major/minor number as one would usually see in the
|
||||
"/usr/lib/python<libvers>" directory name. E.g.
|
||||
|
||||
%define libvers 2.3
|
||||
|
||||
If the new release uses a major/minor version which is
|
||||
different than is in the name of the current
|
||||
"Misc/RPM/python-*.spec" file, rename the file:
|
||||
|
||||
% mv python-2.3.spec python-2.4.spec
|
||||
% cvs remove python-2.3.spec
|
||||
% cvs add python-2.4.spec
|
||||
% cvs commit
|
||||
|
||||
___ If this is a release candidate, mail Sean <jafo@tummy.com>
|
||||
noting the impending release, so that RPMs can be built and
|
||||
tested.
|
||||
|
||||
___ Update the README file, which has a big banner at the top
|
||||
proclaiming its identity.
|
||||
|
||||
|
|
Loading…
Reference in New Issue