Update RELEASING.md

This commit is contained in:
Adam Babik 2018-12-21 15:15:06 +01:00 committed by GitHub
parent 3292538b41
commit 7b3da85352
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 15 additions and 13 deletions

View File

@ -34,22 +34,24 @@ TODO: create a script that can do that instead of manual work.
1. Commit and push the change, 1. Commit and push the change,
1. Go to [Jenkins job](https://ci.status.im/job/status-go/job/parallel/), select "RELEASE" and use `develop` branch. 1. Go to [Jenkins job](https://ci.status.im/job/status-go/job/parallel/), select "RELEASE" and use `develop` branch.
## Releasing from develop (regular release) ## Releasing a new patch (no breaking changes or a hot-fix release)
TODO: create a script that can do that instead of manual work. TODO: create a script that can do that instead of manual work.
1. Pull `develop` branch, 1. Checkout a release branch you want to release from (branch have a name `release/0.X`),
1. Checkout a new branch `release/0.X`, 1. Cherry-pick a commit you want to include,
1. Remove `-beta.Z` suffix from the current version (`VERSION` file),
1. Commit and push the change,
1. Checkout develop branch, bump `X`, reset `Z` to `0` and commit to develop,
1. Go to [Jenkins job](https://ci.status.im/job/status-go/job/parallel/), select "RELEASE" and use `release/0.X` branch.
## Releasing from develop (a hot-fix)
TODO: create a script that can do that instead of manual work.
1. Checkout a release branch you want to hot fix (branch have a name `release/0.X`),
1. Bump `Y` (`0.X.Y`) in the current version (`VERSION` file), 1. Bump `Y` (`0.X.Y`) in the current version (`VERSION` file),
1. Commit and push the change to `release/0.X` branch, 1. Commit and push the change to `release/0.X` branch,
1. Go to [Jenkins job](https://ci.status.im/job/status-go/job/parallel/), select "RELEASE" and use `release/0.X` branch name. 1. Go to [Jenkins job](https://ci.status.im/job/status-go/job/parallel/), select "RELEASE" and use `release/0.X` branch name.
## Releasing a new version (breaking changes)
TODO: create a script that can do that instead of manual work.
1. Merge your PR to `develop` branch,
1. Pull `develop` branch locally,
1. Bump `X`, reset `Z` to `0` and commit to `develop` with a message "Bump version to 0.X.Y",
1. Checkout a new branch `release/0.X`,
1. Remove `-beta.Z` suffix from the current version (`VERSION` file),
1. Commit and push the change,
1. Go to [Jenkins job](https://ci.status.im/job/status-go/job/parallel/), select "RELEASE" and use `release/0.X` branch.