-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Release Cycles
Nimit Kalra edited this page Jun 17, 2016
·
12 revisions
Aim for a new release on the last Monday of each month.
January 25, 2016
- 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)
- attribute all contributors
- update
AUTHORS- run
git authorsand updatePatches and Suggestionssection- remove any repeat users and any users from the
MaintainersandDevelopment Leadsection
- remove any repeat users and any users from the
- run
- update
History.md- run
git changelog - change
n.n.nto new release version
- run
- bump
$VERSIONinbin/git-extrasto 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
- tag version: new release version according to semver (ex:
- publish release
- bump
$VERSIONinbin/git-extrasto next projected release version (ex: if new release version is4.1.0, next projected release version could be4.2.0-dev) - update Homebrew
- notify all issues/PRs under new release milestone that issue/feature is now available via Homebrew