Update documentation, readmes, comments, and utilities to reference the GitHub issue tracker

The perlbug utility and perlbug@perl.org should no longer be used to submit bug reports or patches.

4 files changed, 10 insertions, 13 deletions

diff --git a/Porting/how_to_write_a_perldelta.pod b/Porting/how_to_write_a_perldelta.pod
index 73c17c9ed2..1934b7484f 100644
--- a/Porting/how_to_write_a_perldelta.pod
+++ b/Porting/how_to_write_a_perldelta.pod
@@ -165,7 +165,7 @@ for the particular file in core.)
 
 =item Utility Changes
 
-Changes to installed programs such as F<perlbug> and F<xsubpp> go here. Most
+Changes to installed programs such as F<perldoc> and F<xsubpp> go here. Most
 of these are built within the directory F<utils>.
 
 =item New Documentation
diff --git a/Porting/perldelta_template.pod b/Porting/perldelta_template.pod
index ca24d00f9a..15d6a2222a 100644
--- a/Porting/perldelta_template.pod
+++ b/Porting/perldelta_template.pod
@@ -157,8 +157,8 @@ XXX Description of the purpose of the new file here
 =head2 Changes to Existing Documentation
 
 We have attempted to update the documentation to reflect the changes
-listed in this document.  If you find any we have missed, send email
-to L<perlbug@perl.org|mailto:perlbug@perl.org>.
+listed in this document.  If you find any we have missed, open an issue
+at L<https://github.com/Perl/perl5/issues>.
 
 XXX Changes which significantly change existing files in F<pod/> go here.
 However, any changes to F<pod/perldiag.pod> should go in the L</Diagnostics>
@@ -224,7 +224,7 @@ XXX Describe change here
 
 =head1 Utility Changes
 
-XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go here.
+XXX Changes to installed programs such as F<perldoc> and F<xsubpp> go here.
 Most of these are built within the directory F<utils>.
 
 [ List utility changes as a =head2 entry for each utility and =item
@@ -411,13 +411,12 @@ If you find what you think is a bug, you might check the perl bug database
 at L<https://github.com/Perl/perl5/issues>.  There may also be information at
 L<http://www.perl.org/>, the Perl Home Page.
 
-If you believe you have an unreported bug, please run the L<perlbug> program
-included with your release.  Be sure to trim your bug down to a tiny but
-sufficient test case.  Your bug report, along with the output of C<perl -V>,
-will be sent off to perlbug@perl.org to be analysed by the Perl porting team.
+If you believe you have an unreported bug, please open an issue at
+L<https://github.com/Perl/perl5/issues>.  Be sure to trim your bug down to a
+tiny but sufficient test case.
 
 If the bug you are reporting has security implications which make it
-inappropriate to send to a publicly archived mailing list, then see
+inappropriate to send to a public issue tracker, then see
 L<perlsec/SECURITY VULNERABILITY CONTACT INFORMATION>
 for details of how to report the issue.
 
diff --git a/Porting/pod_lib.pl b/Porting/pod_lib.pl
index 25cf691bf2..f2d854408e 100644
--- a/Porting/pod_lib.pl
+++ b/Porting/pod_lib.pl
@@ -547,7 +547,7 @@ Hash reference; each element provides either a list or a lookup table for
 information about various types of POD files.
 
   'aux'             => [ # utility programs like
-                            'h2xs' and 'perlbug' ]
+                            'h2xs' and 'perldoc' ]
   'generated'       => { # lookup table for generated POD files
                             like 'perlapi.pod' }
   'ignore'          => { # lookup table for files to be ignored }
diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod
index 766d1a24ff..ac8d2098e3 100644
--- a/Porting/release_managers_guide.pod
+++ b/Porting/release_managers_guide.pod
@@ -1109,9 +1109,7 @@ Test L<perlbug> with the following:
     Action (Send/Display/Edit/Subject/Save to File): Q
 
 and carefully examine the output (in F<perlbug.rep]>), especially
-the "Locally applied patches" section. If everything appears okay, then
-delete the file, and try it again, this time actually submitting the bug
-report. Check that it shows up, then remember to close it!
+the "Locally applied patches" section.
 
 =for checklist skip BLEAD-POINT