We already have porting tests catching this. I really don't see how this could
end up being screwed or how it'd be more likely at this point during the release
process than at any other time.
$ git commit -m 'Update Module::CoreList for 5.x.y' dist/Module-CoreList/lib/Module/CoreList.pm
-=head3 check MANIFEST
-
-Check that the manifest is sorted and correct:
-
- $ make distclean
- $ git clean -xdf # This shouldn't be necessary if distclean is correct
- $ perl Porting/manicheck
-
-If manicheck turns up anything wrong, update MANIFEST and begin this step again.
-
- $ ./configure -des -Dusedevel
- $ make test_porting
- $ git commit -m 'Update MANIFEST' MANIFEST
-
-
=head3 update perlhist.pod
I<You MUST SKIP this step for a RC release>
porting/how_to_write_a_perldelta.pod There is no NAME 1
porting/how_to_write_a_perldelta.pod Verbatim line length including indents exceeds 79 by 3
porting/pumpkin.pod Verbatim line length including indents exceeds 79 by 9
-porting/release_managers_guide.pod Verbatim line length including indents exceeds 79 by 9
+porting/release_managers_guide.pod Verbatim line length including indents exceeds 79 by 8
porting/release_managers_guide.pod Verbatim paragraph in NAME section 1
porting/release_schedule.pod There is no NAME 1
symbian/perlutil.pod Verbatim line length including indents exceeds 79 by 4