diff options
| author | Christian Duerr <contact@christianduerr.com> | 2020-11-15 13:38:46 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-11-15 13:38:46 +0000 |
| commit | 2bb2ed817bebf2dfe7d7891cff236f53ddcf7bf9 (patch) | |
| tree | 0f49067b9146f07de911f11b6a47be3b7237f5e3 /CONTRIBUTING.md | |
| parent | c5340a2ccca9d2e7a6f5f60854800f377f896855 (diff) | |
| download | alacritty-2bb2ed817bebf2dfe7d7891cff236f53ddcf7bf9.tar.gz alacritty-2bb2ed817bebf2dfe7d7891cff236f53ddcf7bf9.zip | |
Bump development version to 0.7.0-dev
This is only an update to the development version and does not represent
a stable release.
Diffstat (limited to 'CONTRIBUTING.md')
| -rw-r--r-- | CONTRIBUTING.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index dcaaface..3a2ecae8 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -123,6 +123,7 @@ The exact steps for an exemplary `0.2.0` release might look like this: 1. Initially, the version on the latest master is `0.2.0-dev` 2. A new `v0.2.0` branch is created for the release 3. On master, the version is bumped to `0.3.0-dev` + and the `-dev` suffix is removed from the `0.2.0-dev` changelog 4. In the branch, the version is bumped to `0.2.0-rc1` 5. The new commit in the branch is tagged as `v0.2.0-rc1` 6. A GitHub release is created for the `v0.2.0-rc1` tag @@ -135,7 +136,6 @@ The exact steps for an exemplary `0.2.0` release might look like this: 12. A GitHub release is created for the `v0.2.0` tag 13. The changelog since the last stable release (**not** RC) is added to the GitHub release description - 14. The `-dev` is stripped from the `0.2.0-dev` changelog entries on master On master and with new planned releases, only the minor version is bumped. This makes it possible to create bug fix releases by incrementing the patch version of a previous minor release, without |