-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Fred Drake wrote:

On Thu, May 29, 2008 at 12:11 AM, Fred L. Drake, Jr. <fdrake@gmail.com> wrote:

...

Log message for revision 87005: prepare for a sanitizing release, thanks to a wild svn-based release ... CHANGES =======

+0.6.1 (2008-05-29) +------------------ + +Unchanged from 0.5.2, but released with a new version number thanks to a +package with an 0.6.1dev-rBFN revision found in the wild.

This is disgusting. We're going to have to all avoid placing those nasty releases with Subversion revision numbers in any public repositories. I'm sure I'm among the guilty, but... we've gotta do better.

Amen. <dead-horse beat="sans-merci"> If we quit keeping "guessed nex version number" on the trunk (or on release branches), such a release would be harder to make. Also, we wouldn't have to make unneeded changes to setup.py on the trunk. </dead-horse> Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD4DBQFIQYqD+gerLs4ltQ4RAvu8AKCXDHKeIJm9cD5HGjOPwPd9SdqctQCXdZXF gTfE3sEsazUJdDJqO48F3A== =Ltvx -----END PGP SIGNATURE-----