You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Reinhard Poetz <re...@apache.org> on 2005/03/03 09:02:03 UTC
status.xml in trunk
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.
--
Reinhard Pötz Independant Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
Re: status.xml in trunk
Posted by Reinhard Poetz <re...@apache.org>.
Vadim Gritsenko wrote:
> 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.
yes, that's the idea.
--
Reinhard Pötz Independant Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
Re: status.xml in trunk
Posted by Vadim Gritsenko <va...@reverycodes.com>.
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
Re: status.xml in trunk
Posted by Reinhard Poetz <re...@apache.org>.
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.
--
Reinhard Pötz Independant Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
Re: status.xml in trunk
Posted by Carsten Ziegeler <cz...@apache.org>.
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.
Carsten
--
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/