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
16 =head1 Incompatible Changes
18 XXX For a release on a stable branch, this section aspires to be:
20 There are no changes intentionally incompatible with 5.XXX.XXX. If any
21 exist, they are bugs and reports are welcome.
24 =head1 Core Enhancements
26 XXX New core language features go here. Summarise user-visible core language
27 enhancements. Particularly prominent performance optimisations could go
28 here, but most should go in the L</Performance Enhancements> section.
32 XXX List any platforms that this version of perl compiles on, that previous
33 versions did not. These will either be enabled by new files in the F<hints/>
34 directories, or new subdirectories and F<README> files at the top level of the
37 =head1 Modules and Pragmata
39 XXX All changes to installed files in F<ext/> and F<lib/> go here, in a list
40 ordered by distribution name. Minimally it should be the module version,
41 but it's more useful to the end user to give a paragraph's summary of the
42 module's changes. In an ideal world, dual-life modules would have a
43 F<Changes> file that could be cribbed.
45 =head2 New Modules and Pragmata
55 =head2 Pragmata Changes
65 =head2 Updated Modules
75 =head1 Utility Changes
77 XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go
78 here. Most of these are built within the directories F<utils> and F<x2p>.
88 =head1 New Documentation
90 XXX Changes which create B<new> files in F<pod/> go here.
100 =head1 Changes to Existing Documentation
102 XXX Changes which significantly change existing files in F<pod/> go here.
103 Any changes to F<pod/perldiag.pod> should go in L</New or Changed Diagnostics>.
106 =head1 Performance Enhancements
108 XXX Changes which enhance performance without changing behaviour go here. There
109 may well be none in a stable release.
119 =head1 Installation and Configuration Improvements
121 XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
124 =head2 Configuration improvements
128 =head2 Compilation improvements
132 =head2 Platform Specific Changes
136 =item XXX-some-platform
142 =head1 Selected Bug Fixes
144 XXX Important bug fixes in the core language are summarised here.
145 Bug fixes in files in F<ext/> and F<lib/> are best summarised in
146 L</Modules and Pragmata>.
156 =head1 New or Changed Diagnostics
158 XXX New or changed warnings emitted by the core's C<C> code go here.
168 =head1 Changed Internals
170 XXX Changes which affect the interface available to C<XS> code go here.
182 XXX Changes which create B<new> files in F<t/> go here. Changes to
183 existing files in F<t/> aren't worth summarising, although the bugs that
184 they represent may be.
194 =head1 Known Problems
196 XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
197 tests that had to be C<TODO>ed for the release would be noted here, unless
198 they were specific to a particular platform (see below).
200 This is a list of some significant unfixed bugs, which are regressions
201 from either 5.10.1 or 5.11.0.
213 XXX Add any new known deprecations here.
215 The following items are now deprecated.
225 =head1 Platform Specific Notes
227 XXX Any changes specific to a particular platform. VMS and Win32 are the usual
228 stars here. It's probably best to group changes under the same section layout
229 as the main perldelta
234 XXX If any significant core contributor has died, we've added a short obituary
237 =head1 Acknowledgements
239 XXX The list of people to thank goes here.
242 =head1 Reporting Bugs
244 If you find what you think is a bug, you might check the articles
245 recently posted to the comp.lang.perl.misc newsgroup and the perl
246 bug database at http://rt.perl.org/perlbug/ . There may also be
247 information at http://www.perl.org/ , the Perl Home Page.
249 If you believe you have an unreported bug, please run the B<perlbug>
250 program included with your release. Be sure to trim your bug down
251 to a tiny but sufficient test case. Your bug report, along with the
252 output of C<perl -V>, will be sent off to perlbug@perl.org to be
253 analysed by the Perl porting team.
255 If the bug you are reporting has security implications, which make it
256 inappropriate to send to a publicly archived mailing list, then please send
257 it to perl5-security-report@perl.org. This points to a closed subscription
258 unarchived mailing list, which includes all the core committers, who be able
259 to help assess the impact of issues, figure out a resolution, and help
260 co-ordinate the release of patches to mitigate or fix the problem across all
261 platforms on which Perl is supported. Please only use this address for
262 security issues in the Perl core, not for modules independently
267 The F<Changes> file for an explanation of how to view exhaustive details
270 The F<INSTALL> file for how to build Perl.
272 The F<README> file for general stuff.
274 The F<Artistic> and F<Copying> files for copyright information.