Re: CPAN question

[Chris Dolan]

I'm interested to hear what others say. IMO, uploading to CPAN more than once a week on a regular basis is too much. With mirror propagation time and caching of the module list in CPAN.pm itself, you should expect at least a day or more of delay before people will see your uploaded module.

For more frequent updates, I think VCSs (like CVS) or SourceForge are better alternatives, with point releases going to CPAN.

That said, I think regular uploads to CPAN won't really hurt anything. It just won't help too much.

Chris

On Nov 10, 2004, at 10:57 AM, Sean Quinlan wrote:

Just wondering about appropriate PAN usage. I have a set of modules I'm
working on on an almost daily basis. They are alpha's currently (the
port from the working MySQL::Backup to DBA::Backup &
DBA::Backup::mysql). I talked about them at our local Perl mongers
meeting last night and a few people expressed interest in the project,
as well as a few collaborators.

My impulse is to regularly update the modules on CPAN, at least until we
get a semi-functional beta in place. But I'm apprehensive that using
CPAN like CVS might annoy some of the maintainers. :) What's the general
consensus, keep the modules on CPAN current, or use email/lists/etc. and
only update CPAN at significant development points.

Thanks!

--
Sean Quinlan <[EMAIL PROTECTED]>

--
Chris Dolan, Software Developer, Clotho Advanced Media Inc.
608-294-7900, 1435 E Main St, Madison WI 53703

PGP.sig

Description: This is a digitally signed message part