diff options
| author | Florian Ragwitz <rafl@debian.org> | 2011-10-19 20:35:07 -0700 |
|---|---|---|
| committer | Florian Ragwitz <rafl@debian.org> | 2011-10-20 12:18:33 -0700 |
| commit | 6147c607bb11dc47cca8645cb6ab87c657d939b1 (patch) | |
| tree | e2859ca75468782a3d5a4b75f75fbfc84af09f5c /Porting | |
| parent | f038122280d598c8914def6050b564435a4d3ddc (diff) | |
| download | perl-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.
Diffstat (limited to 'Porting')
| -rw-r--r-- | Porting/release_managers_guide.pod | 15 |
1 files changed, 0 insertions, 15 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> |