--- a/doc/ChangeLog	Wed Mar 24 15:45:41 2010 -0400
+++ b/doc/ChangeLog	Wed Mar 24 15:48:25 2010 -0400
@@ -1,3 +1,7 @@
+2010-03-24  John W. Eaton  <jwe@octave.org>
+
+	* interpreter/bugs.txi: Update for bug tracker.
+
 2010-02-11  Jaroslav Hajek  <highegg@gmail.com>
 
 	* interpreter/expr.txi: Mention no ternary operator and the ifelse

--- a/doc/interpreter/bugs.txi	Wed Mar 24 15:45:41 2010 -0400
+++ b/doc/interpreter/bugs.txi	Wed Mar 24 15:48:25 2010 -0400
@@ -108,20 +108,9 @@
 In order for a bug report to serve its purpose, you must include the
 information that makes it possible to fix the bug.
 
-@findex bug_report
-
-If you have Octave working at all, the easiest way to prepare a complete
-bug report is to use the Octave function @code{bug_report}.  When you
-execute this function, Octave will prompt you for a subject and then
-invoke the editor on a file that already contains all the configuration
-information.  When you exit the editor, Octave will mail the bug report
-for you.
-
-@DOCSTRING(bug_report)
-
 @menu
 * Bug Criteria::                
-* Where: Bug Lists.             Where to send your bug report.
+* Where: Bug Tracker.           Where to submit your bug report.
 * Reporting: Bug Reporting.     How to report a bug effectively.
 * Patches: Sending Patches.     How to send a patch for Octave.
 @end menu
@@ -178,34 +167,24 @@
 for improvement are welcome in any case.
 @end itemize
 
-@node Bug Lists
+@node Bug Tracker
 @appendixsec Where to Report Bugs
-@cindex bug report mailing lists
+@cindex bug tracker
 @cindex reporting bugs
 @cindex bugs, reporting
 
-@findex bug_report
-
-If you have Octave working at all, the easiest way to prepare a complete
-bug report is to use the Octave function @code{bug_report}.  When you
-execute this function, Octave will prompt you for a subject and then
-invoke the editor on a file that already contains all the configuration
-information.  When you exit the editor, Octave will mail the bug report
-for you.
-
-If for some reason you cannot use Octave's @code{bug_report} function,
-send bug reports for Octave to @email{bug@@octave.org}.
+To report a bug in Octave, submit a bug report to the Octave bug tracker
+@url{http://bugs.octave.org}.
 
 @strong{Do not send bug reports to @samp{help-octave}}.  Most users of
-Octave do not want to receive bug reports.  Those that do have asked to
-be on the mailing list.
+Octave do not want to receive bug reports.
 
 @node Bug Reporting
 @appendixsec How to Report Bugs
 @cindex bugs, reporting
 
-Send bug reports for Octave to one of the addresses listed in
-@ref{Bug Lists}.
+Submit bug reports for Octave to the Octave bug tracker
+@url{http://bugs.octave.org}.
 
 The fundamental principle of reporting bugs usefully is this:
 @strong{report all the facts}.  If you are not sure whether to state a
@@ -418,7 +397,9 @@
 @strong{Please do not} send requests to be added or removed from the
 mailing list, or other administrative trivia to the list itself.
 
-If you think you have found a bug in the installation procedure,
-however, you should send a complete bug report for the problem to
-@email{bug@@octave.org}.  @xref{Bug Reporting}, for
-information that will help you to submit a useful report.
+If you think you have found a bug in Octave or in the installation
+procedure, however, you should submit a complete bug report to
+the Octave bug tracker at @url{http://bugs.octave.org}.
+But before you submit a bug report, please read
+@url{http://www.octave.org/bugs.html} to learn how to submit a useful
+bug report.

--- a/src/ChangeLog	Wed Mar 24 15:45:41 2010 -0400
+++ b/src/ChangeLog	Wed Mar 24 15:48:25 2010 -0400
@@ -1,3 +1,8 @@
+2010-03-24  John W. Eaton  <jwe@octave.org>
+
+	* version.h.in (OCTAVE_BUGS_STATEMENT): Point to
+	http://www.octave.org/bugs.html, not the mailing list.
+
 2010-03-24  John W. Eaton  <jwe@octave.org>
 
 	* DLD-FUNCTIONS/config-module.awk: Emit additions to EXTRA_DIST.

--- a/src/version.h.in	Wed Mar 24 15:45:41 2010 -0400
+++ b/src/version.h.in	Wed Mar 24 15:48:25 2010 -0400
@@ -62,8 +62,7 @@
 For more information, visit http://www.octave.org/help-wanted.html"
 
 #define OCTAVE_BUGS_STATEMENT \
-  "Report bugs to <bug@octave.org> (but first, please read\n\
-http://www.octave.org/bugs.html to learn how to write a helpful report)."
+  "Read http://www.octave.org/bugs.html to learn how to submit bug reports."
 
 #define OCTAVE_NAME_VERSION_AND_COPYRIGHT \
   OCTAVE_NAME_AND_VERSION "\n" \