5 perl5330delta - what is new for perl v5.33.0
9 This document describes differences between the 5.32.0 release and the 5.33.0
12 If you are upgrading from an earlier release such as 5.30.0, first read
13 L<perl5320delta>, which describes differences between 5.30.0 and 5.32.0.
15 =head1 Modules and Pragmata
17 =head2 Updated Modules and Pragmata
23 L<feature> has been upgraded from version 1.58 to 1.59.
27 L<Module::CoreList> has been upgraded from version 5.20200620 to 5.20200717.
31 =head1 Acknowledgements
33 Perl 5.33.0 represents approximately 4 weeks of development since Perl
34 5.32.0 and contains approximately 4,300 lines of changes across 47 files
37 Excluding auto-generated files, documentation and release tools, there were
38 approximately 69 lines of changes to 9 .pm, .t, .c and .h files.
40 Perl continues to flourish into its fourth decade thanks to a vibrant
41 community of users and developers. The following people are known to have
42 contributed the improvements that became Perl 5.33.0:
44 Andy Dougherty, Dagfinn Ilmari Mannsåker, Eric Herman, Karen Etheridge,
45 Leon Timmermans, Sawyer X.
47 The list above is almost certainly incomplete as it is automatically
48 generated from version control history. In particular, it does not include
49 the names of the (very much appreciated) contributors who reported issues to
52 Many of the changes included in this version originated in the CPAN modules
53 included in Perl's core. We're grateful to the entire CPAN community for
54 helping Perl to flourish.
56 For a more complete list of all of Perl's historical contributors, please
57 see the F<AUTHORS> file in the Perl source distribution.
61 If you find what you think is a bug, you might check the perl bug database
62 at L<https://github.com/Perl/perl5/issues>. There may also be information at
63 L<http://www.perl.org/>, the Perl Home Page.
65 If you believe you have an unreported bug, please open an issue at
66 L<https://github.com/Perl/perl5/issues>. Be sure to trim your bug down to a
67 tiny but sufficient test case.
69 If the bug you are reporting has security implications which make it
70 inappropriate to send to a public issue tracker, then see
71 L<perlsec/SECURITY VULNERABILITY CONTACT INFORMATION>
72 for details of how to report the issue.
76 If you wish to thank the Perl 5 Porters for the work we had done in Perl 5,
77 you can do so by running the C<perlthanks> program:
81 This will send an email to the Perl 5 Porters list with your show of thanks.
85 The F<Changes> file for an explanation of how to view exhaustive details on
88 The F<INSTALL> file for how to build Perl.
90 The F<README> file for general stuff.
92 The F<Artistic> and F<Copying> files for copyright information.