summaryrefslogtreecommitdiff
path: root/Porting/todo.pod
diff options
context:
space:
mode:
authorDan Book <grinnz@grinnz.com>2019-11-26 19:02:22 -0500
committerKarl Williamson <khw@cpan.org>2019-11-26 17:54:20 -0800
commitb4285b0dabe98fc37362ed5367ba070593c8cbbc (patch)
treecf396f488d63e2cac3e838345fdf568aa2d528c8 /Porting/todo.pod
parent5225e517f9c17c6c8221540e7d29bc1cf6e651c1 (diff)
downloadperl-b4285b0dabe98fc37362ed5367ba070593c8cbbc.tar.gz
Update Porting documents to reference GitHub issues
Diffstat (limited to 'Porting/todo.pod')
-rw-r--r--Porting/todo.pod19
1 files changed, 10 insertions, 9 deletions
diff --git a/Porting/todo.pod b/Porting/todo.pod
index 4fcf4cc782..df78df9957 100644
--- a/Porting/todo.pod
+++ b/Porting/todo.pod
@@ -25,17 +25,18 @@ programming languages offer you 1 line of immortality?
=head1 Tasks that only need Perl knowledge
-=head2 Classify bug tickets by type
+=head2 Label bug tickets by type
-Known bugs in Perl are tracked by L<https://rt.perl.org/> (which also
-includes Perl 6). A summary can be found at
-L<https://rt.perl.org/NoAuth/perl5/Overview.html>.
-It shows bugs classified by "type". However, the type of many of the
-bugs is "unknown". This greatly lowers the chances of them getting
+Known bugs in Perl are tracked by L<https://github.com/Perl/perl5/issues>.
+It shows bugs and can be filtered by assigned labels. However, many are
+L<unlabeled|https://github.com/Perl/perl5/issues?q=is%3Aopen+is%3Aissue+no%3Alabel>
+or have the label L<"Needs Triage"|https://github.com/Perl/perl5/issues?q=is%3Aopen+is%3Aissue+label%3A%22Needs+Triage%22>.
+This greatly lowers the chances of them getting
fixed, as the number of open bugs is overwhelming -- too many to wade
through for someone to try to find the bugs in the parts of
Perl that s/he knows well enough to try to fix. This task involves
-going through these bugs and classifying them into one or more types.
+going through these bugs and assigning one or more labels, and removing the
+"Needs Triage" label if present.
=head2 Ongoing: investigate new bug reports
@@ -44,8 +45,8 @@ a quick investigation to see if it is a real problem, and to reply to
the poster about it, asking for example code that reproduces the
problem. Such code should be added to the test suite as TODO tests, and
the ticket should be classified by type. To get started on this task,
-look at the tickets that are marked as "New Issues" in
-L<https://rt.perl.org/NoAuth/perl5/Overview.html>.
+look at the issues with no comments at
+L<https://github.com/Perl/perl5/issues?q=is%3Aopen+is%3Aissue+comments%3A0>.
=head2 Migrate t/ from custom TAP generation