[Python-checkins] r57394 - python/branches/release25-maint/Doc/commontex/reportingbugs.tex

georg.brandl python-checkins at python.org
Fri Aug 24 19:20:41 CEST 2007


Author: georg.brandl
Date: Fri Aug 24 19:20:41 2007
New Revision: 57394

Modified:
   python/branches/release25-maint/Doc/commontex/reportingbugs.tex
Log:
Bug #1010: docs url points to SF.net, now points to bugs.python.org.


Modified: python/branches/release25-maint/Doc/commontex/reportingbugs.tex
==============================================================================
--- python/branches/release25-maint/Doc/commontex/reportingbugs.tex	(original)
+++ python/branches/release25-maint/Doc/commontex/reportingbugs.tex	Fri Aug 24 19:20:41 2007
@@ -10,8 +10,8 @@
 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
+All bug reports should be submitted via the Python Bug Tracker at
+(\url{http://bugs.python.org}).  The
 bug tracker offers a Web form which allows pertinent information to be
 entered and submitted to the developers.
 
@@ -21,25 +21,24 @@
 fix it; it may be that the problem has already been fixed for the next
 release, or additional information is needed (in which case you are
 welcome to provide it if you can!).  To do this, search the bug
-database using the search box on the left side of the page.
+database using the search box on the top side of the page.
 
 If the problem you're reporting is not already in the bug tracker, go
-back to the Python Bug Tracker
-(\url{http://sourceforge.net/bugs/?group_id=5470}).  Select the
-``Submit a Bug'' link at the top of the page to open the bug reporting
+back to the Python Bug Tracker.  Select the
+``Create new'' link at the left of the page to open the bug reporting
 form.
 
 The submission form has a number of fields.  The only fields that are
-required are the ``Summary'' and ``Details'' fields.  For the summary,
+required are the ``Title'' and ``Type'' fields.  For the title,
 enter a \emph{very} short description of the problem; less than ten
-words is good.  In the Details field, describe the problem in detail,
+words is good.  In the ``Change Note'' field, describe the problem in detail,
 including what you expected to happen and what did happen.  Be sure to
 include the version of Python you used, whether any extension modules
 were involved, and what hardware and software platform you were using
 (including version information as appropriate).
 
-The only other field that you may want to set is the ``Category''
-field, which allows you to place the bug report into a broad category
+The only other field that you may want to set is the ``Components''
+field, which allows you to place the bug report into broad categories
 (such as ``Documentation'' or ``Library'').
 
 Each bug report will be assigned to a developer who will determine


More information about the Python-checkins mailing list