[Python-checkins] CVS: python/dist/src/Doc/texinputs reportingbugs.tex,1.1,1.2

[Fred L. Drake]

Update of /cvsroot/python/python/dist/src/Doc/texinputs
In directory usw-pr-cvs1:/tmp/cvs-serv20884/texinputs

Modified Files:
	reportingbugs.tex 
Log Message:
Update the instructions on reporting bugs to reflect that anonymous reports
are no longer accepted.


Index: reportingbugs.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/texinputs/reportingbugs.tex,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** reportingbugs.tex	2000/09/21 21:32:14	1.1
--- reportingbugs.tex	2002/02/04 21:43:08	1.2
***************
*** 6,9 ****
--- 6,14 ----
  or its documentation.
  
+ Before submitting a report, you will be required to log into SourceForge;
+ this will make it possible for the developers to contact you
+ for additional information if needed.  It is not possible to submit a
+ bug report anonymously.
+ 
  All bug reports should be submitted via the Python Bug Tracker on
  SourceForge (\url{http://sourceforge.net/bugs/?group_id=5470}).  The
***************
*** 11,22 ****
  entered and submitted to the developers.
  
- Before submitting a report, please log into SourceForge if you are a
- member; this will make it possible for the developers to contact you
- for additional information if needed.  If you are not a SourceForge
- member but would not mind the developers contacting you, you may
- include your email address in your bug description.  In this case,
- please realize that the information is publically available and cannot
- be protected.
- 
  The first step in filing a report is to determine whether the problem
  has already been reported.  The advantage in doing so, aside from
--- 16,19 ----
***************
*** 47,52 ****
  
  Each bug report will be assigned to a developer who will determine
! what needs to be done to correct the problem.  If you have a
! SourceForge account and logged in to report the problem, you will
  receive an update each time action is taken on the bug.
  
--- 44,48 ----
  
  Each bug report will be assigned to a developer who will determine
! what needs to be done to correct the problem.  You will
  receive an update each time action is taken on the bug.