[Python-checkins] python/nondist/peps pep-0101.txt,1.38,1.39

bwarsaw at users.sourceforge.net bwarsaw at users.sourceforge.net
Sun Sep 21 21:11:37 EDT 2003


Update of /cvsroot/python/python/nondist/peps
In directory sc8-pr-cvs1:/tmp/cvs-serv24848

Modified Files:
	pep-0101.txt 
Log Message:
More updates from Sean.


Index: pep-0101.txt
===================================================================
RCS file: /cvsroot/python/python/nondist/peps/pep-0101.txt,v
retrieving revision 1.38
retrieving revision 1.39
diff -C2 -d -r1.38 -r1.39
*** pep-0101.txt	22 Sep 2003 01:01:46 -0000	1.38
--- pep-0101.txt	22 Sep 2003 01:11:35 -0000	1.39
***************
*** 140,143 ****
--- 140,167 ----
        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 at 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.
***************
*** 176,182 ****
          file from the distribution.
  
!   ___ For a final release, edit the first paragraph of 
        Doc/whatsnew/whatsnewXX.tex to include the actual release date;
!       e.g. "Python 2.3 was released on August 1, 2003."  
        There's no need to edit this for alpha or beta releases.  Note
        that Andrew often takes care of this.
--- 200,206 ----
          file from the distribution.
  
!   ___ For a final release, edit the first paragraph of
        Doc/whatsnew/whatsnewXX.tex to include the actual release date;
!       e.g. "Python 2.3 was released on August 1, 2003."
        There's no need to edit this for alpha or beta releases.  Note
        that Andrew often takes care of this.





More information about the Python-checkins mailing list