[Zope-CMF] [dev] CHANGES.txt policy

Jens Vagelpohl jens at dataflake.org
Sun Nov 7 14:08:50 EST 2004


On Nov 7, 2004, at 17:41, yuppie wrote:

> Hi!
>
>
> On HEAD I'd really like to have a "HEAD only" section that *only*
> contains changes that didn't go into the maintenance branch. It's hard
> to find out what's the difference between HEAD and branch if all change
> notes are mixed in the same section.
>
> I just cleaned up CHANGES.txt a bit and hope we can agree on that 
> policy.

The way things are presented now in CHANGES.txt on the HEAD looks like 
anyone who works on the 1.5 branch should make sure to keep the 
corresponding part of the HEAD  CHANGES.txt synchronized. I suppose 
that's only a problem in those situation where you really only change 
something on the branch - which shouldn't happen in reality. Unless all 
of a sudden the branch sprouts features that are not on the head...

+1

I personally was always confused about the seemingly different handling 
there. Having a simple policy is good. Let's do it.

jens



More information about the Zope-CMF mailing list