CPAN::Groonga

Make your build: This will get some boilerplate for git
  > milla build
  > git add Build.PL META.json README.md && git commit -m "git stuff"

  # Done? Test and release it!
  > $EDITOR Changes
  > mi

nge your modules from there.

I don't care about the real boilerplate such as C<MANIFEST>,
C<META.json> or C<LICENSE> auto-generated, but don't personally like
the idea of generating documentation or 

 difficult

This is true for most Dist::Zilla based distributions.

Milla copies the plain C<META.json> and C<Build.PL> into the git
repository you automatically bump on every release. And there won't

 - Initial release
___[ .gitignore ]___
/{{$dist->name}}-*
/.build
/_build*
/Build
MYMETA.*
!META.json
/.prove
___[ cpanfile ]___
requires 'perl', '5.012';

# requires 'Some::Module', 'VERSION';

on t

                    $self->installer);
    }

    my @dirty_files = ('dist.ini', 'Changes', 'META.json', 'README.md', 'LICENSE', $self->build_file);
    my @exclude_release = ('README.md');

    $self

', { exclude_filename => [ $self->build_file, 'META.json', 'LICENSE', @exclude_release ] } ],
        [ 'CopyFilesFromBuild', { copy => [ 'META.json', 'LICENSE', $self->build_file ] } ],

        # sh

share eg examples ) ] } ],

        # cpanfile -> META.json
        [ 'Prereqs::FromCPANfile' ],
        [ $self->installer ],
        [ 'MetaJSON' ],

        # experimental dist metadata
        [ '

from git
using C<cpanm> or testable with C<Travis CI>.

  > milla build
  > git add Build.PL META.json README.md && git commit -m "git stuff"

=head2 Making the first release

When you get confident a

mpted to confirm that version in case you need a major
bump.

This will update C<Changes>, C<META.json> and bump C<$VERSION> in your
main module. These changes made by Milla will be automatically
comm

at line.

Next, Edit C<.gitignore> and add the following lines:

  /Dist-Name-*
  /.build
  !META.json

You're almost done, and your directory will look like:

  cpanfile
  dist.ini
  lib/Dist/Name.pm