Fixup rt.perl.org/rt3 => rt.perl.org

These links all would redirect properly, but give out the top URL.

diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod
index 87ce797..37ccf37 100644 (file)
--- a/Porting/release_managers_guide.pod
+++ b/Porting/release_managers_guide.pod
@@ -1276,7 +1276,7 @@ fields C<Perl Version> and C<Fixed In>. The easiest way to determine this is to
 open up any ticket for modification and check the drop downs next to the
 C<Perl Version> and C<Fixed In> labels.
 
-Here, try this link: L<https://rt.perl.org/rt3/Ticket/Modify.html?id=10000>
+Here, try this link: L<https://rt.perl.org/Ticket/Modify.html?id=10000>
 
 If the new version is not listed there, send an email to C<perlbug-admin at
 perl.org> requesting this.

diff --git a/Porting/todo.pod b/Porting/todo.pod
index 1c283e2..4deb52f 100644 (file)
--- a/Porting/todo.pod
+++ b/Porting/todo.pod
@@ -41,9 +41,9 @@ documentation.  This would be a good way to learn more about Perl.
 
 =head2 Classify bug tickets by type
 
-Known bugs in Perl are tracked by L<https://rt.perl.org/rt3> (which also
+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/rt3/NoAuth/perl5/Overview.html>.
+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
 fixed, as the number of open bugs is overwhelming -- too many to wade
@@ -59,7 +59,7 @@ 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/rt3/NoAuth/perl5/Overview.html>.
+L<https://rt.perl.org/NoAuth/perl5/Overview.html>.
 
 =head2 Migrate t/ from custom TAP generation