[Zope-CMF] Re: CHANGES.txt

yuppie y.2004_ at wcm-solutions.de
Sun Aug 15 12:36:48 EDT 2004


Hi!


Jens Vagelpohl wrote:
>> Here is the "official" policy (that I can find) on CHANGES.txt (from :
>>
>>    The path to the file is doc/CHANGES.txt. It lists the changes that
>>    have been made to Zope since the last released version.
>>
>>    If you're fixing a bug, you only need to add to CHANGES.txt in the
>>    branch. If you're adding a feature, you only need to add to
>>    CHANGES.txt in the trunk. Brian Lloyd later stitches them together.
>>
>> Although, in fact, this policy is not clearly followed on the main 
>> Zope tree, either.  I can live with either way, I guess.
> 
> 
> Hmmmm, I wasn't even aware of such an odd policy.

I guess these are the more recent and more official documents:

   <http://dev.zope.org/CVS/ZopeDevelopmentProcess>
   <http://dev.zope.org/Subversion/ZopeDevelopmentProcess>

But the policy is basically the same:

<quoted>

   When you check in a bug fix, you almost always need to:

    * Check in the fix on the current release branch
    * Note the fix in the /doc/CHANGES.txt on the current release
      branch
    * Merge the fix to the trunk to be sure its fixed for the next
      feature release

   Note that you don't need to note the fix in the CHANGES.txt on the
   trunk if you don't want to. At the time a new feature release is
   made, we merge the items in CHANGES.txt from the trunk and current
   release branch so that for any given release it notes the actual
   changes as of that release.

</quoted>

> It's much more straightforward, IMHO, to mandate that changes are noted 
> exactly where they are made. Branch or HEAD doesn't matter. Otherwise it 
> is very hard for people looking at the HEAD to find out what has been 
> done and what hasn't. Also, I bet it is even *less* work to weed out 
> duplicates in CHANGES.txt than it is to stitch it all together from 
> branches... yikes.
> 
> Oh, and yes, I don't think that policy is followed at all on the Zope 
> tree ;)

Seems most people *want to* note the fix in the CHANGES.txt on the 
trunk. That doesn't violate the policy.

I think it is at least confusing that people add these change notes to 
the "HEAD only" section.


Anyway, I also can live with either way. And I'm not the person who has 
to stitch things together.


Cheers,
	Yuppie



More information about the Zope-CMF mailing list