symkat/Daemon-Control — pull request #22 by karenetheridge (2012-06-14 22:55:14+00:00)
Title: Topic/dzil

conversion to Dist::Zilla, including comments in dist.ini explaining what each line of the config does.

During development, to test everything (including release tests), do: 'dzil test --all'. However, 'prove -lr t' still works fine, as does 'perl -Ilib t/foo.t', so you aren't dependent on Dist::Zilla during the development process.

You can see what would be released by doing 'dzil build' -- as you can see, there are *lots* of files generated automatically (Makefile.PL, META.yml, MANIFEST, README, INSTALL, etc).

To release, just do 'dzil release' - it takes care of everything, from determining what the next version should be (it looks at the last 'git tag' - so I created one for the last release - but you can override that with V= dzil release'), checking that you entered something in the Changes file, everything is committed, there are no commits waiting on the remote branch, checking you're not releasing from a side branch, all tests pass, editing the version into all .pm files and the changelog, uploading to cpan (you'll be prompted for your PAUSE password, and also your userid if you don't have a ~/.pause file), creating a new tag, pushing your changes to github, installing the distribution, and then cleaning up! it's *magic*! :D