Comments on: Version numbers on trunk and maintenance branches http://philikon.wordpress.com/2008/07/19/version-numbers-on-trunk-and-maintenance-branches/ Philipp on software and other interesting things Thu, 01 Oct 2009 18:05:34 +0000 http://wordpress.com/ hourly 1 By: Wichert Akkerman http://philikon.wordpress.com/2008/07/19/version-numbers-on-trunk-and-maintenance-branches/#comment-55 Wichert Akkerman Sun, 20 Jul 2008 10:35:57 +0000 http://philikon.wordpress.com/?p=12#comment-55 Unfortunately setuptools has a very magic version version comparison algorithm which no package manager will ever support. It's handling of a, b, c and rc is too magic. Unfortunately setuptools has a very magic version version comparison algorithm which no package manager will ever support. It’s handling of a, b, c and rc is too magic.

]]> By: philikon http://philikon.wordpress.com/2008/07/19/version-numbers-on-trunk-and-maintenance-branches/#comment-54 philikon Sun, 20 Jul 2008 09:47:48 +0000 http://philikon.wordpress.com/?p=12#comment-54 That would work for me, too, as long as a trunk or branch checkout did not contain a version number that could be confused with a release version number. Setuptools just happens to support this neatly with the 'dev' marker. That would work for me, too, as long as a trunk or branch checkout did not contain a version number that could be confused with a release version number. Setuptools just happens to support this neatly with the ‘dev’ marker.

]]> By: Ben Finney http://philikon.wordpress.com/2008/07/19/version-numbers-on-trunk-and-maintenance-branches/#comment-53 Ben Finney Sun, 20 Jul 2008 08:14:10 +0000 http://philikon.wordpress.com/?p=12#comment-53 > What makes it a good idea is the fact that … the version number is actually meaningful, due to setuptools’ version semantics That's all well and good if setuptools is the only thing that compares version numbers to one another. What about an operating-system package manager? What about some external tool looking at version numbers on file archives? What about the application itself? The version number should be *trivially* comparable, precisely so we don't have to rely on one particular tool in order to hope to get the right "semantics". Why not just choose version numbers that compare correctly in alphanumeric sequence? > What makes it a good idea is the fact that … the version number is actually meaningful, due to setuptools’ version semantics

That’s all well and good if setuptools is the only thing that compares version numbers to one another. What about an operating-system package manager? What about some external tool looking at version numbers on file archives? What about the application itself?

The version number should be *trivially* comparable, precisely so we don’t have to rely on one particular tool in order to hope to get the right “semantics”. Why not just choose version numbers that compare correctly in alphanumeric sequence?

]]>