Hi all,
Could someone explain how the core version numbering works after moving to version 2?
Prior to version 2 I thought that semantic versioning was used but now all tagged versions seem to use 4 numbers prior to the hyphen.
This change is causing some confusion for me as to which version is the most up to date, and how to track the latest changes.
I found this on the site http://docs.ansible.com/ansible/community.html#release-numbering but it also seems to imply 3 digits.
Any help appreciated.
Thanks, Alex
Hi Alex, I moved to a 4 digit release version to alleviate some problems we have with packaging (PyPi doesn’t allow the same filename to be uploaded twice). In the event that we have a small packaging problem, we used to have to bump the minor, which I always hated doing. So the 4th digit is really just the packaging release version to us, and the first 3 are the actual release version.
I’ll update that doc to make this a bit more clear in light of the new numbering.
Hi James,
Thanks for the prompt reply and for explaining the new numbering.
I’ve not released any of my own packages to PyPI before so I might be misinterpreting the docs but I’m curious if this packaging identifier could be labelled a post suffix? Or even if the packaging can be uploaded and tested on Test PyPI before releasing? That would mean that packaging issues could be caught there before releasing to a wider audience on PyPI.
Looking at the comparison between releases for 2.0.0 I think a bug fix may have slipped in without the right increment during the packaging changes.
https://github.com/ansible/ansible/compare/v2.0.0.1-1...v2.0.0.2-1
Thanks, Alex
Yes, there was a minor bugfix related to Tower that went in with that as well.