[Python-checkins] CVS: python/nondist/peps pep-0001.txt,1.24,1.25

[Barry Warsaw]

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

Modified Files:
	pep-0001.txt 
Log Message:
Add a Last-Modified: header.

Add a short description of the format for both the Author: and
Post-History: headers.

Elaborate a bit about how and where PEP discussions should be held.


Index: pep-0001.txt
===================================================================
RCS file: /cvsroot/python/python/nondist/peps/pep-0001.txt,v
retrieving revision 1.24
retrieving revision 1.25
diff -C2 -d -r1.24 -r1.25
*** pep-0001.txt	2001/08/14 16:48:57	1.24
--- pep-0001.txt	2001/08/14 22:04:52	1.25
***************
*** 2,5 ****
--- 2,6 ----
  Title: PEP Purpose and Guidelines
  Version: $Revision$
+ Last-Modified: $Date$
  Author: barry@zope.com (Barry A. Warsaw),
      jeremy@zope.com (Jeremy Hylton)
***************
*** 86,92 ****
      will not be accepted.  However, wherever possible, long open-ended
      discussions on public mailing lists should be avoided.  A better
!     strategy is to encourage public feedback directly to the PEP
!     author, who collects and integrates the comments back into the
!     PEP.
  
      Once the authors have completed a PEP, they must inform the PEP
--- 87,95 ----
      will not be accepted.  However, wherever possible, long open-ended
      discussions on public mailing lists should be avoided.  A better
!     strategy is to encourage public feedback be sent directly to the
!     PEP author during the early draft phases, who collects and
!     integrates the comments back into the PEP.  Before code is
!     committed to CVS in a non-experimental way though, discussion must
!     be moved back to the python-dev and/or python-list mailing lists.
  
      Once the authors have completed a PEP, they must inform the PEP
***************
*** 193,196 ****
--- 196,208 ----
        * Replaced-By: <pep number>
  
+     The Author: header lists the email addresses and names of all the
+     authors/owners of the PEP.  The format of the author entry should
+     be
+ 
+         address@dom.ain (Random J. User)
+ 
+     and if there are multiple authors, each should be on a separate
+     line following RFC 822 continuation line conventions.
+ 
      Standards track PEPs must have a Python-Version: header which
      indicates the version of Python that the feature will be released
***************
*** 203,206 ****
--- 215,222 ----
      the author, or on the python-list or python-dev email mailing
      lists.
+ 
+     Post-History: is used to record the dates of when new versions of
+     the PEP are posted to python-list and/or python-dev.  The should
+     be in dd-mmm-yyyy format, e.g. 14-Aug-2001.
  
      PEPs may have a Requires: header, indicating the PEP numbers that