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.

1 files changed, 6 insertions, 7 deletions

diff --git a/README.win32 b/README.win32
index b7d0784762..531318908f 100644
--- a/README.win32
+++ b/README.win32
@@ -685,8 +685,8 @@ or any invocation of make.
 If a module does not build for some reason, look carefully for
 why it failed, and report problems to the module author.  If
 it looks like the extension building support is at fault, report
-that with full details of how the build failed using the perlbug
-utility.
+that with full details of how the build failed using the GitHub
+issue tracker at L<https://github.com/Perl/perl5/issues>.
 
 =item Command-line Wildcard Expansion
 
@@ -874,9 +874,8 @@ executable built during the installation process.  Usage is exactly
 the same as normal C<perl> on Windows, except that options like C<-h>
 don't work (since they need a command-line window to print to).
 
-If you find bugs in perl, you can run C<perlbug> to create a
-bug report (you may have to send it manually if C<perlbug> cannot
-find a mailer on your system).
+If you find bugs in perl, you can report them to
+L<https://github.com/Perl/perl5/issues>.
 
 =head1 BUGS AND CAVEATS
 
@@ -924,8 +923,8 @@ variable in the handler.  Using signals under this port should
 currently be considered unsupported.
 
 Please send detailed descriptions of any problems and solutions that
-you may find to E<lt>F<perlbug@perl.org>E<gt>, along with the output
-produced by C<perl -V>.
+you may find to E<lt>L<https://github.com/Perl/perl5/issues>E<gt>,
+along with the output produced by C<perl -V>.
 
 =head1 ACKNOWLEDGEMENTS