5 [ this is a template for a new perldelta file. Any text flagged as
6 XXX needs to be processed before release. ]
8 perldelta - what is new for perl v5.XXX.XXX
12 This document describes differences between the 5.XXX.XXX release and
13 the 5.XXX.XXX release.
15 If you are upgrading from an earlier release such as 5.YYY.YYY, first read
16 L<perl5YYYdelta>, which describes differences between 5.ZZZ.ZZZ and
21 XXX Any important notices here
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.
29 [ List each enhancement as a =head2 entry ]
33 XXX Any security-related notices go here. In particular, any security
34 vulnerabilities closed should be noted here rather than in the
35 L</Selected Bug Fixes> section.
37 [ List each security issue as a =head2 entry ]
39 =head1 Incompatible Changes
41 XXX For a release on a stable branch, this section aspires to be:
43 There are no changes intentionally incompatible with 5.XXX.XXX. If any
44 exist, they are bugs and reports are welcome.
46 [ List each incompatible change as a =head2 entry ]
50 XXX Any deprecated features, syntax, modules etc. should be listed here.
51 In particular, deprecated modules should be listed here even if they are
52 listed as an updated module in the L</Modules and Pragmata> section.
54 [ List each deprecation as a =head2 entry ]
56 =head1 Performance Enhancements
58 XXX Changes which enhance performance without changing behaviour go here. There
59 may well be none in a stable release.
61 [ List each enhancement as a =item entry ]
71 =head1 Modules and Pragmata
73 XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
74 go here. If Module::CoreList is updated, generate an initial draft of the
75 following sections using F<Porting/corelist-perldelta.pl>, which prints stub
76 entries to STDOUT. Results can be pasted in place of the '=head2' entries
77 below. A paragraph summary for important changes should then be added by hand.
78 In an ideal world, dual-life modules would have a F<Changes> file that could be
81 [ Within each section, list entries as a =item entry ]
83 =head2 New Modules and Pragmata
93 =head2 Updated Modules and Pragmata
103 =head2 Removed Modules and Pragmata
115 XXX Changes to files in F<pod/> go here. Consider grouping entries by
116 file and be sure to link to the appropriate page, e.g. L<perlfunc>.
118 =head2 New Documentation
120 XXX Changes which create B<new> files in F<pod/> go here.
124 XXX Description of the purpose of the new file here
126 =head2 Changes to Existing Documentation
128 XXX Changes which significantly change existing files in F<pod/> go here.
129 However, any changes to F<pod/perldiag.pod> should go in the L</Diagnostics>
138 XXX Description of the change here
144 The following additions or changes have been made to diagnostic output,
145 including warnings and fatal error messages. For the complete list of
146 diagnostic messages, see L<perldiag>.
148 XXX New or changed warnings emitted by the core's C<C> code go here. Also
149 include any changes in L<perldiag> that reconcile it to the C<C> code.
151 [ Within each section, list entries as a =item entry ]
153 =head2 New Diagnostics
155 XXX Newly added diagnostic messages go here
165 =head2 Changes to Existing Diagnostics
167 XXX Changes (i.e. rewording) of diagnostic messages go here
177 =head1 Utility Changes
179 XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go
180 here. Most of these are built within the directories F<utils> and F<x2p>.
182 [ List utility changes as a =head3 entry for each utility and =item
183 entries for each change
184 Use L<XXX> with program names to get proper documentation linking. ]
196 =head1 Configuration and Compilation
198 XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
199 go here. Any other changes to the Perl build process should be listed here.
200 However, any platform-specific changes should be listed in the
201 L</Platform Support> section, instead.
203 [ List changes as a =item entry ].
215 XXX Any significant changes to the testing of a freshly built perl should be
216 listed here. Changes which create B<new> files in F<t/> go here as do any
217 large changes to the testing harness (e.g. when parallel testing was added).
218 Changes to existing files in F<t/> aren't worth summarising, although the bugs
219 that they represent may be covered elsewhere.
221 [ List each test improvement as a =item entry ]
231 =head1 Platform Support
233 XXX Any changes to platform support should be listed in the sections below.
235 [ Within the sections, list each platform as a =item entry with specific
236 changes as paragraphs below it. ]
240 XXX List any platforms that this version of perl compiles on, that previous
241 versions did not. These will either be enabled by new files in the F<hints/>
242 directories, or new subdirectories and F<README> files at the top level of the
247 =item XXX-some-platform
253 =head2 Discontinued Platforms
255 XXX List any platforms that this version of perl no longer compiles on.
259 =item XXX-some-platform
265 =head2 Platform-Specific Notes
267 XXX List any changes for specific platforms. This could include configuration
268 and compilation changes or changes in portability/compatibility. However,
269 changes within modules for platforms should generally be listed in the
270 L</Modules and Pragmata> section.
274 =item XXX-some-platform
280 =head1 Internal Changes
282 XXX Changes which affect the interface available to C<XS> code go here.
283 Other significant internal changes for future core maintainers should
286 [ List each test improvement as a =item entry ]
296 =head1 Selected Bug Fixes
298 XXX Important bug fixes in the core language are summarised here.
299 Bug fixes in files in F<ext/> and F<lib/> are best summarised in
300 L</Modules and Pragmata>.
302 [ List each fix as a =item entry ]
312 =head1 Known Problems
314 XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
315 tests that had to be C<TODO>ed for the release would be noted here, unless
316 they were specific to a particular platform (see below).
318 This is a list of some significant unfixed bugs, which are regressions
319 from either 5.XXX.XXX or 5.XXX.XXX.
321 [ List each fix as a =item entry ]
333 XXX If any significant core contributor has died, we've added a short obituary
336 =head1 Acknowledgements
338 XXX The list of people to thank goes here.
340 =head1 Reporting Bugs
342 If you find what you think is a bug, you might check the articles
343 recently posted to the comp.lang.perl.misc newsgroup and the perl
344 bug database at http://rt.perl.org/perlbug/ . There may also be
345 information at http://www.perl.org/ , the Perl Home Page.
347 If you believe you have an unreported bug, please run the L<perlbug>
348 program included with your release. Be sure to trim your bug down
349 to a tiny but sufficient test case. Your bug report, along with the
350 output of C<perl -V>, will be sent off to perlbug@perl.org to be
351 analysed by the Perl porting team.
353 If the bug you are reporting has security implications, which make it
354 inappropriate to send to a publicly archived mailing list, then please send
355 it to perl5-security-report@perl.org. This points to a closed subscription
356 unarchived mailing list, which includes all the core committers, who be able
357 to help assess the impact of issues, figure out a resolution, and help
358 co-ordinate the release of patches to mitigate or fix the problem across all
359 platforms on which Perl is supported. Please only use this address for
360 security issues in the Perl core, not for modules independently
365 The F<Changes> file for an explanation of how to view exhaustive details
368 The F<INSTALL> file for how to build Perl.
370 The F<README> file for general stuff.
372 The F<Artistic> and F<Copying> files for copyright information.