More release manager updates from 5.13.3 release notes

1 files changed, 24 insertions, 7 deletions

diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod
index cf65c2166c..bdf37e47ae 100644
--- a/Porting/release_managers_guide.pod
+++ b/Porting/release_managers_guide.pod
@@ -401,7 +401,11 @@ of I<advance actions>, do that now.
 I<You MAY SKIP this step for SNAPSHOT>
 
 Finalize the perldelta.  In particular, fill in the Acknowledgements
-section.
+section.  You can generate a list of contributors with checkAUTHORS.pl.
+For example:
+
+  $ git log --pretty=fuller v5.13.2..HEAD | \
+    perl Porting/checkAUTHORS.pl --who -
 
 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
@@ -416,11 +420,16 @@ formatting, e.g.
 
     $ perl pod/pod2html pod/perl5101delta.pod > /tmp/perl5101delta.html
 
+Another good HTML preview option is http://search.cpan.org/pod2html
+
+If you make changes, be sure to commit them.
+
 =item *
 
 Make sure you have a gitwise-clean perl directory (no modified files,
 unpushed commits etc):
 
+    $ git clean -dxf
     $ git status
 
 =item *
@@ -445,6 +454,9 @@ re-make perl to check that it's okay, then commit the updated versions:
 
     $ git commit -a -m 'make regen; make regen_perly'
 
+(XXX regen might be a problem depending on the bison version available.
+We need to get a wizard to give better instructions on what to do or not do.)
+
 =item *
 
 I<You MUST SKIP this step for SNAPSHOT>
@@ -452,8 +464,8 @@ I<You MUST SKIP this step for SNAPSHOT>
 Update C<Module::Corelist> with module version data for the new release.
 
 Note that if this is a maint release, you should run the following actions
-from the maint directory, but commit the C<Corelist.pm> changes in
-I<blead> and subsequently cherry-pick it.
+from the maint branch, but commit the C<Corelist.pm> changes in
+I<blead> and subsequently cherry-pick it.  XXX need a better example
 
 F<corelist.pl> uses ftp.funet.fi to verify information about dual-lived
 modules on CPAN. It can use a full, local CPAN mirror or fall back
@@ -559,7 +571,7 @@ Be sure to commit your changes:
 
 =item *
 
-I<You MUST SKIP this step for SNAPSHOT>
+I<You MUST SKIP this step for SNAPSHOT or BLEAD release>
 
 Update F<patchlevel.h> to add a C<-RC1>-or-whatever string; or, if this is
 a final release, remove it. For example:
@@ -822,9 +834,14 @@ may need to contact a PAUSE administrator or even bump the version of perl.
 Upload both the .gz and .bz2 versions of the tarball.
 
 Wait until you receive notification emails from the PAUSE indexer
-confirming that your uploads have been successfully indexed.  Do not
-proceed any further until you are sure that the indexing of your uploads
-has been successful.
+confirming that your uploads have been received.  IMPORTANT -- you will
+probably get an email that indexing has failed (due to dual-life modules,
+apparently).  This is considered normal.
+
+Do not proceed any further until you are sure that your tarballs are on
+CPAN.  Check your authors directory on one of the "fast" CPAN mirrors
+(e.g.  cpan.shadowcatprojects.net, cpan.dagolden.com, cpan.hexten.net
+or cpan.cpantesters.org) to confirm that your uploads have been successful.
 
 =item *