Fix Maintainers.pl and META.yml for removal of lib/version.t

[perl5.git] / Porting / release_managers_guide.pod

diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod
index a33acf4..54fd7b8 100644 (file)
--- 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>
@@ -855,6 +840,7 @@ Be sure to commit your change:
 
 Mail p5p to announce your new release, with a quote you prepared earlier.
 
+Use the template at Porting/release_announcement_template.txt
 
 =head3 update epigraphs.pod
 
@@ -877,71 +863,40 @@ I<You MUST SKIP this step for RC>
 
 Create a new perldelta.
 
-B<Note>: currently, the buildtoc below must be run in a I<built> perl source
-directory, as at least one of the pod files it expects to find is
-autogenerated: perluniprops.pod. But you can't build perl if you've added
-the new perldelta file and not updated toc. So, make sure you have a built
-perl (with a pod/perluniprops.pod file) now, I<before> continuing.
-
-First, update the F<pod/.gitignore> file  to ignore the next
-release's generated F<pod/perlNNNdelta.pod> file rather than this release's
-one which we are about to set in stone (where NNN is the perl version number
-without the dots. i.e. 5135 for 5.13.5).
-
-    $ (edit pod/.gitignore )
-    $ git add pod/.gitignore
+=over 4
 
-Then, move the existing F<pod/perldelta.pod> to F<pod/perlNNNdelta.pod>,
-and edit the moved delta file to change the C<NAME> from C<perldelta> to
-C<perlNNNdelta>.  For example, assuming you just released 5.10.1, and are
-about to create the 5.10.2 perldelta:
+=item *
 
-    $ rm  pod/perl5101delta.pod # remove the auto-generated file, if any
-    $ git mv pod/perldelta.pod pod/perl5101delta.pod
-    $ (edit pod/perl5101delta.pod to retitle)
-    $ git add pod/perl5101delta.pod
+Confirm that you have a clean checkout with no local changes.
 
-Then create a new empty perldelta.pod file for the new release; see
-F<Porting/how_to_write_a_perldelta.pod>. You should be able to do this by
-just copying in a skeleton template and then doing a quick fix up of the
-version numbers.  Then commit the move and the new file.
+=item *
 
-    $ cp -i Porting/perldelta_template.pod pod/perldelta.pod
-    $ (edit pod/perldelta.pod)
-    $ git add pod/perldelta.pod
-    $ git commit -m 'create perldelta for 5.10.2'
+Run F<Porting/new-perldelta.pl>
 
-=head3 update perldelta TOC and references
+=item *
 
-Now you need to update various tables of contents related to perldelta,
-most of which can be generated automatically.
+Run the C<git add> commands it outputs to add new and modified files.
 
-Edit F<pod.lst>: add the new entry for the perlNNNdelta file for the
-current version (the file that will be symlinked to perldelta).
+=item *
 
-Manually create a temporary link to the new delta file; normally this is
-done from the Makefile, but the Makefile is updated by buildtoc, and
-buildtoc won't run without the file there:
+Verify that the build still works, by running C<./Configure> and
+C<make test_porting>. (On Win32, run C<nmake> and
+C<nmake test TEST_FILES="porting\*.t ..\lib\diagnostics.t">.)
 
-    $ ln -s perldelta.pod pod/perl5102delta.pod
+=item *
 
-Run C<perl pod/buildtoc --build-all> to update the F<perldelta> version in
-the following files:
+If F<t/porting/podcheck.t> spots errors in the new F<pod/perldelta.pod>,
+run C<./perl -MTestInit t/porting/podcheck.t | less> for more detail.
+Skip to the end of its test output to see the options it offers you.
 
-    MANIFEST
-    Makefile.SH
-    pod/perl.pod
-    vms/descrip_mms.template
-    win32/Makefile
-    win32/makefile.mk
-    win32/pod.mak
+=item *
 
-Finally, commit:
+When C<make test_porting> passes, commit the new perldelta.
 
-    $ git commit -a -m 'update TOC for perlNNNdelta'
+=back
 
 At this point you may want to compare the commit with a previous bump to
-see if they look similar.  See commit dd885b5 for an example of a
+see if they look similar.  See commit e3c71926d3 for an example of a
 previous version bump.