Re^2: PDL-2.4.3_01 released, testing sought

search.cpan.org marks every PDL release as "UNAUTHORIZED"

I *think* that's under control (but I'll make some enquiries ... thanks for drawing it to my attention). The fact that 2.4.3_01 is "UNAUTHORIZED" is not, of itself, a concern. I suspect that might happen because it's been uploaded to Chris Marshall's account. When 2.4.4 is released, it will (presumably) be uploaded to Christian Soeller's account - and hopefully won't be slammed with the "UNAUTHORIZED" tag that 2.4.3 got lumbered with. We probably won't know for sure until 2.4.4 gets uploaded.

Cheers,
Rob

Comment on Re^2: PDL-2.4.3_01 released, testing sought

Replies are listed 'Best First'.
Re^3: PDL-2.4.3_01 released, testing sought by Anonymous Monk on Oct 21, 2008 at 14:27 UTC
Actually, there is no current PDL developer with sufficient permissions for a clean upload to PAUSE. One of the goals for this 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. We 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, we will be documenting the process and suggestions for multi-author maintainance for some sort of FAQ ref for all perl module authors.	[reply]

Replies are listed 'Best First'.

Re^3: PDL-2.4.3_01 released, testing sought
by Anonymous Monk on Oct 21, 2008 at 14:27 UTC

Actually, there is no current PDL developer with sufficient permissions for a clean upload to PAUSE.

One of the goals for this 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.

We 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, we will be documenting the process and suggestions for multi-author maintainance for some sort of FAQ ref for all perl module authors.

[reply]