[cage] Some clarifications on the CPAN process.

git-svn-id: https://svn.parrot.org/parrot/trunk@38213 d31e2699-5ff4-0310-a27c-f18f2fbe73fe

ports/cpan/cpan_release.pod

@@ -10,17 +10,14 @@ release tarball to CPAN. This should only be done for releases in the
 
 =item 1
 
-To upload a Parrot release to CPAN, your PAUSE ID will need to be a
-member of the PARROTRE group. Adding new members is a manual process
-performed by the PAUSE maintainers, so allow some time for this to
-happen.
-
-=item 2
-
 In PAUSE, assign yourself co-maintainer permissions on all modules owned
-by PARROTRE. 
+by PARROTRE, or ask a member of PARROTRE to do it for you.
 
-=item 3
+(You don't have to be a member of PARROTRE to upload a Parrot release to
+CPAN, but you do have to have co-maintainer permissions on the modules.
+See F<ports/cpan/pause_guide.pod> for more details.)
+
+=item 2
 
 Upload the Parrot tarball to CPAN. 
 
@@ -29,7 +26,7 @@ content of META.yml. Don't panic, the tarball still uploaded okay.  You
 do need to fix META.yml for the next release. Under "no_index" list any
 modules that aren't properly part of the Parrot distribution. 
 
-=item 4
+=item 3
 
 Once you get a reply from the PAUSE indexer, log in to PAUSE to clean up
 module permissions. Under "View Permissions" search for your PAUSE ID.

ports/cpan/pause_guide.pod

@@ -4,24 +4,19 @@
 
 In the Parrot distribution, all modules should be owned by the PARROTRE
 user in PAUSE. This allows a group of maintainers to manage permissions
-and metadata on the Parrot modules. In the Parrot project, every active
-a release manager will also be made a member of the PARROTRE group.
-Current members are: ARANDAL, BDFOY, CHROMATIC, COKE, JESSE, JONATHAN,
-MDIEP, PARTICLE, PMIC. 
+and metadata on the Parrot modules. You don't have to be a release
+manager to be part of the PARROTRE group, you only need a PAUSE ID and
+experience in mainatining CPAN modules. Current members are: ARANDAL,
+BDFOY, CHROMATIC, COKE, JESSE, JONATHAN, MDIEP, PARTICLE, PMIC. (At the
+moment, the only way to edit the list of members in the group is to
+write to modules@perl.org and wait for a PAUSE admin to update the list,
+so it needs to happen well in advance of the release date.)
 
 Membership in the PARROTRE group isn't required for uploading Parrot
 distributions to PAUSE. What is required for making a release is that
 your individual PAUSE ID be granted co-maintainer permissions on all
 PARROTRE modules. Members of the PARROTRE group have access to grant
-this permission.
-
-Generally the project manager will add your name to PARROTRE group when
-you first sign up to take a Parrot release rotation, but it's worth
-checking with the project manager several weeks ahead of your first
-release to make sure.  (At the moment, the only way to edit the list of
-members in the group is to write to modules@perl.org and wait for a
-PAUSE admin to update the list, so it needs to happen well in advance of
-the release date.)
+this permission. 
 
 =head1 The PAUSE process