From 5ed69d2bd4d29a68f74c5c3b55026de6ba32d135 Mon Sep 17 00:00:00 2001 From: Lukas Mai Date: Wed, 9 Apr 2025 05:35:34 +0200 Subject: [PATCH] RMG: be more explicit about Perl Releasers team requirement ... and mention why you need it even if you already have a commit bit. --- Porting/release_managers_guide.pod | 19 +++++++++++-------- 1 file changed, 11 insertions(+), 8 deletions(-) diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod index 6ada3d08fe77..508e24065380 100644 --- a/Porting/release_managers_guide.pod +++ b/Porting/release_managers_guide.pod @@ -177,14 +177,17 @@ Andreas' email address at: =head3 GitHub access -You will need a working C installation, checkout of the perl -git repository and perl commit bit. For information about working -with perl and git, see L. - -If you are not yet a perl committer, you won't be able to make a -release. You will need to have a GitHub account (if you don't have one) -and contact the Steering Council with your username to get membership in the -L<< Perl-Releasers|https://github.com/orgs/Perl/teams/perl-releasers >> team. +You will need a working C installation and a checkout of the perl +git repository. For information about working with perl and git, see +L. + +You will also need a L, a perl commit bit +and be a member of the L team. If you are +not yet a perl committer, you won't be able to commit changes to the main +repository; if you are not in Perl Releasers, you won't be able to push new +version tags. Contact the Steering Council with your GitHub username to be +added to the Perl Releasers team. =head3 Web-based file share