X-Git-Url: https://perl5.git.perl.org/perl5.git/blobdiff_plain/48100be180e1ed747313758d3ed70dd9c8879f3e..036935f1993182e7c6f159b90e0e79e791177741:/Porting/release_managers_guide.pod
diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod
index 8db2488..a5f39f5 100644
--- 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.
+=head3 rt.perl.org update access
+
+Make sure you have permission to close tickets on L
+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 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.
+=head3 git clone of https://github.com/perlorg/perlweb
+
+For updating the L 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
@@ -164,12 +177,11 @@ to use as an epigraph to your release announcement.
=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 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,
@@ -1111,10 +1123,10 @@ It should be visible at a URL like C.
I
-Ask Leo Lapworth to update the front page of L to
-link to this new release. If you're feeling ambitious, you can fork
-L and edit the
-F file, then make a pull request.
+In the C repository, edit F
+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