-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/28/2013 11:27 AM, Ronald Oussoren wrote:
> But necessary to have. Or am the only one that accidently released a > version that had serious bugs? Nope. The way to address such a version is to release a new, fixed version (preferably one with a suitably-PEP-compliant version which indicates the version being corrected). The only legitimate reason to yank a release is that you are under legal compulsion to do so (a takedown notice or equivalent), or you discover that the version released has been trojaned in some way. Once you release software into the wild, you can't take it back. For one thing, anybody who has already installed your package won't be able to verify that where got the buggy version if you yank it. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlEvj5EACgkQ+gerLs4ltQ43tACgqdxpqR1zohCuLWRLX4ycB9dx sukAniL+3DylBQtVr5o2+GS96GcMbOXz =YOgY -----END PGP SIGNATURE----- _______________________________________________ Catalog-SIG mailing list Catalog-SIG@python.org http://mail.python.org/mailman/listinfo/catalog-sig
