-
-=head3 finalize perldelta
-
-Finalize the perldelta. In particular, fill in the Acknowledgements
-section, which can be generated with something like:
-
- $ perl Porting/acknowledgements.pl v5.15.0..HEAD
-
-Re-read the perldelta to try to find any embarrassing typos and thinkos;
-remove any C<TODO> or C<XXX> flags; update the "Known Problems" section
-with any serious issues for which fixes are not going to happen now; and
-run through pod and spell checkers, e.g.
-
- $ podchecker -warnings -warnings pod/perldelta.pod
- $ spell pod/perldelta.pod
-
-Also, you may want to generate and view an HTML version of it to check
-formatting, e.g.
-
- $ ./perl -Ilib ext/Pod-Html/bin/pod2html pod/perldelta.pod > /tmp/perldelta.html
-
-Another good HTML preview option is http://search.cpan.org/pod2html
-
-If you make changes, be sure to commit them.
-
-=for checklist skip BLEAD-POINT MAINT RC
-
-=head3 remove stale perldeltas
-
-For the first RC release that is ONLY for a BLEAD-FINAL, the perldeltas
-from the BLEAD-POINT releases since the previous BLEAD_FINAL should have
-now been consolidated into the current perldelta, and hence are now just
-useless clutter. They can be removed using:
-
- $ git rm <file1> <file2> ...
-
-For example, for RC0 of 5.16.0:
-
- $ cd pod
- $ git rm perldelta515*.pod
-
-=for checklist skip BLEAD BLEAD-POINT
-
-=head3 add recent perldeltas
-
-For the first RC for a MAINT release, copy in any recent perldeltas from
-blead that have been added since the last release on this branch. This
-should include any recent maint releases on branches older than your one,
-but not newer. For example if you're producing a 5.14.x release, copy any
-perldeltas from recent 5.10.x, 5.12.x etc maint releases, but not from
-5.16.x or higher. Remember to
-
- $ git add <file1> <file2> ...
-
-=head3 update and commit perldelta files
-
-If you have added or removed any perldelta files via the previous two
-steps, then edit F<pod/perl.pod> to add/remove them from its table of
-contents, then run F<Porting/pod_rules.pl> to propagate your changes there
-into all the other files that mention them (including F<MANIFEST>). You'll
-need to C<git add> the files that it changes.
-
-Then build a clean perl and do a full test
-
- $ git status
- $ git clean -dxf
- $ ./Configure -Dusedevel -des
- $ make
- $ make test
-
-Once all tests pass, commit your changes.
-