view release on metacpan or  search on metacpan

CONTRIBUTING  view on Meta::CPAN

      * Write good commit messages.

      The commit message "subject" is on the first line and should be 50
      characters or less. If the commit needs more explanation, the commit
      message "body" then comes after an empty line and is wrapped to about
      72 characters.

 Development Workflow

    Before you start, you may want to read and make sure you understand the
    "Commit Guidelines", "Directory Structure", and "Branch Layout".

      1. Branch your topic from master:

          git checkout -b $TOPIC_BRANCH master

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

      See "Commit Guidelines".

      3. Make sure the tests still pass:

          dzil test

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

 Release Workflow

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

      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 Changes and summarize the changes after the {{$NEXT}}
      token. Just leave the file uncommitted; it will automatically be
      committed in the next step.

      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
      Changes), tagging, and uploading to the CPAN.