On Thu, 24 Mar 2016, Alan Pevec wrote:
Another example (not release:managed project but still) where we have
this confusion is gnocchi:
openstack/gnocchi > master $ python ./setup.py --version
2.0.1.dev61
openstack/gnocchi > stable/2.0 $ python ./setup.py --version
2.0.3.dev13
Sorry, I've never understood this feature of pbr (pre and post versioning
is it?). Don't these problems go away if everyone just steps up and uses
explicit version numbers in the projects (in __version__)[1].
No guessing required. No weird magic in pbr that few people
understand.
If some kind of automatic control and validation is required, do it
during the explicit tagging stage?
What is the goal of pre versioning?
[1] The fact that I can't look in the code for __version__ gives me
rage face.
--
Chris Dent (�s°□°)�s�喋擤ォ� http://anticdent.org/
freenode: cdent tw: @anticdent
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
