[Zope3-dev] Re: CHANGES.txt
Tres Seaver
tseaver at palladion.com
Fri Jul 13 12:49:44 EDT 2007
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Gary Poster wrote:
> On Jul 13, 2007, at 11:30 AM, Jim Fulton wrote:
>
>> On Jul 13, 2007, at 11:07 AM, Philipp von Weitershausen wrote:
>>
>>> Tres Seaver wrote:
>>>> Doing proper release management can't reeally be called a waste
>>>> of time
>>>> (that would include documenting exactly what *has* changed).
>>> Tres raises a good point. We should continue to maintain a
>>> CHANGES.txt or a 'Changes' section in README.txt for all zope.*
>>> projects now. And I would recommend that others do the same with
>>> z3c.* etc. packages.
>> Agreed.
>>
>> I recommend using a changes section in README.txt because it's
>> tricky getting distutils to include other root-level files and I
>> want to keep our setup scripts as simple as we can.
Distutils sucks in this regard.
> Hm (and sigh). I was following what I thought was another Tres
> suggestion: put CHANGES.txt in the package, and a pointer in the top
> level to the package's version.
That is still my preference: I think a people are more likely to find a
changelog that way.
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.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGl60o+gerLs4ltQ4RAmNmAKCKQPQME/pdBN087ADCZ4suwHAHFwCgz5fi
R+elhyT0jmgcJ7ZJoD00lMU=
=x0f/
-----END PGP SIGNATURE-----
More information about the Zope3-dev
mailing list