Closed jamesleesaunders closed 7 years ago
Hey @jamesleesaunders, good idea. The release notes are good. We have a script set up on Jenkins that will take care of bumping the version numbers, tagging the release on GitHub, and pushing to PyPI. So in the future we can let that script bump the version number in the __init__.py
. I'll merge this without the version and then run the release job to bump us to 2.2.5.
Also, I copied your release notes over to the GitHub release page as well: https://github.com/nioinnovation/python-xbee/releases/tag/2.2.5
@mattdodge Cool thanks! I notice the newest tag generated by Jenkins is '2.2.5' where as the previous tags are 'v2.2.4', 'v2.2.3' etc. I dont know much about how Jenkins works but is this something which is configurable, or would you like me to change all the previous tags? Or would you rather they stay as they are? Renaming tags whilst maintaining their dates Does envole a little git craftwork! (You may have guessed I am a little OCD... the best developers are ;-) )
Also nice touch adding the PyPi badges to the readme!
Oh, good catch! I've updated the Jenkins job so it will be v2.2.5
rather than 2.2.5
from now on. Also replaced the existing 2.2.5
tag with v2.2.5
.
Hi @hansmosh @mattdodge We have had a few nice additions recently, do you think it is appropriate to bump to 2.2.5 and publish on PyPi? Summary of recent changes: