Sean Quinlan writes: > 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.
In general I recon Cpan uploads should be less often than CVS commits -- for example if adding a feature you might first of all commit the docs for it, then the tests, then the core of the feature, then the interface for using the feature, then changes to the docs based on how it actually works rather than how you planned it. Each of those make sense as separate CVS commits (they are a step forwards and they don't break any existing functionality), but it doesn't make sense to release to Cpan till after the last one. However if you're adding a few features there's no reason not to make a Cpan upload after each one: each version is an improvement on the previous one, and there isn't any advantage in making people who want the first one waiting till you've got the rest written. Smylers
