Release Cycles

Frequency

Aim for a new release on the last Monday of each month.

Next Projected Release

January 25, 2016

Release Checklist

• move all pending issues/PRs to next release milestone
• think of a neat release name
• look through all commits and create a list of changes for the release post (example)
  • it could be done with script: https://gist.github.com/spacewander/13e18cf150b96c69ec69df0056286738
• update AUTHORS
• update History.md
  • run git changelog
  • change n.n.n to new release version
• bump $VERSION in bin/git-extras to new release version
• make the release post
  • tag version: new release version according to semver (ex: 0.0.0)
  • release title: Version 0.0.0 (release name)
  • description: list of changes; list all new commands and any breaking changes for any commands
• publish release
• bump $VERSION in bin/git-extras to next projected release version (ex: if new release version is 4.1.0, next projected release version could be 4.2.0-dev)
• update Homebrew
• notify all issues/PRs under new release milestone that issue/feature is now available via Homebrew