Use correct new versioning now

This commit is contained in:
Matthias 2019-06-24 20:16:31 +02:00
parent c106534663
commit 8e92fc62a3
1 changed files with 2 additions and 2 deletions

View File

@ -140,7 +140,7 @@ git checkout develop
git checkout -b new_release
```
* Edit `freqtrade/__init__.py` and add the desired version (for example `0.18.0`)
* Edit `freqtrade/__init__.py` and add the version matching the current date (for example `2019.7` for June 2019). Minor versions can be `2019.7-1` should we need to do a second release that month.
* Commit this part
* push that branch to the remote and create a PR against the master branch
@ -163,5 +163,5 @@ git log --oneline --no-decorate --no-merges master..develop
### After-release
* Update version in develop to next valid version and postfix that with `-dev` (`0.18.0 -> 0.18.1-dev`).
* Update version in develop by postfixing that with `-dev` (`2019.6 -> 2019.6-dev`).
* Create a PR against develop to update that branch.