Update the release managers' guide: don't push the tag too soon!

Remind release managers not to push a new tag until the indexing of
the new uploads has been successful. A problem with indexing 5.11.5
meant that we nearly ended up with 5.11.6 instead, since the 5.11.5
tag had already been pushed.

diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod
index 66a3bff..566171e 100644 (file)
--- a/Porting/release_managers_guide.pod
+++ b/Porting/release_managers_guide.pod
@@ -808,12 +808,19 @@ high-reliability connection to the Internet, you should probably use the
 new release from wherever you put it for testers to find it.  This will
 eliminate anxious gnashing of teeth while you wait to see if your
 15 megabyte HTTP upload successfully completes across your slow, twitchy
-cable modem.  I<Remember>: if your upload is partially successful, you
-may need to contact a PAUSE administrator or even bump the version of
-perl.
+cable modem.  You can make use of your home directory on dromedary for
+this purpose: F<http://users.perl5.git.perl.org/~USERNAME> maps to
+F</home/USERNAME/public_html>, where F<USERNAME> is your login account
+on dromedary.  I<Remember>: if your upload is partially successful, you
+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.
+
 =item *
 
 Now that you've shipped the new perl release to PAUSE, it's