Hi!

While deploying a lot of custom but CPAN-style code today I once again 
was bored by the mostly repetitive stuff I had to do (you know, update 
Changes, bump the version, run the tests, blabla).

I was tempted to enhance the script we're using (which mostly does the 
git-side of the process, i.e. tag the release and upload it to our 
custom cpan), but on the other hand I knew that there are some things on 
CPAN that should make this process easier. CPAN beeing CPAN, there are several 
things available, and I couldn't find a quick overview about what's 
$best

So, what would you choose to handle releasing of modules that use 
Module::Build and git and follow the general CPAN dist best practices?

ShipIt doesn't like Module::Build, even though there's a patch available 
(not applied for more than a year: 
http://rt.cpan.org/Public/Bug/Display.html?id=33081
)

Module::Release doesn't seem to handle git

Dist::Zilla is more about managing a dist, not releasing it (and I don't 
want to wait for "the glorious future of Dist::Zilla" :-)

Adam Kennedy seems to be working on similar things, but what exactly?

So. It seems there's nothing off the shelf that fits my needs. I 
wouldn't mind contributing to one of the above projects (or to another 
one..). But to which?

What do you use for taking the boring stuff out of module releases?


-- 
#!/usr/bin/perl                              http://domm.plix.at
for(ref bless{},just'another'perl'hacker){s-:+-$"-g&&print$_.$/}

Reply via email to