Release Cycles

Frequency

Aim for a new release every half year.

Release Checklist

• open an issue to notify that we are kicking off a new release (example)
• think of a neat release name
• look through all commits and create a list of changes for the release post (example)
• update AUTHORS via git authors --list --no-email | awk '{ print "- "$0}' >> AUTHORS, then remove the repeated authors.
• update History.md
  • run git changelog -n
  • 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 (we can wait for a volunteer from Homebrew community to do it)