In perl.git, the branch blead has been updated
<http://perl5.git.perl.org/perl.git/commitdiff/d158d46d555800558af193b2d3cb557971493507?hp=16fc71a0101f5d5b0e141a61a53ac3d3bb965842>
- Log -----------------------------------------------------------------
commit d158d46d555800558af193b2d3cb557971493507
Author: Matthew Horsfall <wolfs...@gmail.com>
Date: Mon Aug 21 15:28:23 2017 -0400
Update INSTALL for 5.27.3
M INSTALL
commit abe32213b13f4048869047847ec9dfd810090ff0
Author: Matthew Horsfall <wolfs...@gmail.com>
Date: Mon Aug 21 15:26:27 2017 -0400
Prep perldetla for release
M pod/perldelta.pod
-----------------------------------------------------------------------
Summary of changes:
INSTALL | 4 +-
pod/perldelta.pod | 325 ++++++------------------------------------------------
2 files changed, 35 insertions(+), 294 deletions(-)
diff --git a/INSTALL b/INSTALL
index 63604f1432..1b9c000240 100644
--- a/INSTALL
+++ b/INSTALL
@@ -2562,9 +2562,9 @@ seriously consider using a separate directory, since
development
subversions may not have all the compatibility wrinkles ironed out
yet.
-=head2 Upgrading from 5.25.12 or earlier
+=head2 Upgrading from 5.27.2 or earlier
-B<Perl 5.27.3 may not be binary compatible with Perl 5.25.12 or
+B<Perl 5.27.3 may not be binary compatible with Perl 5.27.2 or
earlier Perl releases.> Perl modules having binary parts
(meaning that a C compiler is used) will have to be recompiled to be
used with 5.27.3. If you find you do need to rebuild an extension with
diff --git a/pod/perldelta.pod b/pod/perldelta.pod
index 58f37e79a7..129a57843c 100644
--- a/pod/perldelta.pod
+++ b/pod/perldelta.pod
@@ -2,9 +2,6 @@
=head1 NAME
-[ 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.3
=head1 DESCRIPTION
@@ -15,44 +12,10 @@ release.
If you are upgrading from an earlier release such as 5.27.1, first read
L<perl5272delta>, which describes differences between 5.27.1 and 5.27.2.
-=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
-
-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.
-
-[ List each security issue as a =head2 entry ]
-
-=head1 Incompatible Changes
-
-XXX For a release on a stable branch, this section aspires to be:
-
- 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.
-
-[ List each incompatible change as a =head2 entry ]
-
=head1 Deprecations
-XXX Any deprecated features, syntax, modules etc. should be listed here.
-
=head2 Module removals
-XXX Remove this section if inapplicable.
-
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
@@ -71,165 +34,57 @@ not usually on concerns over their design.
=item B::Debug
-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.
-
=back
-[ List each other deprecation as a =head2 entry ]
-
=head1 Performance Enhancements
-XXX Changes which enhance performance without changing behaviour go here.
-There may well be none in a stable release.
-
-[ List each enhancement as an =item entry ]
-
=over 4
=item *
-XXX
-
-=back
-
-=head1 Modules and Pragmata
-
-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.
-
-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.)
-
-[ Within each section, list entries as an =item entry ]
-
-=head2 New Modules and Pragmata
-
-=over 4
+C<SvTRUE()> is now more efficient.
=item *
-XXX
-
-=back
-
-=head2 Updated Modules and Pragmata
-
-=over 4
+C<keys()> in void and scalar contexts is now more efficient.
=item *
-L<XXX> has been upgraded from version A.xx to B.yy.
-
-=back
-
-=head2 Removed Modules and Pragmata
-
-=over 4
+Various integer-returning ops are now more efficient in scalar/boolean context.
=item *
-XXX
-
-=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<perl...@perl.org|mailto:perl...@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
+C<< if (index(...) != -1) { ... } >> is now more efficient.
=item *
-XXX Description of the change here
+C<for()> loops and similar constructs are now more efficient in most cases.
=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
+=head1 Modules and Pragmata
-=head3 New Warnings
+=head2 New Modules and Pragmata
=over 4
=item *
-XXX L<message|perldiag/"message">
+XXX
=back
-=head2 Changes to Existing Diagnostics
-
-XXX Changes (i.e. rewording) of diagnostic messages go here
+=head2 Updated Modules and Pragmata
=over 4
=item *
-XXX Describe change here
+L<XXX> has been upgraded from version A.xx to B.yy.
=back
-=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>
+=head2 Removed Modules and Pragmata
=over 4
@@ -241,13 +96,6 @@ XXX
=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 *
@@ -257,107 +105,8 @@ disallowing arithmetic on void and function pointers.
=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 ]
-
-=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 *
@@ -382,43 +131,35 @@ interpreter. This matches the behaviour of threaded
builds. [perl
=back
-=head1 Known Problems
-
-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.
-
-[ List each fix as an =item entry ]
-
-=over 4
-
-=item *
-
-XXX
-
-=back
-
-=head1 Errata From Previous Releases
-
-=over 4
-
-=item *
+=head1 Acknowledgements
-XXX Add anything here that we forgot to add, or were mistaken about, in
-the perldelta of a previous release.
+Perl 5.27.3 represents approximately 5 weeks of development since Perl 5.27.2
+and contains approximately 5,600 lines of changes across 150 files from 19
+authors.
-=back
+Excluding auto-generated files, documentation and release tools, there were
+approximately 4,000 lines of changes to 84 .pm, .t, .c and .h files.
-=head1 Obituary
+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.3:
-XXX If any significant core contributor has died, we've added a short obituary
-here.
+Aaron Crane, Aristotle Pagaltzis, Chris 'BinGOs' Williams, Craig A. Berry,
+Dagfinn Ilmari Mannsåker, Daniel Dragan, David Mitchell, Father Chrysostomos,
+James E Keenan, Karl Williamson, Ken Brown, Lukas Mai, Matthew Horsfall,
+Nicholas Clark, Robin Barker, Steffen Müller, Steve Hay, Tony Cook, Zefram.
-=head1 Acknowledgements
+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.
-XXX Generate this with:
+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.
- perl Porting/acknowledgements.pl v5.25.5..HEAD
+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
--
Perl5 Master Repository
