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 reports are welcome.
+ There are no changes intentionally incompatible with 5.XXX.XXX
+ If any exist, they are bugs and reports are welcome.
[ List each incompatible change as a =head2 entry ]
=item *
-XXX
+L<XXX> has been upgraded from version 0.69 to version 0.70.
=back
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>.
-[ Within each section, list entries as a =item entry ]
-
=head2 New Documentation
XXX Changes which create B<new> files in F<pod/> go here.
-=over 4
-
-=item L<XXX>
-
-XXX
+=head3 L<XXX>
-=back
+XXX Description of the purpose of the new file here
=head2 Changes to Existing Documentation
However, any changes to F<pod/perldiag.pod> should go in the L</Diagnostics>
section.
+=head3 L<XXX>
+
=over 4
-=item L<XXX>
+=item *
-XXX
+XXX Description of the change here
=back
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.
-[ Within each section, list entries as a =item entry ]
+[ Within each section, list entries as a =item entry that links to perldiag,
+ e.g.
+
+ =item *
+
+ L<Invalid version object|perldiag/"Invalid version object">
+]
=head2 New Diagnostics
XXX Newly added diagnostic messages go here
+=head3 New Errors
+
=over 4
=item *
-XXX
+XXX L<message|perldiag/"message">
+
+=back
+
+=head3 New Warnings
+
+=over 4
+
+=item *
+
+XXX L<message|perldiag/"message">
=back
=item *
-XXX
+XXX Describe change here
=back
XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go
here. Most of these are built within the directories F<utils> and F<x2p>.
-[ List utility changes as a =item entry. Use L<XXX> with program names to get
-proper documentation linking. ]
+[ List utility changes as a =head3 entry for each utility and =item
+entries for each change
+Use L<XXX> with program names to get proper documentation linking. ]
+
+=head3 L<XXX>
=over 4
-=item L<XXX>
+=item *
XXX
Other significant internal changes for future core maintainers should
be noted as well.
-[ List each test improvement as a =item entry ]
+[ List each change as a =item entry ]
=over 4
=head1 Acknowledgements
-XXX The list of people to thank goes here.
+XXX Generate this with:
+
+ perl Porting/acknowledgements.pl v5.15.1..HEAD
=head1 Reporting Bugs
bug database at http://rt.perl.org/perlbug/ . There may also be
information at http://www.perl.org/ , the Perl Home Page.
-If you believe you have an unreported bug, please run the B<perlbug>
+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
If the bug you are reporting has security implications, which make it
inappropriate to send to a publicly archived mailing list, then please send
it to perl5-security-report@perl.org. This points to a closed subscription
-unarchived mailing list, which includes all the core committers, who be able
+unarchived mailing list, which includes
+all the core committers, who will be able
to help assess the impact of issues, figure out a resolution, and help
co-ordinate the release of patches to mitigate or fix the problem across all
platforms on which Perl is supported. Please only use this address for