You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Gianugo Rabellino <gi...@gmail.com> on 2005/02/14 09:46:18 UTC

Re: Adding the sitemap path to Cocoon's Request object

On Mon, 14 Feb 2005 09:29:08 +0100, Carsten Ziegeler
<cz...@apache.org> wrote:
> Gianugo Rabellino wrote:
>  > <SNIP/>
> > I am very bad in naming
> > stuff, but I would say that something like getSitemapPath() could do the
> > trick.
> Hmm, did you have a look at the Request interface in 2.2:
>      String getSitemapPath();
> 
> Is this what you're looking for :)

D'OH! OK, I'm going to write 200 times "every committer is supposed to
check out 2.2 as well" as a punishment.

So, let's change the question: what's wrong in backporting this
functionality to 2.1?

Ciao,
-- 
Gianugo Rabellino
Pro-netics s.r.l. -  http://www.pro-netics.com
Orixo, the XML business alliance: http://www.orixo.com
(blogging at http://www.rabellino.it/blog/)

Re: Adding the sitemap path to Cocoon's Request object

Posted by Reinhard Poetz <re...@apache.org>.
Carsten Ziegeler wrote:
> Gianugo Rabellino wrote:
> 
>> On Mon, 14 Feb 2005 09:29:08 +0100, Carsten Ziegeler
>> <cz...@apache.org> wrote:
>>
>>> Gianugo Rabellino wrote:
>>> > <SNIP/>
>>>
>>>> I am very bad in naming
>>>> stuff, but I would say that something like getSitemapPath() could do 
>>>> the
>>>> trick.
>>>
>>>
>>> Hmm, did you have a look at the Request interface in 2.2:
>>>     String getSitemapPath();
>>>
>>> Is this what you're looking for :)
>>
>>
>>
>> D'OH! OK, I'm going to write 200 times "every committer is supposed to
>> check out 2.2 as well" as a punishment.
>>
>> So, let's change the question: what's wrong in backporting this
>> functionality to 2.1?
>>
> :) My opinion is we shouldn't change contracts in maintenance releases.

+1

> As backporting would change the request interface, I think we shouldn't 
> do it. If we change contracts inbetween, we could imho just skip the 
> versioning schema and simply use month/year as the release version :)
> But that's just my opinion about it.

-- 
Reinhard Pötz           Independant Consultant, Trainer & (IT)-Coach 

{Software Engineering, Open Source, Web Applications, Apache Cocoon}

                                        web(log): http://www.poetz.cc
--------------------------------------------------------------------

Re: Adding the sitemap path to Cocoon's Request object

Posted by Carsten Ziegeler <cz...@apache.org>.
Gianugo Rabellino wrote:
> On Mon, 14 Feb 2005 09:29:08 +0100, Carsten Ziegeler
> <cz...@apache.org> wrote:
> 
>>Gianugo Rabellino wrote:
>> > <SNIP/>
>>
>>>I am very bad in naming
>>>stuff, but I would say that something like getSitemapPath() could do the
>>>trick.
>>
>>Hmm, did you have a look at the Request interface in 2.2:
>>     String getSitemapPath();
>>
>>Is this what you're looking for :)
> 
> 
> D'OH! OK, I'm going to write 200 times "every committer is supposed to
> check out 2.2 as well" as a punishment.
> 
> So, let's change the question: what's wrong in backporting this
> functionality to 2.1?
> 
:) My opinion is we shouldn't change contracts in maintenance releases. 
As backporting would change the request interface, I think we shouldn't 
do it. If we change contracts inbetween, we could imho just skip the 
versioning schema and simply use month/year as the release version :)
But that's just my opinion about it.

Carsten

-- 
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/