[Distutils] Version management for devpi (was: devpi-{server-2.2.2, web-2.4.0, client-2.3.0} releases)

[Ben Finney]

holger krekel <holger at merlinux.eu> writes:

> We just released devpi-server-2.2.2, devpi-web-2.4.0 and devpi-client-2.3.0,
> core parts of the private pypi package management and testing system.

Thank you for the release, and for continuing to work on this code base.

What reason is there to have different code bases, with different
versions, for a collection that is so clearly all related and makes
sense as a single code base?

It's very confusing to know what versions relate to other versions of
other parts of devpi. The versions don't help to know the timeline,
which defeats one of the primary purposes of versions on a code base.

Since the code tends to be ready for release at the same time, why not
make a single version string for the whole code base, and release it as
a unit?

-- 
 \      “Reichel's Law: A body on vacation tends to remain on vacation |
  `\            unless acted upon by an outside force.” —Carol Reichel |
_o__)                                                                  |
Ben Finney