chromatic schrieb:
https://pause.perl.org/pause/authenqueryI
It's only a CPAN indexing issue. Whenever a release manager uploads a new
bundle, he or she needs to change permissions for all new indexed modules to
allow the PARROTRE group to upload new versions. Unless/until you're a
release
Bernhard Schmalhofer schrieb:
Does this mean that all release managers should be in the PARROTRE group?
If so, somebody should check that this is indeed the case.
Judging from https://pause.perl.org/pause/authenquery, I'm no member
in PARROTRE. **
Sorry, I misread
Hi,
for Parrot 0.6.4 following Perl 5 modules were not indexed:
Parrot::Configure::Options::Test::Prepare
Parrot::Pmc2c::PMC::PrintTree
Parrot::Test::Util::Runloop
Parrot::SearchOps
It looks like co-maintainership needs to be given the release managers.
Regards,
Bernhard
Bernhard Schmalhofer wrote:
Hi,
for Parrot 0.6.4 following Perl 5 modules were not indexed:
Parrot::Configure::Options::Test::Prepare
Parrot::Pmc2c::PMC::PrintTree
Barney: I know that I wrote the two modules above (or, at least,
refactored them into their current form). What, if anything,
On Tuesday 15 July 2008 17:23:20 James E Keenan wrote:
Bernhard Schmalhofer wrote:
for Parrot 0.6.4 following Perl 5 modules were not indexed:
Parrot::Configure::Options::Test::Prepare
Parrot::Pmc2c::PMC::PrintTree
Barney: I know that I wrote the two modules above (or, at least,
i seem to recall that we agreed instead to noindex the Parrot::
modules... Nobody is expected to use them outside parrot anyway.
On 7/15/08, chromatic [EMAIL PROTECTED] wrote:
On Tuesday 15 July 2008 17:23:20 James E Keenan wrote:
Bernhard Schmalhofer wrote:
for Parrot 0.6.4 following Perl
