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
On Friday 13 July 2007 11:07, 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
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
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
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