Re: faulty releases and pypi access [update]
Tres Seaver <[email protected]>
| Newsgroups | gmane.comp.web.zope.zope3 |
|---|---|
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jim Fulton wrote: > On Sep 26, 2007, at 10:42 AM, Stephan Richter wrote: > >> On Wednesday 26 September 2007 10:40, Jim Fulton wrote: >>>> What about using CHANGES.txt, which we should be maintaining anyway? >>> I agree with a change log. CHANGES.txt is difficult to get included >>> in distributions. Having one requires a more complex setup.py. I'd >>> rather recommend including a change log in README.txt. >> -1. I don't like that. We include CHANGES.txt via the long >> description; that's >> good enough for me. > > Do you think that the change log should be included in the distribution? +10. The cheeseshop metadata is not where I would expect to look for a changelog; having it readable there is only helpful *before* I've downloaded. FWIW, I think that both README.txt and CHANGES.txt should be "package data", so that they are discoverable after installing an egg. The top-level README.txt should be boilerplate, and point to those files (the setup.py process can then stitch them all todgether). Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 [email protected] 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 iD8DBQFG+nfe+gerLs4ltQ4RApwzAJ9WjIb1eWRU1LZA8Tm6hAnVLgcnnwCgovHP HlNNaXNmE8X/4nz4oVVpPmE= =PqY/ -----END PGP SIGNATURE-----