Closed baztian closed 7 years ago
I forgot to mention a requirement:
pip install bumpversion
LGTM. Every time I prepare a release I was thinking about such a tool. I'm OK with dropping dev version.
@sunng87, while I'm at it. What is the purpose of the JIP_VERSION constant in init.py? I guess it sits there to be referenced by setup.py. Correct? I would prefer to have setup.py also under control of bumpversion and remove JIP_VERSION completely. That has the advantage of not having cyclic dependencies from importing init.py in setup.py if you import 3rd party libs that setup.py has not yet been installed. Would that be ok?
@baztian I think having JIP_VERSION in the source is for jip version
command. Does python have more elegant way to deal with that?
__version__
is Python standard. Instead of accessing JIP_VERSION we could access just version.
Rebased onto master
Built a new release using
bumpversion patch
git push --follow-tags upstream
good job!
This PR makes it possible to just call
bumpversion patch
(orbumpversion minor
,bumpversion major
) to update versions, the changelog section of the README and add tags. As a last stepgit push --tags
is required to have a new release. This would drop support for.devX
versions. It might be possible with bumpversion. I haven't checked as I don't see a need for that.@jiptool what do you think?