summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFlorian Ragwitz <rafl@debian.org>2011-10-19 20:35:07 -0700
committerFlorian Ragwitz <rafl@debian.org>2011-10-20 12:18:33 -0700
commit6147c607bb11dc47cca8645cb6ab87c657d939b1 (patch)
treee2859ca75468782a3d5a4b75f75fbfc84af09f5c
parentf038122280d598c8914def6050b564435a4d3ddc (diff)
downloadperl-6147c607bb11dc47cca8645cb6ab87c657d939b1.tar.gz
Remove the MANIFEST check from the release guide
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.
-rw-r--r--Porting/release_managers_guide.pod15
-rw-r--r--t/porting/known_pod_issues.dat2
2 files changed, 1 insertions, 16 deletions
diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod
index a33acf4b2f..fbb778ff3b 100644
--- a/Porting/release_managers_guide.pod
+++ b/Porting/release_managers_guide.pod
@@ -508,21 +508,6 @@ cherry-pick it back).
$ 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>
diff --git a/t/porting/known_pod_issues.dat b/t/porting/known_pod_issues.dat
index fc9d85f481..20454dd95c 100644
--- a/t/porting/known_pod_issues.dat
+++ b/t/porting/known_pod_issues.dat
@@ -286,7 +286,7 @@ porting/expand-macro.pl Verbatim line length including indents exceeds 79 by 2
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