[Python-checkins] python/nondist/peps pep-0102.txt,1.6,1.7

[mwh@users.sourceforge.net]

Update of /cvsroot/python/python/nondist/peps
In directory usw-pr-cvs1:/tmp/cvs-serv19419/nondist/peps

Modified Files:
	pep-0102.txt 
Log Message:
Woo, these changes have been sitting around for a while.
Just a couple of things learnt from 221.


Index: pep-0102.txt
===================================================================
RCS file: /cvsroot/python/python/nondist/peps/pep-0102.txt,v
retrieving revision 1.6
retrieving revision 1.7
diff -C2 -d -r1.6 -r1.7
*** pep-0102.txt	11 Apr 2002 14:30:15 -0000	1.6
--- pep-0102.txt	12 Aug 2002 11:42:43 -0000	1.7
***************
*** 109,113 ****
        news.txt file looking for interesting things to add to NEWS.
  
!   ___ Check your NEWS changes into the maintenance branch.
  
    ___ Once the release is underway, Fred Drake needs to create the 
--- 109,114 ----
        news.txt file looking for interesting things to add to NEWS.
  
!   ___ Check your NEWS changes into the maintenance branch.  It's easy
!       to forget to update the release date in this file!
  
    ___ Once the release is underway, Fred Drake needs to create the 
***************
*** 167,171 ****
        as far as we know, and 2) we're going to max out the compression
        level, which isn't a supported option.
!       % tar cf - Python-2.1.2 | gzip -9 > Python-2.1.2.tgz
  
    ___ Calculate the MD5 checksum of the tgz file you just created
--- 168,172 ----
        as far as we know, and 2) we're going to max out the compression
        level, which isn't a supported option.
!       % tar -cf - Python-2.1.2 | gzip -9 > Python-2.1.2.tgz
  
    ___ Calculate the MD5 checksum of the tgz file you just created
***************
*** 220,223 ****
--- 221,235 ----
          python.org; this contains the "full scoop" of changes to
          Python since the previous release for this version of Python.
+ 
+         If this is the first release in a series (e.g. 2.2.1c1) then
+         you'll need to create a new directory (e.g. 2.2.1).  It's
+         probably best to copy the last directory across:
+ 
+         % cp -r 2.2 2.2.1
+         % rm -rf 2.2.1/CVS
+         % cvs add 2.2.1
+ 
+         and then make changes as needed.  Verbiage from prereleases of
+         previous versions can be found in CVS if you're feeling uninspired.
  
      ___ Also, update the MD5 checksums.