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]>
signature.asc
Description: This is a digitally signed message part
