You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Carsten Ziegeler <cz...@s-und-n.de> on 2001/12/17 13:00:24 UTC
Planning the next release (was Re: patch politics)
Hi Team,
I think it's time to think of a new release which should be
a maintainance release. We have fixed some bugs, cleaned up
parts of the docs etc.
Now, what else should be done? I see currently two points:
a) The changing of the directory structure according to the proposal.
b) "Forgetting the 2.0 branch" to maintain only one CVS version. This
requires to move all experimental stuff into the scratchpad area.
We have to be sure to be compatible with 2.0!
So what do you think about it? Perhaps a volunteer for a)?
Cheers,
Carsten
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
i18n transformer, Was: Planning the next release (was Re: patch politics)
Posted by Vadim Gritsenko <va...@verizon.net>.
> From: Torsten Curdt [mailto:tcurdt@dff.st]
>
Torsten,
> d) Making sure everything works;) Unfortunately some of
> the samples don't. Somehow e.g. the i18n transformer
> seems to be broken.
Does it work now for you? I fixed some bugs in transformer recently...
Don't know many languages though... (to verify that it works as
expected)
Vadim
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: Planning the next release (was Re: patch politics)
Posted by Torsten Curdt <tc...@dff.st>.
> > Hi Team,
> >
> > I think it's time to think of a new release which should be
> > a maintainance release. We have fixed some bugs, cleaned up
> > parts of the docs etc.
> >
> > Now, what else should be done? I see currently two points:
> >
> > a) The changing of the directory structure according to the proposal.
> >
> > b) "Forgetting the 2.0 branch" to maintain only one CVS version. This
> > requires to move all experimental stuff into the scratchpad area.
> > We have to be sure to be compatible with 2.0!
>
>
> c) Adding the deprecation policy to the docs!
d) Making sure everything works;) Unfortunately some of
the samples don't. Somehow e.g. the i18n transformer
seems to be broken.
--
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: Planning the next release (was Re: patch politics)
Posted by Berin Loritsch <bl...@apache.org>.
Carsten Ziegeler wrote:
> Hi Team,
>
> I think it's time to think of a new release which should be
> a maintainance release. We have fixed some bugs, cleaned up
> parts of the docs etc.
>
> Now, what else should be done? I see currently two points:
>
> a) The changing of the directory structure according to the proposal.
>
> b) "Forgetting the 2.0 branch" to maintain only one CVS version. This
> requires to move all experimental stuff into the scratchpad area.
> We have to be sure to be compatible with 2.0!
c) Adding the deprecation policy to the docs!
>
> So what do you think about it? Perhaps a volunteer for a)?
>
> Cheers,
> Carsten
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
> .
>
>
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: Planning the next release (was Re: patch politics)
Posted by giacomo <gi...@apache.org>.
On Mon, 17 Dec 2001, Carsten Ziegeler wrote:
> Gerhard Froehlich wrote:
> >
> > >-----Original Message-----
> > >From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de]
> > >Sent: Monday, December 17, 2001 1:00 PM
> > >To: Cocoon-Dev
> > >Subject: Planning the next release (was Re: patch politics)
> > >
> > >
> > >Hi Team,
> > >
> > >I think it's time to think of a new release which should be
> > >a maintainance release. We have fixed some bugs, cleaned up
> > >parts of the docs etc.
> > >
> > >Now, what else should be done? I see currently two points:
> > >
> > >a) The changing of the directory structure according to the proposal.
> >
> > I can do it if you want. But maybe I need some help:
> > Proposal
> > scratchpad/lib
> > scratchpad/src/org/apache/cocoon/scratchpad/${packages}
> > scratchpad/webapp/...??
> >
> > I don't know if it is possible to have an extra cocoon.roles
> > and cocoon.xconf file (Sitemap ?) for the scratchpad. That would
> > be cool, to prevent messing up the production files.
> >
> Yes, it must be separated, so there must be separate roles and
> configuration files. These all can be merged with a simple
> (yet-to-be-written)
> Ant task which merges during build all those files. For
> the optional components this is already done with the sitemap,
> so there should be no problem in extending this a little bit.
I don't think is it a big problem. If you'd like to compile the
scratchpad part copy it over to the build directory which will overwrite
the ones from the normal java directory (which include the .roles file.
Same with the webapp dir.
Giacomo
>
> Carsten
> > >b) "Forgetting the 2.0 branch" to maintain only one CVS version. This
> > > requires to move all experimental stuff into the scratchpad area.
> > > We have to be sure to be compatible with 2.0!
> >
> > +1
> >
> > >So what do you think about it? Perhaps a volunteer for a)?
> >
> > Gerhard
> >
> > "Whose cruel idea was it for the word "lisp" to have an "s" in it?"
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> > For additional commands, email: cocoon-dev-help@xml.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: Planning the next release (was Re: patch politics)
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Gerhard Froehlich wrote:
>
> >-----Original Message-----
> >From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de]
> >Sent: Monday, December 17, 2001 1:00 PM
> >To: Cocoon-Dev
> >Subject: Planning the next release (was Re: patch politics)
> >
> >
> >Hi Team,
> >
> >I think it's time to think of a new release which should be
> >a maintainance release. We have fixed some bugs, cleaned up
> >parts of the docs etc.
> >
> >Now, what else should be done? I see currently two points:
> >
> >a) The changing of the directory structure according to the proposal.
>
> I can do it if you want. But maybe I need some help:
> Proposal
> scratchpad/lib
> scratchpad/src/org/apache/cocoon/scratchpad/${packages}
> scratchpad/webapp/...??
>
> I don't know if it is possible to have an extra cocoon.roles
> and cocoon.xconf file (Sitemap ?) for the scratchpad. That would
> be cool, to prevent messing up the production files.
>
Yes, it must be separated, so there must be separate roles and
configuration files. These all can be merged with a simple
(yet-to-be-written)
Ant task which merges during build all those files. For
the optional components this is already done with the sitemap,
so there should be no problem in extending this a little bit.
Carsten
> >b) "Forgetting the 2.0 branch" to maintain only one CVS version. This
> > requires to move all experimental stuff into the scratchpad area.
> > We have to be sure to be compatible with 2.0!
>
> +1
>
> >So what do you think about it? Perhaps a volunteer for a)?
>
> Gerhard
>
> "Whose cruel idea was it for the word "lisp" to have an "s" in it?"
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: Planning the next release (was Re: patch politics)
Posted by Gerhard Froehlich <g-...@gmx.de>.
>-----Original Message-----
>From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de]
>Sent: Monday, December 17, 2001 1:00 PM
>To: Cocoon-Dev
>Subject: Planning the next release (was Re: patch politics)
>
>
>Hi Team,
>
>I think it's time to think of a new release which should be
>a maintainance release. We have fixed some bugs, cleaned up
>parts of the docs etc.
>
>Now, what else should be done? I see currently two points:
>
>a) The changing of the directory structure according to the proposal.
I can do it if you want. But maybe I need some help:
Proposal
scratchpad/lib
scratchpad/src/org/apache/cocoon/scratchpad/${packages}
scratchpad/webapp/...??
I don't know if it is possible to have an extra cocoon.roles
and cocoon.xconf file (Sitemap ?) for the scratchpad. That would
be cool, to prevent messing up the production files.
>b) "Forgetting the 2.0 branch" to maintain only one CVS version. This
> requires to move all experimental stuff into the scratchpad area.
> We have to be sure to be compatible with 2.0!
+1
>So what do you think about it? Perhaps a volunteer for a)?
Gerhard
"Whose cruel idea was it for the word "lisp" to have an "s" in it?"
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: Planning the next release (was Re: patch politics)
Posted by giacomo <gi...@apache.org>.
On Tue, 18 Dec 2001, Carsten Ziegeler wrote:
> Giacomo Pati wrote:
> >
> > Quoting Carsten Ziegeler <cz...@s-und-n.de>:
> >
> > > Giacomo Pati wrote:
> > > >
> > > > On Mon, 17 Dec 2001, Carsten Ziegeler wrote:
> > > >
> > > > > Hi Team,
> > > > >
> > > > > I think it's time to think of a new release which should be
> > > > > a maintainance release. We have fixed some bugs, cleaned up
> > > > > parts of the docs etc.
> > > > >
> > > > > Now, what else should be done? I see currently two points:
> > > > >
> > > > > a) The changing of the directory structure according to the
> > > proposal.
> > > > >
> > > > > b) "Forgetting the 2.0 branch" to maintain only one CVS version.
> > > This
> > > > > requires to move all experimental stuff into the scratchpad area.
> > > > > We have to be sure to be compatible with 2.0!
> > > > >
> > > > > So what do you think about it? Perhaps a volunteer for a)?
> > > >
> > > > I can do a) in the HEAD (I don't think we should do it in 2.0 branch)
> > > >
> > > Great!
> > > I agree with you here, but we should then make a 2.0.1 release from
> > > the HEAD. So then we really do not need to worry about the 2.0 branch
> > > anymore.
> >
> > As we have applied all the patches *also* to the 2.0 branch we
> > can (for a 2.0.1
> > release) build it from there and stick with HEAD afterwards (no
> > more synching)
> >
> Hm, no I think that we then have the same situation as now. The HEAD and
> the 2.0 branch differ in some points. Sooner or later we have to decide
> what of the new functions in the HEAD should be in the next release
> of Cocoon.
> So I think we should move everything which is additional to the 2.0 branch
> in the scratchpad area. There might be exceptions for this rule.
> We can then directly make a 2.0.1 version from the HEAD and afterwards
> move that parts from the scratchpad area back to the src which are
> finished.
>
> If we first would do a 2.0.1 from the 2.0 branch, we still need to move
> some parts of the HEAD in the scratchpad area.
>
> I feel that making a 2.0.1 from a "cleanup" HEAD is a little bit less work.
Ok.
Giacomo
>
> Carsten
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: Planning the next release (was Re: patch politics)
Posted by Gerhard Froehlich <g-...@gmx.de>.
>-----Original Message-----
>From: Vadim Gritsenko [mailto:vadim.gritsenko@verizon.net]
>Sent: Tuesday, December 18, 2001 3:48 PM
>To: cocoon-dev@xml.apache.org
>Subject: RE: Planning the next release (was Re: patch politics)
>
>
>> From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de]
>>
>> Giacomo Pati wrote:
>> >
>> > Quoting Carsten Ziegeler <cz...@s-und-n.de>:
>> >
>> > > Giacomo Pati wrote:
>> > > >
>> > > > On Mon, 17 Dec 2001, Carsten Ziegeler wrote:
>> > > >
>> > > > > Hi Team,
>> > > > >
>> > > > > I think it's time to think of a new release which should be
>> > > > > a maintainance release. We have fixed some bugs, cleaned up
>> > > > > parts of the docs etc.
>> > > > >
>> > > > > Now, what else should be done? I see currently two points:
>> > > > >
>> > > > > a) The changing of the directory structure according to the
>> > > proposal.
>> > > > >
>> > > > > b) "Forgetting the 2.0 branch" to maintain only one CVS
>version.
>> > > This
>> > > > > requires to move all experimental stuff into the scratchpad
>area.
>> > > > > We have to be sure to be compatible with 2.0!
>> > > > >
>> > > > > So what do you think about it? Perhaps a volunteer for a)?
>> > > >
>> > > > I can do a) in the HEAD (I don't think we should do it in 2.0
>branch)
>> > > >
>> > > Great!
>> > > I agree with you here, but we should then make a 2.0.1 release
>from
>> > > the HEAD. So then we really do not need to worry about the 2.0
>branch
>> > > anymore.
>> >
>> > As we have applied all the patches *also* to the 2.0 branch we
>> > can (for a 2.0.1
>> > release) build it from there and stick with HEAD afterwards (no
>> > more synching)
>> >
>> Hm, no I think that we then have the same situation as now. The HEAD
>and
>> the 2.0 branch differ in some points. Sooner or later we have to
>decide
>> what of the new functions in the HEAD should be in the next release
>> of Cocoon.
>> So I think we should move everything which is additional to the 2.0
>branch
>> in the scratchpad area. There might be exceptions for this rule.
>> We can then directly make a 2.0.1 version from the HEAD and afterwards
>> move that parts from the scratchpad area back to the src which are
>> finished.
>>
>> If we first would do a 2.0.1 from the 2.0 branch, we still need to
>move
>> some parts of the HEAD in the scratchpad area.
>>
>> I feel that making a 2.0.1 from a "cleanup" HEAD is a little bit less
>work.
>
>Agree with that. +1 for 2.0.1 from the HEAD.
>
>Vadim
+1 from me
Gerhard
"EARTH FIRST! We'll strip-mine the other planets later."
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: Planning the next release (was Re: patch politics)
Posted by Vadim Gritsenko <va...@verizon.net>.
> From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de]
>
> Giacomo Pati wrote:
> >
> > Quoting Carsten Ziegeler <cz...@s-und-n.de>:
> >
> > > Giacomo Pati wrote:
> > > >
> > > > On Mon, 17 Dec 2001, Carsten Ziegeler wrote:
> > > >
> > > > > Hi Team,
> > > > >
> > > > > I think it's time to think of a new release which should be
> > > > > a maintainance release. We have fixed some bugs, cleaned up
> > > > > parts of the docs etc.
> > > > >
> > > > > Now, what else should be done? I see currently two points:
> > > > >
> > > > > a) The changing of the directory structure according to the
> > > proposal.
> > > > >
> > > > > b) "Forgetting the 2.0 branch" to maintain only one CVS
version.
> > > This
> > > > > requires to move all experimental stuff into the scratchpad
area.
> > > > > We have to be sure to be compatible with 2.0!
> > > > >
> > > > > So what do you think about it? Perhaps a volunteer for a)?
> > > >
> > > > I can do a) in the HEAD (I don't think we should do it in 2.0
branch)
> > > >
> > > Great!
> > > I agree with you here, but we should then make a 2.0.1 release
from
> > > the HEAD. So then we really do not need to worry about the 2.0
branch
> > > anymore.
> >
> > As we have applied all the patches *also* to the 2.0 branch we
> > can (for a 2.0.1
> > release) build it from there and stick with HEAD afterwards (no
> > more synching)
> >
> Hm, no I think that we then have the same situation as now. The HEAD
and
> the 2.0 branch differ in some points. Sooner or later we have to
decide
> what of the new functions in the HEAD should be in the next release
> of Cocoon.
> So I think we should move everything which is additional to the 2.0
branch
> in the scratchpad area. There might be exceptions for this rule.
> We can then directly make a 2.0.1 version from the HEAD and afterwards
> move that parts from the scratchpad area back to the src which are
> finished.
>
> If we first would do a 2.0.1 from the 2.0 branch, we still need to
move
> some parts of the HEAD in the scratchpad area.
>
> I feel that making a 2.0.1 from a "cleanup" HEAD is a little bit less
work.
Agree with that. +1 for 2.0.1 from the HEAD.
Vadim
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: Planning the next release (was Re: patch politics)
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Giacomo Pati wrote:
>
> Quoting Carsten Ziegeler <cz...@s-und-n.de>:
>
> > Giacomo Pati wrote:
> > >
> > > On Mon, 17 Dec 2001, Carsten Ziegeler wrote:
> > >
> > > > Hi Team,
> > > >
> > > > I think it's time to think of a new release which should be
> > > > a maintainance release. We have fixed some bugs, cleaned up
> > > > parts of the docs etc.
> > > >
> > > > Now, what else should be done? I see currently two points:
> > > >
> > > > a) The changing of the directory structure according to the
> > proposal.
> > > >
> > > > b) "Forgetting the 2.0 branch" to maintain only one CVS version.
> > This
> > > > requires to move all experimental stuff into the scratchpad area.
> > > > We have to be sure to be compatible with 2.0!
> > > >
> > > > So what do you think about it? Perhaps a volunteer for a)?
> > >
> > > I can do a) in the HEAD (I don't think we should do it in 2.0 branch)
> > >
> > Great!
> > I agree with you here, but we should then make a 2.0.1 release from
> > the HEAD. So then we really do not need to worry about the 2.0 branch
> > anymore.
>
> As we have applied all the patches *also* to the 2.0 branch we
> can (for a 2.0.1
> release) build it from there and stick with HEAD afterwards (no
> more synching)
>
Hm, no I think that we then have the same situation as now. The HEAD and
the 2.0 branch differ in some points. Sooner or later we have to decide
what of the new functions in the HEAD should be in the next release
of Cocoon.
So I think we should move everything which is additional to the 2.0 branch
in the scratchpad area. There might be exceptions for this rule.
We can then directly make a 2.0.1 version from the HEAD and afterwards
move that parts from the scratchpad area back to the src which are
finished.
If we first would do a 2.0.1 from the 2.0 branch, we still need to move
some parts of the HEAD in the scratchpad area.
I feel that making a 2.0.1 from a "cleanup" HEAD is a little bit less work.
Carsten
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: Planning the next release (was Re: patch politics)
Posted by Giacomo Pati <gi...@apache.org>.
Quoting Carsten Ziegeler <cz...@s-und-n.de>:
> Giacomo Pati wrote:
> >
> > On Mon, 17 Dec 2001, Carsten Ziegeler wrote:
> >
> > > Hi Team,
> > >
> > > I think it's time to think of a new release which should be
> > > a maintainance release. We have fixed some bugs, cleaned up
> > > parts of the docs etc.
> > >
> > > Now, what else should be done? I see currently two points:
> > >
> > > a) The changing of the directory structure according to the
> proposal.
> > >
> > > b) "Forgetting the 2.0 branch" to maintain only one CVS version.
> This
> > > requires to move all experimental stuff into the scratchpad area.
> > > We have to be sure to be compatible with 2.0!
> > >
> > > So what do you think about it? Perhaps a volunteer for a)?
> >
> > I can do a) in the HEAD (I don't think we should do it in 2.0 branch)
> >
> Great!
> I agree with you here, but we should then make a 2.0.1 release from
> the HEAD. So then we really do not need to worry about the 2.0 branch
> anymore.
As we have applied all the patches *also* to the 2.0 branch we can (for a 2.0.1
release) build it from there and stick with HEAD afterwards (no more synching)
Giacomo
>
> Carsten
>
> > Giacomo
> >
> > >
> > > Cheers,
> > > Carsten
> > >
> > >
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> > > For additional commands, email: cocoon-dev-help@xml.apache.org
> > >
> > >
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> > For additional commands, email: cocoon-dev-help@xml.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: Planning the next release (was Re: patch politics)
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Giacomo Pati wrote:
>
> On Mon, 17 Dec 2001, Carsten Ziegeler wrote:
>
> > Hi Team,
> >
> > I think it's time to think of a new release which should be
> > a maintainance release. We have fixed some bugs, cleaned up
> > parts of the docs etc.
> >
> > Now, what else should be done? I see currently two points:
> >
> > a) The changing of the directory structure according to the proposal.
> >
> > b) "Forgetting the 2.0 branch" to maintain only one CVS version. This
> > requires to move all experimental stuff into the scratchpad area.
> > We have to be sure to be compatible with 2.0!
> >
> > So what do you think about it? Perhaps a volunteer for a)?
>
> I can do a) in the HEAD (I don't think we should do it in 2.0 branch)
>
Great!
I agree with you here, but we should then make a 2.0.1 release from
the HEAD. So then we really do not need to worry about the 2.0 branch
anymore.
Carsten
> Giacomo
>
> >
> > Cheers,
> > Carsten
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> > For additional commands, email: cocoon-dev-help@xml.apache.org
> >
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: Planning the next release (was Re: patch politics)
Posted by giacomo <gi...@apache.org>.
On Mon, 17 Dec 2001, Carsten Ziegeler wrote:
> Hi Team,
>
> I think it's time to think of a new release which should be
> a maintainance release. We have fixed some bugs, cleaned up
> parts of the docs etc.
>
> Now, what else should be done? I see currently two points:
>
> a) The changing of the directory structure according to the proposal.
>
> b) "Forgetting the 2.0 branch" to maintain only one CVS version. This
> requires to move all experimental stuff into the scratchpad area.
> We have to be sure to be compatible with 2.0!
>
> So what do you think about it? Perhaps a volunteer for a)?
I can do a) in the HEAD (I don't think we should do it in 2.0 branch)
Giacomo
>
> Cheers,
> Carsten
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org