diff options
author | Harel Ben-Attia <harelba@gmail.com> | 2020-09-19 12:54:51 +0300 |
---|---|---|
committer | Harel Ben-Attia <harelba@gmail.com> | 2020-09-19 12:54:51 +0300 |
commit | a7d0555e6dec026571377255a22ae116d5fb94ff (patch) | |
tree | 46855c70c385e7a0588187c76b4f89ec01cf4e6c | |
parent | ef0235a989ab321919467d3098ff7b10f2f35db9 (diff) |
-rw-r--r-- | VERSION_BUMP.md | 18 | ||||
-rwxr-xr-x | bin/q.py | 2 | ||||
-rwxr-xr-x | do-manual-release.sh | 2 | ||||
-rw-r--r-- | setup.py | 2 |
4 files changed, 21 insertions, 3 deletions
diff --git a/VERSION_BUMP.md b/VERSION_BUMP.md new file mode 100644 index 0000000..7a4c5bf --- /dev/null +++ b/VERSION_BUMP.md @@ -0,0 +1,18 @@ + +# Version bump +Currently, there are some manual steps needed in order to release a new version: + +* Make sure that you're in a branch +* Change the version in the following three files: `bin/q.py`, `setup.py` and `do-manual-release.sh` and commit them to the branch +* perform merge into master of that branch +* add a tag of the release version +* `git push --tags origin master` +* create a release in github with the tag you've just created + +Pushing to master will trigger a build/release, and will push the artifacts to the new release as assets. + +The reason for this is related to limitations in the way that pyci uploads the binaries to github. + +# + +TBD - Continue with the flow of wrapping the artifacts with rpm/deb, copying the files to packages-for-q, and updating the web site. @@ -33,7 +33,7 @@ from __future__ import print_function from collections import OrderedDict -q_version = '2.0.17' +q_version = '2.0.18' __all__ = [ 'QTextAsData' ] diff --git a/do-manual-release.sh b/do-manual-release.sh index 1111677..9e0d787 100755 --- a/do-manual-release.sh +++ b/do-manual-release.sh @@ -2,7 +2,7 @@ set -e -VERSION=2.0.17 +VERSION=2.0.18 if [[ "$TRAVIS_BRANCH" != "master" ]] then @@ -2,7 +2,7 @@ from setuptools import setup -q_version = '2.0.17' +q_version = '2.0.18' setup( name='q', |