Actually, there is no current PDL developer with sufficient permissions for a clean upload to PAUSE. One of the goals for the upload was to diagnose any remaining permissions needed for PDL maintenance and to coordinate them so that future releases can happen cleanly without a lot of work to sort out permissions.
I have been working to collect maintainer permissions for PDL maintainers that do not wish to participate actively in development. For the purposes of module permissions, that is basically that they keep up with the pdl-developer's list and are responsive to the need to adjust module permissions for release management. There are only a few remaining authors to work with on this issue and we plan to get their permissions fully coordinated by the formal PDL-2.4.4 release. Afterward, I will be documenting the process and suggestions for multi-author maintainance for some sort of FAQ ref for all perl module authors. --Chris Sisyphus wrote: > > ----- Original Message ----- From: "Chris Marshall" <[EMAIL PROTECTED]> > To: "pdl-porters" <[EMAIL PROTECTED]>; "perldl list" > <[email protected]> > Sent: Monday, October 20, 2008 1:16 PM > Subject: [Pdl-porters] PDL-2.4.4 pre-release as PDL-2.4.3_01 on CPAN > > >> As advertised, PDL-2.4.3_01, a developers pre-release of >> PDL-2.4.4, has just been posted to CPAN. > > I posted this news to perlmonks (in an attempt to get some additional > testing done). > > The thread is at: > http://www.perlmonks.org/index.pl?node_id=718190 > > Someone asked about the fact that 2.4.3_01 is marked as > "UNAUTHORIZED". Is that something to be concerned about ? I'm thinking > it might have happened simply because it was uploaded to Chris's > account rather than Christian's. > > Should we upload a 2.4.3_02 to Christian's account to make sure that > "UNAUTHORIZED" problem has, in fact, been addressed ? > > Cheers, > Rob > > _______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
