On Wed, 2004-11-10 at 12:22, Chris Dolan wrote: > 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.
Ah, very good point! Thanks for reminding me. > For more frequent updates, I think VCSs (like CVS) or SourceForge are > better alternatives, with point releases going to CPAN. Agreed. But although I'm used to using CVS and Perforce for collaborative projects, I'm not sure if everyone who has expressed interest is. Not to mention I don't have a personal CVS server. And setting up a new sourceforge project would be more of a pain than this project probably requires. For the moment I think I'll just put new tarballs on my own website, and wait for more significant checkpoints to update 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 -- Sean Quinlan <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
