[Zope-Coders] How to get going :-)

[Chris McDonough]

Uh oh, me and Andreas are providing conflicting info.  :-(

Brian, when do you need to write a line to CHANGES.txt in the trunk? 
When do you need to do it in the branch?

Chris McDonough wrote:
> 
> 
> Steve Alexander wrote:
> 
>> Chris McDonough wrote:
>>  >
>>
>>> OTOH, if it's a bugfix
>>> situation where its just a nobrainer, just check the fix in to both the
>>> trunk and the current release branch.
>>
>>
>>
>>
>> This is probably obvious, but I guess that when checking a bugfix into 
>> the the trunk and the current release, a CHANGES.txt file needs to be 
>> changed also.
> 
> 
> Yes, sorry.  Usually you need make a comment in it on the current 
> release branch only, though.  The right file is doc/CHANGES.txt
> 
>>
>> Does the CHANGES.txt file get changed differently for the trunk and 
>> release?
>>
> 
> The only time an entry should make it in to the trunk CHANGES.txt is if 
> the feature only makes it in to the trunk for some reason... in practice 
> this is rare.
> 
>> Where should new changes be appended to; the top of the change list, 
>> the bottom, or near a similar change?
> 
> 
> The top... it's organizedin reverse-chronological order by release.  if 
> you're changing the release branch's CHANGES.txt and there's no entry 
> for the release you're working on (let say, for instance, it hasn't been 
> released yet! ;-), just make a section named "Unreleased" and put the 
> comments under it.
> 
> Note that it's usually a good idea to reference the Collector issue 
> number in the CHANGES.txt
> .
> 


-- 
Chris McDonough                    Zope Corporation
http://www.zope.org             http://www.zope.com
"Killing hundreds of birds with thousands of stones"