perldelta - what is new for perl v5.29.0
This document describes differences between the 5.28.0 release and the 5.29.0 release.
If you are upgrading from an earlier release such as 5.27.0, first read perl5280delta, which describes differences between 5.27.0 and 5.28.0.
This usage has been deprecated and scheduled for removal in 5.30. See "Use of unassigned code point or non-standalone grapheme for a delimiter." in perldeprecation
Archive::Tar has been upgraded from version 2.28 to 2.30.
feature has been upgraded from version 1.52 to 1.53.
Module::CoreList has been upgraded from version 5.20180622 to 5.20180626.
Unicode::UCD has been upgraded from version 0.70 to 0.71.
Perl 5.29.0 represents approximately 1 week of development since Perl 5.28.0 and contains approximately 320,000 lines of changes across 79 files from 4 authors.
Excluding auto-generated files, documentation and release tools, there were approximately 310,000 lines of changes to 30 .pm, .t, .c and .h files.
Perl continues to flourish into its fourth decade thanks to a vibrant community of users and developers. The following people are known to have contributed the improvements that became Perl 5.29.0:
Abigail, James E Keenan, Karl Williamson, Sawyer X.
The list above is almost certainly incomplete as it is automatically generated from version control history. In particular, it does not include the names of the (very much appreciated) contributors who reported issues to the Perl bug tracker.
Many of the changes included in this version originated in the CPAN modules included in Perl's core. We're grateful to the entire CPAN community for helping Perl to flourish.
For a more complete list of all of Perl's historical contributors, please see the AUTHORS file in the Perl source distribution.
If you find what you think is a bug, you might check the perl bug database at https://rt.perl.org/ . There may also be information at http://www.perl.org/ , the Perl Home Page.
If you believe you have an unreported bug, please run the 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 perl -V, will be sent off to perlbug@perl.org to be analysed by the Perl porting team.
If the bug you are reporting has security implications which make it inappropriate to send to a publicly archived mailing list, then see "SECURITY VULNERABILITY CONTACT INFORMATION" in perlsec for details of how to report the issue.
If you wish to thank the Perl 5 Porters for the work we had done in Perl 5, you can do so by running the perlthanks program:
perlthanksThis will send an email to the Perl 5 Porters list with your show of thanks.
The Changes file for an explanation of how to view exhaustive details on what changed.
The INSTALL file for how to build Perl.
The README file for general stuff.
The Artistic and Copying files for copyright information.