On Friday 01 August 2008, Christophe Combelles wrote:
> > I wanted a separate file that tracks the changes to the
> > controlled-packages.cfg file.
> In my understanding, there is almost no source code in 'zope.release',
> since it has been moved into 'zope.kgs'. So there should be very few
> entries in CHANGES.txt, and I'm not sure there is a real interest in having
> two separate files. In my opinion, it adds confusion, people are more used
> to maintain CHANGES.txt.

Okay, I am open to suggestions and want to hear others give an opinion too.

> The other problem is there is no tag for c1, c2, c3 and c4. I thought
> zope.release was meant to represent the release number of zope.

It is. I and Marius simply did not create those tags.

> I would tend to:
> - create a tag for all missing candidates

Cool, I take you up on that.

> - merge KGS-HISTORY.txt into CHANGES.txt and recover missing information
> from published control-packages.cfg

These are two tasks:

- Update KGS-HISTORY.txt to contain the changes of the previous releases. 
(Luckily you can just look at the SVN changelog for controlled-packages.cfg.) 
I take you up on that one as well! :-)

- Merge KGS-HISTORY.txt into CHANGES.txt. I want to hear a couple more 
opinions on that.

Stephan Richter
Web Software Design, Development and Training
Google me. "Zope Stephan Richter"
Zope-Dev maillist  -  Zope-Dev@zope.org
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope )

Reply via email to