cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ralph Goers <Ralph.Go...@digitalinsight.com>
Subject RE: Incompatible change Request.getRequestURI()
Date Thu, 22 Apr 2004 19:48:11 GMT
Ouch.

Presumably this is mixed in with other fixes, etc. meant for 2.1.5.  That
would mean that if the release management proposal you made is followed no
more maintenance can be done on 2.1 unless this is pulled out.

One thing I really don't understand is how Cocoon's CVS is set up. In
projects I have worked on new development is always on head. When a release
is done a branch is made and all maintenance occurs on that branch (and is
merged into the head). From discussion here, it sounds like instead Cocoon
has different repositories for different releases. I'm just curious as to
why.

Ralph

-----Original Message-----
From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de] 
Sent: Thursday, April 22, 2004 12:04 PM
To: dev@cocoon.apache.org
Subject: RE: Incompatible change Request.getRequestURI()

It's a feature. We discussed this incompatible change some weeks
ago and voted to do it as now an internal redirect is a real
internal redirect, so there is no difference to an external
redirect anymore.

PS: This is another candidate to make a 2.2 release next.

Carsten 

 

Mime
View raw message