3 [ Any text flagged as XXX needs to be processed before release. ]
5 perldelta - what is new for perl v5.11.1
9 This document describes differences between the 5.11.0 release and
15 =head1 Incompatible Changes
17 XXX For a release on a stable branch, this section aspires to be:
19 There are no changes intentionally incompatible with 5.XXX.XXX. If any
20 exist, they are bugs and reports are welcome.
23 =head1 Core Enhancements
25 XXX New core language features go here. Summarise user-visible core language
26 enhancements. Particularly prominent performance optimisations could go
27 here, but most should go in the L</Performance Enhancements> section.
31 XXX List any platforms that this version of perl compiles on, that previous
32 versions did not. These will either be enabled by new files in the F<hints/>
33 directories, or new subdirectories and F<README> files at the top level of the
36 =head1 Modules and Pragmata
38 XXX All changes to installed files in F<ext/> and F<lib/> go here, in a list
39 ordered by distribution name. Minimally it should be the module version,
40 but it's more useful to the end user to give a paragraph's summary of the
41 module's changes. In an ideal world, dual-life modules would have a
42 F<Changes> file that could be cribbed.
44 =head2 New Modules and Pragmata
54 =head2 Pragmata Changes
64 =head2 Updated Modules
74 =head1 Utility Changes
76 XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go
77 here. Most of these are built within the directories F<utils> and F<x2p>.
87 =head1 New Documentation
89 XXX Changes which create B<new> files in F<pod/> go here.
99 =head1 Changes to Existing Documentation
101 XXX Changes which significantly change existing files in F<pod/> go here.
102 Any changes to F<pod/perldiag.pod> should go in L</New or Changed Diagnostics>.
105 =head1 Performance Enhancements
107 XXX Changes which enhance performance without changing behaviour go here. There
108 may well be none in a stable release.
118 =head1 Installation and Configuration Improvements
120 XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
123 =head2 Configuration improvements
127 =head2 Compilation improvements
131 =head2 Platform Specific Changes
135 =item XXX-some-platform
141 =head1 Selected Bug Fixes
143 XXX Important bug fixes in the core language are summarised here.
144 Bug fixes in files in F<ext/> and F<lib/> are best summarised in
145 L</Modules and Pragmata>.
155 =head1 New or Changed Diagnostics
157 XXX New or changed warnings emitted by the core's C<C> code go here.
167 =head1 Changed Internals
169 XXX Changes which affect the interface available to C<XS> code go here.
181 XXX Changes which create B<new> files in F<t/> go here. Changes to
182 existing files in F<t/> aren't worth summarising, although the bugs that
183 they represent may be.
193 =head1 Known Problems
195 XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
196 tests that had to be C<TODO>ed for the release would be noted here, unless
197 they were specific to a particular platform (see below).
199 This is a list of some significant unfixed bugs, which are regressions
200 from either 5.10.1 or 5.11.0.
212 XXX Add any new known deprecations here.
214 The following items are now deprecated.
224 =head1 Platform Specific Notes
226 XXX Any changes specific to a particular platform. VMS and Win32 are the usual
227 stars here. It's probably best to group changes under the same section layout
228 as the main perldelta
232 XXX If any significant core contributor has died, we've added a short obituary
235 =head1 Acknowledgements
237 XXX The list of people to thank goes here.
240 =head1 Reporting Bugs
242 If you find what you think is a bug, you might check the articles
243 recently posted to the comp.lang.perl.misc newsgroup and the perl
244 bug database at http://rt.perl.org/perlbug/ . There may also be
245 information at http://www.perl.org/ , the Perl Home Page.
247 If you believe you have an unreported bug, please run the B<perlbug>
248 program included with your release. Be sure to trim your bug down
249 to a tiny but sufficient test case. Your bug report, along with the
250 output of C<perl -V>, will be sent off to perlbug@perl.org to be
251 analysed by the Perl porting team.
253 If the bug you are reporting has security implications, which make it
254 inappropriate to send to a publicly archived mailing list, then please send
255 it to perl5-security-report@perl.org. This points to a closed subscription
256 unarchived mailing list, which includes all the core committers, who be able
257 to help assess the impact of issues, figure out a resolution, and help
258 co-ordinate the release of patches to mitigate or fix the problem across all
259 platforms on which Perl is supported. Please only use this address for
260 security issues in the Perl core, not for modules independently
265 The F<Changes> file for an explanation of how to view exhaustive details
268 The F<INSTALL> file for how to build Perl.
270 The F<README> file for general stuff.
272 The F<Artistic> and F<Copying> files for copyright information.