[Zope-CMF] Re: [dev] After the goldrush....

[Tres Seaver]

yuppie wrote:
> Tres Seaver wrote:
> 
>> Jens Vagelpohl wrote:
>>
>>>>  - I would like to do another CMF bug day before the final release.
>>>>    Since "last Friday of the month" is already teed up for Zope, we
>>>>    could either piggyback that date (27 August) or avoid it (e.g.,
>>>>    3 September).  Opinions?
>>>
>>>
>>> +0 (Both dates are fine by me)
>>
>>
>> Let's try for the 3rd then, in conjunction with the Zope bug day.
> 
> 
> +0
> 
> Can't tell if I'll be available at one of these days.
> 
>>>>  - Please check bugfixes in on both the HEAD and the 'CMF-1_5-branch',
>>>>    and add them only to 'CHANGES.txt' on the branch.
>>>
>>>
>>> They should not be noted in CHANGES.txt on the HEAD if they end up 
>>> there?
>>
>>
>> That is a good question.  One of the things I want to do before the 
>> final release is weed out the duplicates in CHANGES.txt and 
>> HISTORY.txt.  Maybe it makes most sense to continue recording the 
>> duplicates on the HEAD, just as a confirmation that the forward-port 
>> did occur.
> 
> 
> -1
> 
> Unless there is a very good reason I don't like to have different 
> checkin policies for Zope and CMF.
> 
> Branch and HEAD checkins should be done at the same time, so watching 
> the checkin list it should be easy to spot missing forward-ports.
> 
> If we change to the new policy: Checkin notes and their order should be 
> identical to allow diffing.
> 
> 
> Just my 2 cents, Yuppie
> 
> _______________________________________________ 
> Zope-CMF maillist  -  Zope-CMF at lists.zope.org
> http://mail.zope.org/mailman/listinfo/zope-cmf
> 
> See http://collector.zope.org/CMF for bug reports and feature requests
> 

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.

Tres.
-- 
===============================================================
Tres Seaver                                tseaver at zope.com
Zope Corporation      "Zope Dealers"       http://www.zope.com