view release on metacpan or  search on metacpan

lib/App/WordPressTools/Contributing.pod  view on Meta::CPAN

=item 1.

Branch your topic from master:

    git checkout -b $TOPIC_BRANCH master

=item 2.

Make your changes in a logical sequence of one or more commits.

See L</Commit Guidelines>.

=item 3.

Make sure the tests still pass:

    dzil test

=item 4.

Send your patches to the authors.

If you use GitHub, you can push your topic branch to your fork and then create a pull request back to our master branch
using the GitHub interface:

    git push origin $TOPIC_BRANCH

If you don't use GitHub, send your patch to the authors via email:

    git checkout $TOPIC_BRANCH
    git format-patch -M origin

    # Then send patches as attachments using your favorite email client or using git:
    git send-email *.patch

See L<Public Project over Email|https://git-scm.com/book/en/v2/Distributed-Git-Contributing-to-a-Project#Public-Project-over-Email>
from the L<Pro Git|https://git-scm.com/book/en/v2> book for instructions on configuring git for sending email.

=back

=head2 Release Workflow

We use L<Dist::Zilla> to manage releases. The release management scripts do pretty much all of the work.

=over

=item 1.

Write to the changelog.

First, take a look at the list of commits since the last release:

    git shortlog origin/release..master

Then edit F<Changes> and summarize the changes after the C<{{$NEXT}}> token. Just leave the file uncommitted; it will
automatically be committed in the next step.

=item 2.

Run the release script and follow the prompts:

    git checkout master
    dzil release

The release script will take care of making the release commit (with F<Changes>), tagging, and uploading to the CPAN.

=back

=cut