Clearify this is for even numbered (BLEAD-FINAL) releases.

[perl5.git] / Porting / release_managers_guide.pod

diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod
index 8db2488..a5f39f5 100644 (file)
--- a/Porting/release_managers_guide.pod
+++ b/Porting/release_managers_guide.pod
@@ -142,6 +142,13 @@ Make sure that search.cpan.org knows that you're allowed to upload
 perl distros. Contact Graham Barr to make sure that you're on the right
 list.
 
 perl distros. Contact Graham Barr to make sure that you're on the right
 list.
 

+=head3 rt.perl.org update access
+
+Make sure you have permission to close tickets on L<http://rt.perl.org/>
+so you can respond to bug report as necessary during your stint.  If you
+don't, make an account (if you don't have one) and contact the pumpking
+with your username to get ticket-closing permission.
+

 =head3 git checkout and commit bit
 
 You will need a working C<git> installation, checkout of the perl
 =head3 git checkout and commit bit
 
 You will need a working C<git> installation, checkout of the perl


@@ -153,6 +160,12 @@ release.  Have a chat with whichever evil perl porter tried to talk
 you into the idea in the first place to figure out the best way to
 resolve the issue.
 
 you into the idea in the first place to figure out the best way to
 resolve the issue.
 

+=head3 git clone of https://github.com/perlorg/perlweb
+
+For updating the L<http://dev.perl.org> web pages, either a Github account or
+sweet-talking somebody with a Github account into obedience is needed. This
+is only needed on the day of the release or shortly afterwards.
+

 =for checklist skip RC
 
 =head3 Quotation for release announcement epigraph
 =for checklist skip RC
 
 =head3 Quotation for release announcement epigraph


@@ -164,12 +177,11 @@ to use as an epigraph to your release announcement.
 
 =head2 Building a release - advance actions
 
 
 =head2 Building a release - advance actions
 

-The work of building a release candidate for a numbered release of
+The work of building a release candidate for an even numbered release of

 perl generally starts several weeks before the first release candidate.
 Some of the following steps should be done regularly, but all I<must> be
 done in the run up to a release.
 
 perl generally starts several weeks before the first release candidate.
 Some of the following steps should be done regularly, but all I<must> be
 done in the run up to a release.
 

-

 =head3 dual-life CPAN module synchronisation
 
 Ensure that dual-life CPAN modules are synchronised with CPAN.  Basically,
 =head3 dual-life CPAN module synchronisation
 
 Ensure that dual-life CPAN modules are synchronised with CPAN.  Basically,


@@ -1111,10 +1123,10 @@ It should be visible at a URL like C<http://search.cpan.org/dist/perl-5.10.1/>.
 
 I<You MUST SKIP this step for a RC release>
 
 
 I<You MUST SKIP this step for a RC release>
 

-Ask Leo Lapworth to update the front page of L<http://dev.perl.org/perl5/> to
-link to this new release. If you're feeling ambitious, you can fork
-L<https://github.com/perlorg/perlweb> and edit the
-F<docs/dev/perl5/index.html> file, then make a pull request.
+In the C<perlorg> repository, edit F<docs/dev/perl5/index.html>
+to link to this new release. Then make a pull request to Leo Lapworth.
+If this fails for some reason and you cannot cajole anybody else into
+submitting that change, you can mail Leo as last resort.

 
 =for checklist end
 
 
 =for checklist end