summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorZefram <zefram@fysh.org>2010-12-19 23:41:10 +0000
committerZefram <zefram@fysh.org>2010-12-19 23:41:10 +0000
commitb28f69c227e6e7efae176dc0ac44d3622eef31e4 (patch)
tree20485c2ffc333142643066f6ca65dfa989d11bb3
parentb6aa14cd2bcbea5793902cd478a4258670ce6000 (diff)
downloadperl-b28f69c227e6e7efae176dc0ac44d3622eef31e4.tar.gz
tweak later segments of release procedure
Slightly more clue about the indexer failures. Move some post-release steps into a new "the day after" section.
-rw-r--r--Porting/release_managers_guide.pod58
1 files changed, 35 insertions, 23 deletions
diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod
index 74a82f0197..4eefa63cdf 100644
--- a/Porting/release_managers_guide.pod
+++ b/Porting/release_managers_guide.pod
@@ -846,12 +846,12 @@ 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 received. IMPORTANT -- you will
-probably get an email that indexing has failed (due to dual-life modules,
-apparently). This is considered normal.
+probably get an email that indexing has failed, due to module permissions.
+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
+(e.g., cpan.hexten.net
or cpan.cpantesters.org) to confirm that your uploads have been successful.
=item *
@@ -886,26 +886,6 @@ Add your quote to F<Porting/epigraphs.pod> and commit it.
=item *
-Wait 24 hours or so, then post the announcement to use.perl.org.
-(if you don't have access rights to post news, ask someone like Rafael to
-do it for you.)
-
-=item *
-
-Check http://www.cpan.org/src/ to see if the new tarballs have appeared.
-They should appear automatically, but if they don't then ask Jarkko to look
-into it, since his scripts must have broken.
-
-=item *
-
-I<You MUST SKIP this step for RC, BLEAD>
-
-Ask Jarkko to update the descriptions of which tarballs are current in
-http://www.cpan.org/src/README.html, and Rafael to update
-http://dev.perl.org/perl5/
-
-=item *
-
I<You MUST SKIP this step for RC>
Remind the current maintainer of C<Module::CoreList> to push a new release
@@ -1047,6 +1027,38 @@ Thanks for releasing perl!
=back
+=head2 Building a release - the day after
+
+=over 4
+
+=item *
+
+Check L<http://www.cpan.org/src/> to see if the new tarballs have appeared.
+They should appear automatically, some hours after upload,
+but if they don't then ask Jarkko to look
+into it, since his scripts must have broken.
+
+=item *
+
+Check L<http://search.cpan.org> to see if it has indexed the distribution.
+It should be visible at a URL like C<http://search.cpan.org/dist/perl-5.10.1/>.
+
+=item *
+
+I<This step ONLY for STABLE>
+
+Ask Jarkko to update the descriptions of which tarballs are current in
+L<http://www.cpan.org/src/README.html>, and Rafael to update
+L<http://dev.perl.org/perl5/>
+
+=item *
+
+Post the release announcement to use.perl.org.
+(if you don't have access rights to post news, ask someone like Rafael to
+do it for you.)
+
+=back
+
=head1 SOURCE
Based on