diff options
author | Steve Hay <steve.m.hay@googlemail.com> | 2018-11-06 21:59:45 +0000 |
---|---|---|
committer | Steve Hay <steve.m.hay@googlemail.com> | 2018-11-06 21:59:45 +0000 |
commit | 4b1589a00b5c839e96aa8849d3a6e4bd179f5d81 (patch) | |
tree | 1447fabe43fe59b0f791544c5507a6e9db577244 | |
parent | e0eae03760cafde89463c4d3d238be9a629f7fca (diff) | |
download | perl-4b1589a00b5c839e96aa8849d3a6e4bd179f5d81.tar.gz |
perldelta - Update Modules and Pragmata section
-rw-r--r-- | pod/perldelta.pod | 38 |
1 files changed, 1 insertions, 37 deletions
diff --git a/pod/perldelta.pod b/pod/perldelta.pod index d5ebc3ab1d..f7e93875de 100644 --- a/pod/perldelta.pod +++ b/pod/perldelta.pod @@ -95,49 +95,13 @@ XXX =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 - -=item * - -XXX Remove this section if not applicable. - -=back - =head2 Updated Modules and Pragmata =over 4 =item * -L<XXX> has been upgraded from version A.xx to B.yy. - -If there was something important to note about this change, include that here. - -=back - -=head2 Removed Modules and Pragmata - -=over 4 - -=item * - -XXX +L<Module::CoreList> has been upgraded from version 5.20180622 to 5.20181122_28. =back |