Module Build/Test/Release System

jbisbee has asked for the wisdom of the Perl Monks concerning the following question:

Replies are listed 'Best First'.
Re: Module Build/Test/Release System by dragonchild (Archbishop) on Jun 24, 2008 at 17:09 UTC
I use Module::Install for new stuff. I used to use Module::Build, but I've migrated because I like MI better. My criteria for good software: Does it work? Can someone else come in, make a change, and be reasonably certain no bugs were introduced?	[reply]
Re: Module Build/Test/Release System by perrin (Chancellor) on Jun 24, 2008 at 18:31 UTC
Automated changelogs aren't worth the bits they're stored in. If you aren't going to manually create a changelog that tells people something useful about what changed (see DBI for a great example), I don't think it's worth having a changelog at all.	[reply]
Re: Module Build/Test/Release System by moritz (Cardinal) on Jun 24, 2008 at 15:47 UTC
I use Module::Build for my modules (which are plain perl modules so far), and it works well. If you use it, be sure to use a relatively new version (I had some minor troubles with Version 0.26, all of which seem to be fixed in newer releases). `perl Build.PL ./Build test ./Build manifest ./Build dist` [download]	[reply] [d/l]
Re^2: Module Build/Test/Release System by jbisbee (Pilgrim) on Jun 24, 2008 at 16:01 UTC
I understand ExtUtils::MakeMaker/Module::Build part of building out a distribution. I guess I'm really looking for auto generation of change logs, potentially uping version #s, uploading to CPAN, etc rolled into a nice neat package. I know of people who have built out their own release systems and see what other 'hooks' there are to make life easier for a CPAN developer. -biz-	[reply]