[Distutils] dev versions
Tres Seaver
tseaver at palladion.com
Tue Oct 13 19:45:36 CEST 2009
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Reinout van Rees wrote:
> On 2009-10-08, Ian Bicking <ianb at colorstudy.com> wrote:
>> So after creating, say, version 0.3.1, I always mark a package as 0.3.2dev.
>> But this is annoying, you might never create a version 0.3.2 (e.g., 0.4
>> might be the next level). So, it would be better to use something like
>> 0.3.1~dev. What is considered best practice for this? Ideally something
>> that works with both Setuptools and the upcoming Distribute version spec.
>
>
> a) Where's the annoyment exactly? It is easy to change and it's a release-time
> decision anyway.
- - It makes the package under development "look" like it is released,
which is a Bad Thing for people who blindly want to depend on stuff.
- - It creates lots of unnecessary commit message churn (go count how many
messages on the zope-commits list are for "SVB" management).
- - Furthermore, it (appears) to promise a release which may or may not
ever be made
- - It encourages people to forego thinking about what the correct release
number should be (we've had a number of releases which should have
been "feature" releses which got made using the "default next version"
bugfix number).
> b) In a previous discussion on a zope mailinglist (about using '0' for this
> purpose, which was pretty much shot down for the zope toolkit because of
> the problems attached to it), someone mentioned adding '+svn' to the
> previous version number. So from 0.3.1 to 0.3.1+svn. Apparently that
> sorts it behind 0.3.1. You could try something like that. The poster
> mentioned it as a debian standard.
The ZTK discussion was closed by fiat, not by achieving consensus.
Neither Jim nor I agree with the proclamation, but will (grudgingly, in
my case) abide by it within the context of the ZTK.
Tres.
- --
===================================================================
Tres Seaver +1 540-429-0999 tseaver at palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkrUvMAACgkQ+gerLs4ltQ5uiwCfeGfFO8VpkdKNszrDdKoEFLyT
A20An0TkCQYjaxWdCRJmp/I68OvBTn2D
=cRaR
-----END PGP SIGNATURE-----
More information about the Distutils-SIG
mailing list