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.

Author: Grinnz

AUTHORS

@@ -3,7 +3,8 @@
 # (hopefully) current and preferred email addresses from the commits.
 # These people have either submitted patches or suggestions, or their bug
 # reports or comments have inspired the appropriate patches.  Corrections,
-# additions, deletions welcome; send them to perlbug@perl.org, preferably
+# additions, deletions welcome; send them as a pull request to
+# https://github.com/Perl/perl5, or to perl5-porters@perl.org, preferably
 # as the output of diff(1), diff -u or diff -c between the original and a
 # corrected version of this file.
 #

Configure

@@ -1537,8 +1537,8 @@ case "$sh" in
 $me:  Fatal Error:  I can't find a Bourne Shell anywhere.
 
 Usually it's in /bin/sh.  How did you even get this far?
-Please contact me (Perl Maintainers) at perlbug@perl.org and
-we'll try to straighten this all out.
+Please contact me (Perl Maintainers) at https://github.com/Perl/perl5/issues
+and we'll try to straighten this all out.
 EOM
 	exit 1
 	;;
@@ -2121,7 +2121,7 @@ THIS PACKAGE SEEMS TO BE INCOMPLETE.
 You have the option of continuing the configuration process, despite the
 distinct possibility that your kit is damaged, by typing 'y'es.  If you
 do, don't blame me if something goes wrong.  I advise you to type 'n'o
-and contact the author (perlbug@perl.org).
+and contact the author (https://github.com/Perl/perl5/issues).
 
 EOM
 		echo $n "Continue? [n] $c" >&4
@@ -2401,7 +2401,7 @@ Much effort has been expended to ensure that this shell script will run on any
 Unix system.  If despite that it blows up on yours, your best bet is to edit
 Configure and run it again.  If you can't run Configure for some reason,
 you'll have to generate a config.sh file by hand.  Whatever problems you
-have, let me (perlbug@perl.org) know how I blew it.
+have, let me (https://github.com/Perl/perl5/issues) know how I blew it.
 
 This installation script affects things in two ways:
 
@@ -3370,7 +3370,7 @@ EOM
 	(cd $src/hints; ls -C *.sh) | $sed 's/\.sh/   /g' >&4
 	dflt=''
 	: Half the following guesses are probably wrong... If you have better
-	: tests or hints, please send them to perlbug@perl.org
+	: tests or hints, please send them to https://github.com/Perl/perl5/issues
 	: The metaconfig authors would also appreciate a copy...
 	$test -f /irix && osname=irix
 	$test -f /xenix && osname=sco_xenix
@@ -5788,7 +5788,7 @@ compile='
 mc_file=$1;
 shift;
 case "$usedevel" in $define|true|[yY]*) if $test ! -f "${mc_file}.c"; then
-echo "Internal Configure script bug - compiler test file ${mc_file}.c is missing. Please report this to perlbug@perl.org" >&4;
+echo "Internal Configure script bug - compiler test file ${mc_file}.c is missing. Please report this to https://github.com/Perl/perl5/issues" >&4;
 exit 1;
 fi;
 esac;
@@ -8784,7 +8784,7 @@ case "$shrpdir" in
 *)	$cat >&4 <<EOM
 WARNING:  Use of the shrpdir variable for the installation location of
 the shared $libperl is not supported.  It was never documented and
-will not work in this version.  Let me (perlbug@perl.org)
+will not work in this version.  Let me (https://github.com/Perl/perl5/issues)
 know of any problems this may cause.
 
 EOM

INSTALL

@@ -2384,30 +2384,28 @@ settings"> above.
 
 =head1 Reporting Problems
 
-Wherever possible please use the perlbug tool supplied with this Perl
-to report problems, as it automatically includes summary configuration
-information about your perl, which may help us track down problems far
-more quickly. But first you should read the advice in this file,
-carefully re-read the error message and check the relevant manual pages
-on your system, as these may help you find an immediate solution.
-Once you've exhausted the documentation, please report bugs to us using
-the 'perlbug' tool.
-
-The perlbug tool is installed along with perl, so after you have
-completed C<make install> it should be possible to run it with plain
-C<perlbug>.  If the install fails, or you want to report problems with
-C<make test> without installing perl, then you can use C<make nok> to
-run perlbug to report the problem, or run it by hand from this source
-directory with C<./perl -Ilib utils/perlbug>
-
-If the build fails too early to run perlbug uninstalled, then please
-B<run> the C<./myconfig> shell script, and mail its output along with
-an accurate description of your problem to perlbug@perl.org
+Please report problems to the GitHub issue tracker at
+https://github.com/Perl/perl5/issues, which will ask for the
+appropriate summary configuration information about your perl, which
+may help us track down problems far more quickly.  But first you should
+read the advice in this file, carefully re-read the error message and
+check the relevant manual pages on your system, as these may help you
+find an immediate solution.  Once you've exhausted the documentation,
+please report bugs to us using the GitHub tracker.
+
+The summary configuration information can be printed with C<perl -V>.
+If the install fails, or you want to report problems with C<make test>
+without installing perl, then you can run it by hand from this source
+directory with C<./perl -V>.
+
+If the build fails too early to run perl, then please
+B<run> the C<./myconfig> shell script, and include its output along
+with an accurate description of your problem.
 
 If Configure itself fails, and does not generate a config.sh file
-(needed to run C<./myconfig>), then please mail perlbug@perl.org the
+(needed to run C<./myconfig>), then please open an issue with the
 description of how Configure fails along with details of your system
--- for example the output from running C<uname -a>
+-- for example the output from running C<uname -a>.
 
 Please try to make your message brief but clear.  Brief, clear bug
 reports tend to get answered more quickly.  Please don't worry if your
@@ -2420,13 +2418,10 @@ config.sh or a complete Configure or make log) unless absolutely
 necessary.  Do not include a complete transcript of your build
 session.  Just include the failing commands, the relevant error
 messages, and whatever preceding commands are necessary to give the
-appropriate context.  Plain text should usually be sufficient -- fancy
-attachments or encodings may actually reduce the number of people who
-read your message.  Your message will get relayed to over 400
-subscribers around the world so please try to keep it brief but clear.
+appropriate context.
 
 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.
 

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

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.
 

Porting/pod_lib.pl

@@ -547,7 +547,7 @@ =head2 C<get_pod_metadata()>
 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 }

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
 

README

@@ -61,8 +61,7 @@ Perl is a large and complex system that's used for everything from
 knitting to rocket science.  If you run into trouble, it's quite
 likely that someone else has already solved the problem you're
 facing. Once you've exhausted the documentation, please report bugs to us
-using the 'perlbug' tool. For more information about perlbug, either type
-'perldoc perlbug' or just 'perlbug' on a line by itself.
+at the GitHub issue tracker at https://github.com/Perl/perl5/issues
 
 While it was current when we made it available, Perl is constantly evolving
 and there may be a more recent version that fixes bugs you've run into or

README.bs2000

@@ -8,7 +8,7 @@ about pod in pod/perlpod.pod or the short summary in the INSTALL file.
 perlbs2000 - building and installing Perl for BS2000.
 
 B<This document needs to be updated, but we don't know what it should say.
-Please email comments to L<perlbug@perl.org|mailto:perlbug@perl.org>.>
+Please submit comments to L<https://github.com/Perl/perl5/issues>.>
 
 =head1 SYNOPSIS
 

README.freebsd

@@ -36,5 +36,6 @@ C<argv[0]> value for C<$^X>.
 Nicholas Clark <nick@ccl4.org>, collating wisdom supplied by Slaven Rezic
 and Tim Bunce.
 
-Please report any errors, updates, or suggestions to L<mailto:perlbug@perl.org>.
+Please report any errors, updates, or suggestions to
+L<https://github.com/Perl/perl5/issues>.
 

README.irix

@@ -134,5 +134,6 @@ at least the shuffle.t and sort.t failures.
 
 Jarkko Hietaniemi <jhi@iki.fi>
 
-Please report any errors, updates, or suggestions to F<perlbug@perl.org>.
+Please report any errors, updates, or suggestions to
+L<https://github.com/Perl/perl5/issues>.
 

README.linux

@@ -35,5 +35,6 @@ is needed to get this working better.
 
 Steve Peters <steve@fisharerojo.org>
 
-Please report any errors, updates, or suggestions to F<perlbug@perl.org>.
+Please report any errors, updates, or suggestions to
+L<https://github.com/Perl/perl5/issues>.
 

README.macosx

@@ -122,8 +122,8 @@ on G5-based hosts.
 
 Support for 64-bit addressing is experimental: some aspects of Perl may be
 omitted or buggy. Note the messages output by F<Configure> for further 
-information. Please use C<perlbug> to submit a problem report in the
-event that you encounter difficulties.
+information. Please use L<https://github.com/Perl/perl5/issues> to submit a
+problem report in the event that you encounter difficulties.
 
 When building 64-bit modules, it is your responsibility to ensure that linked
 external libraries and frameworks provide 64-bit support: if they do not,

README.openbsd

@@ -26,5 +26,6 @@ will run into this problem.  If you want to run a threaded Perl on OpenBSD
 
 Steve Peters <steve@fisharerojo.org>
 
-Please report any errors, updates, or suggestions to F<perlbug@perl.org>.
+Please report any errors, updates, or suggestions to
+L<https://github.com/Perl/perl5/issues>.
 

README.os390

@@ -13,7 +13,7 @@ This document will help you Configure, build, test and install Perl
 on OS/390 (aka z/OS) Unix System Services.
 
 B<This document needs to be updated, but we don't know what it should say.
-Please email comments to L<perlbug@perl.org|mailto:perlbug@perl.org>.>
+Please submit comments to L<https://github.com/Perl/perl5/issues>.>
 
 =head1 DESCRIPTION
 

README.os400

@@ -7,7 +7,7 @@ designed to be readable as is.
 perlos400 - Perl version 5 on OS/400
 
 B<This document needs to be updated, but we don't know what it should say.
-Please email comments to L<perlbug@perl.org|mailto:perlbug@perl.org>.>
+Please submit comments to L<https://github.com/Perl/perl5/issues>.>
 
 =head1 DESCRIPTION
 

README.solaris

@@ -709,4 +709,5 @@ The original was written by Andy Dougherty F<doughera@lafayette.edu>
 drawing heavily on advice from Alan Burlison, Nick Ing-Simmons, Tim Bunce,
 and many other Solaris users over the years.
 
-Please report any errors, updates, or suggestions to F<perlbug@perl.org>.
+Please report any errors, updates, or suggestions to
+L<https://github.com/Perl/perl5/issues>.

README.vms

@@ -467,10 +467,9 @@ of the GNU cc headers.
 =head1 Reporting Bugs
 
 If you come across what you think might be a bug in Perl, please report
-it. There's a script in PERL_ROOT:[UTILS], perlbug, that walks you through
-the process of creating a bug report. This script includes details of your
-installation, and is very handy. Completed bug reports should go to
-perlbug@perl.org.
+it. The issue tracker at L<https://github.com/Perl/perl5/issues> walks you
+through the process of creating a bug report and including details of your
+installation.
 
 =head1 CAVEATS
 

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
 

hints/README.hints

@@ -9,7 +9,8 @@ can't or doesn't guess properly.  Most of these hint files have been
 tested with at least some version of perl5, but some are still left
 over from perl4.
 
-Please send any problems or suggested changes to perlbug@perl.org.
+Please send any problems or suggested changes to
+L<https://github.com/Perl/perl5/issues>.
 
 =head1 Hint file naming convention.
 

hints/bsdos.sh

@@ -125,7 +125,7 @@ $define|true|[yY]*)
 	*)   cat <<EOM >&4
 I did not know that BSD/OS $osvers supports POSIX threads.
 
-Feel free to tell perlbug@perl.org otherwise.
+Feel free to tell https://github.com/Perl/perl5/issues otherwise.
 EOM
 	    exit 1
 	    ;;

hints/freebsd.sh

@@ -207,7 +207,7 @@ $define|true|[yY]*)
 	0.*|1.*|2.0*|2.1*)   cat <<EOM >&4
 I did not know that FreeBSD $osvers supports POSIX threads.
 
-Feel free to tell perlbug@perl.org otherwise.
+Feel free to tell https://github.com/Perl/perl5/issues otherwise.
 EOM
 	      exit 1
 	      ;;

pod/perl.pod

@@ -428,11 +428,9 @@ displayed by diagnostics are internally stored as short integers,
 so they are limited to a maximum of 65535 (higher numbers usually being
 affected by wraparound).
 
-You may mail your bug reports (be sure to include full configuration
+You may submit your bug reports (be sure to include full configuration
 information as output by the myconfig program in the perl source
-tree, or by C<perl -V>) to perlbug@perl.org .  If you've succeeded
-in compiling perl, the L<perlbug> script in the F<utils/> subdirectory
-can be used to help mail in a bug report.
+tree, or by C<perl -V>) to L<https://github.com/Perl/perl5/issues>.
 
 Perl actually stands for Pathologically Eclectic Rubbish Lister, but
 don't tell anyone I said that.