cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vadim Gritsenko <va...@reverycodes.com>
Subject Re: status.xml in trunk
Date Thu, 03 Mar 2005 13:33:34 GMT
Reinhard Poetz wrote:
> Carsten Ziegeler wrote:
> 
>> Reinhard Poetz wrote:
>>
>>> Is there any reason why we duplicate all release/action entries that 
>>> are valid for 2.1 and trunk?
>>>
>>> If there is no objection I will remove all entries that belong to 2.1 
>>> in trunk/status.xml.
>>
>> In theory there is no reason as everything that is applied to 2.1 should
>> also be applied to trunk. But unfortunately people forget about it which
>> results in differences between the two versions. With two separate
>> status.xml files we have a little tool to see if something has been
>> applied to 2.1 that hasn't been added to trunk as well - of course if
>> someone does not update status.xml in 2.1 then we won't see it anyway.
>>
>> So, if we take more care when applying things I'm +1 for your idea.
> 
> ok, then let's wait with cleaning it up until 2.2 will be released.

Do you want to point to 2.1/changes.html instead of replicating? 
2.2/changes.html then should mention "branching point" - which probably will be 
2.1.7 release. I'd guess that with 2.1.8 (if it happens) branches might diverge.

Vadim

Mime
View raw message