--- /dev/null
+=encoding utf8
+
+=head1 NAME
+
+perl52711delta - what is new for perl v5.27.11
+
+=head1 DESCRIPTION
+
+This document describes differences between the 5.27.10 release and the 5.27.11
+release.
+
+If you are upgrading from an earlier release such as 5.27.9, first read
+L<perl52710delta>, which describes differences between 5.27.9 and 5.27.10.
+
+=head1 Security
+
+=head2 [CVE-2017-12837] Heap buffer overflow in regular expression compiler
+
+Compiling certain regular expression patterns with the case-insensitive
+modifier could cause a heap buffer overflow and crash perl. This has now been
+fixed.
+L<[perl #131582]|https://rt.perl.org/Public/Bug/Display.html?id=131582>
+
+=head2 [CVE-2017-12883] Buffer over-read in regular expression parser
+
+For certain types of syntax error in a regular expression pattern, the error
+message could either contain the contents of a random, possibly large, chunk of
+memory, or could crash perl. This has now been fixed.
+L<[perl #131598]|https://rt.perl.org/Public/Bug/Display.html?id=131598>
+
+=head2 [CVE-2017-12814] C<$ENV{$key}> stack buffer overflow on Windows
+
+A possible stack buffer overflow in the C<%ENV> code on Windows has been fixed
+by removing the buffer completely since it was superfluous anyway.
+L<[perl #131665]|https://rt.perl.org/Public/Bug/Display.html?id=131665>
+
+=head1 Performance Enhancements
+
+=over 4
+
+=item *
+
+The start up overhead for creating regular expression patterns with
+Unicode properties (C<\p{...}>) has been greatly reduced in most cases.
+
+=back
+
+=head1 Modules and Pragmata
+
+=head2 Updated Modules and Pragmata
+
+=over 4
+
+=item *
+
+L<bytes> has been upgraded from version 1.05 to 1.06.
+
+=item *
+
+L<Carp> has been upgraded from version 1.49 to 1.50.
+
+=item *
+
+L<Devel::PPPort> has been upgraded from version 3.39 to 3.40.
+
+=item *
+
+L<Exporter> has been upgraded from version 5.72 to 5.73.
+
+=item *
+
+L<ExtUtils::Constant> has been upgraded from version 0.24 to 0.25.
+
+=item *
+
+L<I18N::Langinfo> has been upgraded from version 0.16 to 0.17.
+
+=item *
+
+L<IO> has been upgraded from version 1.38 to 1.39.
+
+=item *
+
+L<Module::CoreList> has been upgraded from version 5.20180221 to 5.20180420.
+
+=item *
+
+L<POSIX> has been upgraded from version 1.83 to 1.84.
+
+=item *
+
+L<subs> has been upgraded from version 1.02 to 1.03.
+
+=item *
+
+L<Time::HiRes> has been upgraded from version 1.9757 to 1.9759.
+
+=item *
+
+L<vars> has been upgraded from version 1.03 to 1.04.
+
+=item *
+
+L<version> has been upgraded from version 0.9918 to 0.9923.
+
+=back
+
+=head1 Documentation
+
+XXX Changes to files in F<pod/> go here. Consider grouping entries by
+file and be sure to link to the appropriate page, e.g. L<perlfunc>.
+
+=head2 New Documentation
+
+XXX Changes which create B<new> files in F<pod/> go here.
+
+=head3 L<XXX>
+
+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>.
+
+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>
+section.
+
+Additionally, the following selected changes have been made:
+
+=head3 L<XXX>
+
+=over 4
+
+=item *
+
+XXX Description of the change here
+
+=back
+
+=head1 Diagnostics
+
+The following additions or changes have been made to diagnostic output,
+including warnings and fatal error messages. For the complete list of
+diagnostic messages, see L<perldiag>.
+
+XXX New or changed warnings emitted by the core's C<C> code go here. Also
+include any changes in L<perldiag> that reconcile it to the C<C> code.
+
+=head2 New Diagnostics
+
+XXX Newly added diagnostic messages go under here, separated into New Errors
+and New Warnings
+
+=head3 New Errors
+
+=over 4
+
+=item *
+
+XXX L<message|perldiag/"message">
+
+=back
+
+=head3 New Warnings
+
+=over 4
+
+=item *
+
+XXX L<message|perldiag/"message">
+
+=back
+
+=head2 Changes to Existing Diagnostics
+
+XXX Changes (i.e. rewording) of diagnostic messages go here
+
+=over 4
+
+=item *
+
+XXX Describe change here
+
+=back
+
+=head1 Acknowledgements
+
+Perl 5.27.11 represents approximately 4 weeks of development since Perl
+5.27.10 and contains approximately 440,000 lines of changes across 200 files
+from 21 authors.
+
+Excluding auto-generated files, documentation and release tools, there were
+approximately 440,000 lines of changes to 88 .pm, .t, .c and .h files.
+
+Perl continues to flourish into its third decade thanks to a vibrant
+community of users and developers. The following people are known to have
+contributed the improvements that became Perl 5.27.11:
+
+Aaron Crane, Alexandr Savca, Chris 'BinGOs' Williams, Dagfinn Ilmari
+Mannsåker, Daniel Dragan, David Mitchell, H.Merijn Brand, James E Keenan,
+John Peacock, Karl Williamson, Marc-Philip Werner, Nicholas Clark, Pali,
+Ricardo Signes, Sawyer X, Sergey Aleynikov, Steve Hay, Todd Rinaldo, Tony
+Cook, Yves Orton, Zefram.
+
+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 F<AUTHORS> file in the Perl source distribution.
+
+=head1 Reporting Bugs
+
+If you find what you think is a bug, you might check the perl bug database
+at L<https://rt.perl.org/> . 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 the bug you are reporting has security implications which make it
+inappropriate to send to a publicly archived mailing list, then see
+L<perlsec/SECURITY VULNERABILITY CONTACT INFORMATION>
+for details of how to report the issue.
+
+=head1 Give Thanks
+
+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 C<perlthanks> program:
+
+ perlthanks
+
+This will send an email to the Perl 5 Porters list with your show of thanks.
+
+=head1 SEE ALSO
+
+The F<Changes> file for an explanation of how to view exhaustive details on
+what changed.
+
+The F<INSTALL> file for how to build Perl.
+
+The F<README> file for general stuff.
+
+The F<Artistic> and F<Copying> files for copyright information.
+
+=cut
=head1 NAME
-perldelta - what is new for perl v5.27.11
+[ this is a template for a new perldelta file. Any text flagged as XXX needs
+to be processed before release. ]
+
+perldelta - what is new for perl v5.27.12
=head1 DESCRIPTION
-This document describes differences between the 5.27.10 release and the 5.27.11
+This document describes differences between the 5.27.11 release and the 5.27.12
release.
-If you are upgrading from an earlier release such as 5.27.9, first read
-L<perl52710delta>, which describes differences between 5.27.9 and 5.27.10.
+If you are upgrading from an earlier release such as 5.27.10, first read
+L<perl52711delta>, which describes differences between 5.27.10 and 5.27.11.
+
+=head1 Notice
+
+XXX Any important notices here
+
+=head1 Core Enhancements
+
+XXX New core language features go here. Summarize user-visible core language
+enhancements. Particularly prominent performance optimisations could go
+here, but most should go in the L</Performance Enhancements> section.
+
+[ List each enhancement as a =head2 entry ]
=head1 Security
-=head2 [CVE-2017-12837] Heap buffer overflow in regular expression compiler
+XXX Any security-related notices go here. In particular, any security
+vulnerabilities closed should be noted here rather than in the
+L</Selected Bug Fixes> section.
-Compiling certain regular expression patterns with the case-insensitive
-modifier could cause a heap buffer overflow and crash perl. This has now been
-fixed.
-L<[perl #131582]|https://rt.perl.org/Public/Bug/Display.html?id=131582>
+[ List each security issue as a =head2 entry ]
-=head2 [CVE-2017-12883] Buffer over-read in regular expression parser
+=head1 Incompatible Changes
-For certain types of syntax error in a regular expression pattern, the error
-message could either contain the contents of a random, possibly large, chunk of
-memory, or could crash perl. This has now been fixed.
-L<[perl #131598]|https://rt.perl.org/Public/Bug/Display.html?id=131598>
+XXX For a release on a stable branch, this section aspires to be:
-=head2 [CVE-2017-12814] C<$ENV{$key}> stack buffer overflow on Windows
+ There are no changes intentionally incompatible with 5.XXX.XXX
+ If any exist, they are bugs, and we request that you submit a
+ report. See L</Reporting Bugs> below.
-A possible stack buffer overflow in the C<%ENV> code on Windows has been fixed
-by removing the buffer completely since it was superfluous anyway.
-L<[perl #131665]|https://rt.perl.org/Public/Bug/Display.html?id=131665>
+[ List each incompatible change as a =head2 entry ]
-=head1 Performance Enhancements
+=head1 Deprecations
-=over 4
+XXX Any deprecated features, syntax, modules etc. should be listed here.
-=item *
+=head2 Module removals
-The start up overhead for creating regular expression patterns with
-Unicode properties (C<\p{...}>) has been greatly reduced in most cases.
+XXX Remove this section if not applicable.
-=back
+The following modules will be removed from the core distribution in a
+future release, and will at that time need to be installed from CPAN.
+Distributions on CPAN which require these modules will need to list them as
+prerequisites.
-=head1 Modules and Pragmata
+The core versions of these modules will now issue C<"deprecated">-category
+warnings to alert you to this fact. To silence these deprecation warnings,
+install the modules in question from CPAN.
-=head2 Updated Modules and Pragmata
+Note that these are (with rare exceptions) fine modules that you are encouraged
+to continue to use. Their disinclusion from core primarily hinges on their
+necessity to bootstrapping a fully functional, CPAN-capable Perl installation,
+not usually on concerns over their design.
-=over 4
+=over
-=item *
+=item XXX
-L<bytes> has been upgraded from version 1.05 to 1.06.
+XXX Note that deprecated modules should be listed here even if they are listed
+as an updated module in the L</Modules and Pragmata> section.
-=item *
+=back
-L<Carp> has been upgraded from version 1.49 to 1.50.
+[ List each other deprecation as a =head2 entry ]
-=item *
+=head1 Performance Enhancements
-L<Devel::PPPort> has been upgraded from version 3.39 to 3.40.
+XXX Changes which enhance performance without changing behaviour go here.
+There may well be none in a stable release.
-=item *
+[ List each enhancement as an =item entry ]
-L<Exporter> has been upgraded from version 5.72 to 5.73.
+=over 4
=item *
-L<ExtUtils::Constant> has been upgraded from version 0.24 to 0.25.
+XXX
-=item *
+=back
-L<I18N::Langinfo> has been upgraded from version 0.16 to 0.17.
+=head1 Modules and Pragmata
-=item *
+XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
+go here. If Module::CoreList is updated, generate an initial draft of the
+following sections using F<Porting/corelist-perldelta.pl>. A paragraph summary
+for important changes should then be added by hand. In an ideal world,
+dual-life modules would have a F<Changes> file that could be cribbed.
-L<IO> has been upgraded from version 1.38 to 1.39.
+The list of new and updated modules is modified automatically as part of
+preparing a Perl release, so the only reason to manually add entries here is if
+you're summarising the important changes in the module update. (Also, if the
+manually-added details don't match the automatically-generated ones, the
+release manager will have to investigate the situation carefully.)
-=item *
+[ Within each section, list entries as an =item entry ]
-L<Module::CoreList> has been upgraded from version 5.20180221 to 5.20180420.
+=head2 New Modules and Pragmata
+
+=over 4
=item *
-L<POSIX> has been upgraded from version 1.83 to 1.84.
+XXX Remove this section if not applicable.
-=item *
+=back
+
+=head2 Updated Modules and Pragmata
-L<subs> has been upgraded from version 1.02 to 1.03.
+=over 4
=item *
-L<Time::HiRes> has been upgraded from version 1.9757 to 1.9759.
+L<XXX> has been upgraded from version A.xx to B.yy.
-=item *
+If there was something important to note about this change, include that here.
+
+=back
+
+=head2 Removed Modules and Pragmata
-L<vars> has been upgraded from version 1.03 to 1.04.
+=over 4
=item *
-L<version> has been upgraded from version 0.9918 to 0.9923.
+XXX
=back
=back
-=head1 Acknowledgements
+=head1 Utility Changes
+
+XXX Changes to installed programs such as F<perlbug> 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
+entries for each change
+Use L<XXX> with program names to get proper documentation linking. ]
+
+=head2 L<XXX>
+
+=over 4
+
+=item *
+
+XXX
+
+=back
+
+=head1 Configuration and Compilation
+
+XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
+go here. Any other changes to the Perl build process should be listed here.
+However, any platform-specific changes should be listed in the
+L</Platform Support> section, instead.
+
+[ List changes as an =item entry ].
+
+=over 4
+
+=item *
+
+XXX
+
+=back
+
+=head1 Testing
+
+XXX Any significant changes to the testing of a freshly built perl should be
+listed here. Changes which create B<new> files in F<t/> go here as do any
+large changes to the testing harness (e.g. when parallel testing was added).
+Changes to existing files in F<t/> aren't worth summarizing, although the bugs
+that they represent may be covered elsewhere.
+
+XXX If there were no significant test changes, say this:
+
+Tests were added and changed to reflect the other additions and changes
+in this release.
+
+XXX If instead there were significant changes, say this:
+
+Tests were added and changed to reflect the other additions and
+changes in this release. Furthermore, these significant changes were
+made:
+
+[ List each test improvement as an =item entry ]
+
+=over 4
+
+=item *
+
+XXX
+
+=back
+
+=head1 Platform Support
+
+XXX Any changes to platform support should be listed in the sections below.
+
+[ Within the sections, list each platform as an =item entry with specific
+changes as paragraphs below it. ]
+
+=head2 New Platforms
+
+XXX List any platforms that this version of perl compiles on, that previous
+versions did not. These will either be enabled by new files in the F<hints/>
+directories, or new subdirectories and F<README> files at the top level of the
+source tree.
+
+=over 4
+
+=item XXX-some-platform
+
+XXX
+
+=back
+
+=head2 Discontinued Platforms
+
+XXX List any platforms that this version of perl no longer compiles on.
+
+=over 4
+
+=item XXX-some-platform
+
+XXX
+
+=back
+
+=head2 Platform-Specific Notes
+
+XXX List any changes for specific platforms. This could include configuration
+and compilation changes or changes in portability/compatibility. However,
+changes within modules for platforms should generally be listed in the
+L</Modules and Pragmata> section.
+
+=over 4
+
+=item XXX-some-platform
+
+XXX
+
+=back
+
+=head1 Internal Changes
+
+XXX Changes which affect the interface available to C<XS> code go here. Other
+significant internal changes for future core maintainers should be noted as
+well.
+
+[ List each change as an =item entry ]
-Perl 5.27.11 represents approximately 4 weeks of development since Perl
-5.27.10 and contains approximately 440,000 lines of changes across 200 files
-from 21 authors.
+=over 4
+
+=item *
+
+XXX
+
+=back
+
+=head1 Selected Bug Fixes
+
+XXX Important bug fixes in the core language are summarized here. Bug fixes in
+files in F<ext/> and F<lib/> are best summarized in L</Modules and Pragmata>.
+
+[ List each fix as an =item entry ]
+
+=over 4
+
+=item *
+
+XXX
+
+=back
+
+=head1 Known Problems
-Excluding auto-generated files, documentation and release tools, there were
-approximately 440,000 lines of changes to 88 .pm, .t, .c and .h files.
+XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
+tests that had to be C<TODO>ed for the release would be noted here. Unfixed
+platform specific bugs also go here.
-Perl continues to flourish into its third decade thanks to a vibrant
-community of users and developers. The following people are known to have
-contributed the improvements that became Perl 5.27.11:
+[ List each fix as an =item entry ]
-Aaron Crane, Alexandr Savca, Chris 'BinGOs' Williams, Dagfinn Ilmari
-Mannsåker, Daniel Dragan, David Mitchell, H.Merijn Brand, James E Keenan,
-John Peacock, Karl Williamson, Marc-Philip Werner, Nicholas Clark, Pali,
-Ricardo Signes, Sawyer X, Sergey Aleynikov, Steve Hay, Todd Rinaldo, Tony
-Cook, Yves Orton, Zefram.
+=over 4
+
+=item *
+
+XXX
+
+=back
+
+=head1 Errata From Previous Releases
+
+=over 4
-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.
+=item *
+
+XXX Add anything here that we forgot to add, or were mistaken about, in
+the perldelta of a previous release.
+
+=back
+
+=head1 Obituary
+
+XXX If any significant core contributor or member of the CPAN community has
+died, add a short obituary here.
+
+=head1 Acknowledgements
-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.
+XXX Generate this with:
-For a more complete list of all of Perl's historical contributors, please
-see the F<AUTHORS> file in the Perl source distribution.
+ perl Porting/acknowledgements.pl v5.27.11..HEAD
=head1 Reporting Bugs