On Jul 13, 2007, at 11:34 AM, 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.


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.

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 reasonable too, although it's more work than what I'm suggesting. :)


Jim Fulton                      mailto:[EMAIL PROTECTED]                Python 
CTO                             (540) 361-1714                  
Zope Corporation        http://www.zope.com             http://www.zope.org

Zope3-dev mailing list
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com

Reply via email to