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 2002/06/12 09:22:31 UTC
Planning the releases
Hi Team,
I think it's time to recall the "release early release often" paradigma...
As others already mentioned over the last weeks, we should try to
release a 2.0.3 as soon as possible. For this we should collect the
open issues, do them and release (sounds simple, doesn't it?)
As I'm next week on vacation near Paris :) what do you think of
the 1st of July as a release date for 2.0.3?
And if we are already talking about releases, what do we have
to do for 2.1? It seems that many things are nearly finished, so
we can start to think of a beta phase. I would
propose the 15th of July for the release date of 2.1 beta 1.
What do you think?
What are the open issues (for both releases)?
Carsten
Carsten Ziegeler Chief Architect Open Source Group, S&N AG
------------------------------------------------------------------
Cocoon Consulting, Training and Projects
------------------------------------------------------------------
mailto:cziegeler@s-und-n.de http://www.s-und-n.de
http://ziegeler.bei.t-online.de
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: Planning the releases
Posted by Peter Royal <pr...@apache.org>.
On Wednesday 12 June 2002 06:08 am, Davanum Srinivas wrote:
> July 1 for C2.0.3
> July 15 for C2.1 beta 1
+1 to both.
-pete
--
peter royal -> proyal@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 releases
Posted by Davanum Srinivas <di...@yahoo.com>.
+1 for both dates.
July 1 for C2.0.3
July 15 for C2.1 beta 1
Thanks,
dims
--- Christian Haul <ha...@dvs1.informatik.tu-darmstadt.de> wrote:
> On 12.Jun.2002 -- 09:22 AM, Carsten Ziegeler wrote:
> > Hi Team,
> >
> > I think it's time to recall the "release early release often" paradigma...
> >
> > As others already mentioned over the last weeks, we should try to
> > release a 2.0.3 as soon as possible. For this we should collect the
> > open issues, do them and release (sounds simple, doesn't it?)
> >
> > As I'm next week on vacation near Paris :) what do you think of
> > the 1st of July as a release date for 2.0.3?
>
> +1
>
> > And if we are already talking about releases, what do we have
> > to do for 2.1? It seems that many things are nearly finished, so
> > we can start to think of a beta phase. I would
> > propose the 15th of July for the release date of 2.1 beta 1.
> >
> > What do you think?
>
> +1
>
> Chris.
>
> --
> C h r i s t i a n H a u l
> haul@informatik.tu-darmstadt.de
> fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
=====
Davanum Srinivas - http://xml.apache.org/~dims/
__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: Planning the releases
Posted by Christian Haul <ha...@dvs1.informatik.tu-darmstadt.de>.
On 12.Jun.2002 -- 09:22 AM, Carsten Ziegeler wrote:
> Hi Team,
>
> I think it's time to recall the "release early release often" paradigma...
>
> As others already mentioned over the last weeks, we should try to
> release a 2.0.3 as soon as possible. For this we should collect the
> open issues, do them and release (sounds simple, doesn't it?)
>
> As I'm next week on vacation near Paris :) what do you think of
> the 1st of July as a release date for 2.0.3?
+1
> And if we are already talking about releases, what do we have
> to do for 2.1? It seems that many things are nearly finished, so
> we can start to think of a beta phase. I would
> propose the 15th of July for the release date of 2.1 beta 1.
>
> What do you think?
+1
Chris.
--
C h r i s t i a n H a u l
haul@informatik.tu-darmstadt.de
fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: Planning the releases
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Stefano Mazzocchi wrote:
>
> >> And if we are already talking about releases, what do we have to do
> >> for 2.1? It seems that many things are nearly finished, so we can
> >> start to think of a beta phase. I would propose the 15th of July for
> >> the release date of 2.1 beta 1.
>
> -1
>
> We are not even close to what I think 2.1 should be about. I would be in
> favor of an 'alpha' release, meaning that we don't make any effort
> whatsoever for API back compatibility between 2.1 releases until we go
> final (as the WARNING states clearly today), but a beta means that we
> are happy with the interfaces we have and I'm not.
Actually I proposed the date above to push things ;) I currently fear that
we are making the same mistake we made with 2.0 where every month we said,
"Hey, let's move the release just one month because we need this cool thing
in the release".
>
> > - switch to Avalon Source everywhere (is it already done ?)
>
> This is a big one. I would like more info to evaluate this.
What do you need? The switch has already taken place in CVS.
>
> > - switch to LogEnabled
>
> makes sense.
>
> > - I have to write the extended sitemap variable substitution, i.e.
> > {request:foo}. I'm late on this since my Cocoon time is currently
> > devoted to reviewing a book written by people named... Carsten and
> > Matthew ;-)
>
> Cool.
>
> > - more tests and examples on the flowmap. Seems to me that this
> > strategic stuff has been a set a bit aside due to lack of time.
> >
> > Entering beta state would then allow more people to test this baby !
>
> But would slow us down in development and since we need to develop
> rather than to do bugfixes, I don't like this.
>
> My issues are:
>
> 1) the flowmap/sitemap connection semantics are bad. I don't like them.
> We need to do something more aggressive on this realm. NOTE: we'll have
> to change the version of the sitemap namespace in 2.1, but still be back
> compatible with 2.0.x
We could move this to 2.2
>
> 2) finish the design of blocks
>
> Thursday I spent a day with Giacomo talking about the above two points
> (I did consulting in Zurich this week). I'll write extensive RT tomorrow
> or the next day about what we achieved.
>
> I'm happy to state that we were finally able to provide a solution for
> all the problems with had on the table, expecially about sitemap/flowmap
> integration and about block polymorphism.
We could move this to 2.2 as well.
>
> I don't want to enter beta state until we have finished discussing such
> important design issues.
>
Hmm, I agree. But again, I think we are making the same mistake as we did
with the 2.0 release.
What about moving everything which has not been discussed in detail to
the 2.2 release?
> Hope you understand my points.
>
Of course, we can't make a beta if we don't have a stable API/contracts.
Carsten
Carsten Ziegeler Chief Architect Open Source Group, S&N AG
------------------------------------------------------------------
Cocoon Consulting, Training and Projects
------------------------------------------------------------------
mailto:cziegeler@s-und-n.de http://www.s-und-n.de
http://ziegeler.bei.t-online.de
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: Planning the releases
Posted by Stefano Mazzocchi <st...@apache.org>.
Sylvain Wallez wrote:
+1 for 2.0.3 as soon as possible. I don't have issues with that.
> >> And if we are already talking about releases, what do we have to do
> >> for 2.1? It seems that many things are nearly finished, so we can
> >> start to think of a beta phase. I would propose the 15th of July for
> >> the release date of 2.1 beta 1.
-1
We are not even close to what I think 2.1 should be about. I would be in
favor of an 'alpha' release, meaning that we don't make any effort
whatsoever for API back compatibility between 2.1 releases until we go
final (as the WARNING states clearly today), but a beta means that we
are happy with the interfaces we have and I'm not.
> - switch to Avalon Source everywhere (is it already done ?)
This is a big one. I would like more info to evaluate this.
> - switch to LogEnabled
makes sense.
> - I have to write the extended sitemap variable substitution, i.e.
> {request:foo}. I'm late on this since my Cocoon time is currently
> devoted to reviewing a book written by people named... Carsten and
> Matthew ;-)
Cool.
> - more tests and examples on the flowmap. Seems to me that this
> strategic stuff has been a set a bit aside due to lack of time.
>
> Entering beta state would then allow more people to test this baby !
But would slow us down in development and since we need to develop
rather than to do bugfixes, I don't like this.
My issues are:
1) the flowmap/sitemap connection semantics are bad. I don't like them.
We need to do something more aggressive on this realm. NOTE: we'll have
to change the version of the sitemap namespace in 2.1, but still be back
compatible with 2.0.x
2) finish the design of blocks
Thursday I spent a day with Giacomo talking about the above two points
(I did consulting in Zurich this week). I'll write extensive RT tomorrow
or the next day about what we achieved.
I'm happy to state that we were finally able to provide a solution for
all the problems with had on the table, expecially about sitemap/flowmap
integration and about block polymorphism.
I don't want to enter beta state until we have finished discussing such
important design issues.
Hope you understand my points.
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<st...@apache.org> Friedrich Nietzsche
--------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: Planning the releases
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Vadim Gritsenko wrote:
>
> > From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de]
> >
> >
> > Vadim Gritsenko wrote:
> > >
> > > <snip/>
> > > This is the most discussed issue on the user list, it must be fixed
> > > before release. Can we have now Excalibur which works with 1.3 *and*
> > > 1.4?
> > >
> > What is needed for it?
> >
> > The current excalibur is compiled with jdk 1.4
> > in 1.2 compatible mode. For me this works on JDK 1.4 and 1.3 without
> > problems.
>
> You mean JDBC pool works ok now? Cool then.
>
Ehhmmm, ok, I didn't check if the JDBC pool works... but I just tested it
and yes, it's not working with jdk1.4 but with jdk1.3.... :(
> Vadim
>
>
> > 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 releases
Posted by Vadim Gritsenko <va...@verizon.net>.
> From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de]
>
>
> Vadim Gritsenko wrote:
> >
> > <snip/>
> > This is the most discussed issue on the user list, it must be fixed
> > before release. Can we have now Excalibur which works with 1.3 *and*
> > 1.4?
> >
> What is needed for it?
>
> The current excalibur is compiled with jdk 1.4
> in 1.2 compatible mode. For me this works on JDK 1.4 and 1.3 without
> problems.
You mean JDBC pool works ok now? Cool then.
Vadim
> Carsten
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: Planning the releases
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Vadim Gritsenko wrote:
>
> <snip/>
> This is the most discussed issue on the user list, it must be fixed
> before release. Can we have now Excalibur which works with 1.3 *and*
> 1.4?
>
What is needed for it?
The current excalibur is compiled with jdk 1.4
in 1.2 compatible mode. For me this works on JDK 1.4 and 1.3 without
problems.
Carsten
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: Planning the releases
Posted by Vadim Gritsenko <va...@verizon.net>.
> From: Sylvain Wallez [mailto:sylvain.wallez@anyware-tech.com]
>
> Nicola Ken Barozzi wrote:
>
> > Carsten Ziegeler wrote:
> >
> >> Hi Team,
> >>
> >> I think it's time to recall the "release early release often"
> >> paradigma...
> >>
> >> As others already mentioned over the last weeks, we should try to
> >> release a 2.0.3 as soon as possible. For this we should collect the
> >> open issues, do them and release (sounds simple, doesn't it?)
> >
> >
> > ;-)
> >
> > Major thing: make the distro working and tested on Jdk 1.3 *and*
1.4.
This is the most discussed issue on the user list, it must be fixed
before release. Can we have now Excalibur which works with 1.3 *and*
1.4?
> > I haven't looked in the linkstatus 1.2 problem yet, lack of time :-/
> > What was the code snippet that was giving problems with 1.2?
> >
> >> As I'm next week on vacation near Paris :) what do you think of
> >> the 1st of July as a release date for 2.0.3?
> >
> >
> > +1
+1 provided issue above is solved.
> +1 also. Want a french guide for your vacation ? ;)
>
> >> And if we are already talking about releases, what do we have to do
> >> for 2.1? It seems that many things are nearly finished, so we can
> >> start to think of a beta phase. I would propose the 15th of July
for
> >> the release date of 2.1 beta 1.
> >
> > +0
+0. I have not had a chance to review new interfaces/syntax additions.
After Cocoon goes beta, it won't be possible to make any changes. Hope
will have time for this till July 15th.
> >> What do you think?
> >
> >
> > I think that 2.1 features are all the ones we have now in CVS,
bsically.
> > We need to :
> > - apply patches
> > - test flowmap + docs + etc
> > - documentation to forrest format
> > - finish example refactoring
> > - finish to move scratchpad stuff in main trunk
> >
>
> Some more issues/todo for 2.1 :
> - switch to Avalon Source everywhere (is it already done ?)
> - switch to LogEnabled
> - I have to write the extended sitemap variable substitution, i.e.
> {request:foo}. I'm late on this since my Cocoon time is currently
> devoted to reviewing a book written by people named... Carsten and
> Matthew ;-)
> - more tests and examples on the flowmap. Seems to me that this
> strategic stuff has been a set a bit aside due to lack of time.
+1.
Vadim
> Entering beta state would then allow more people to test this baby !
>
> Sylvain
>
> --
> Sylvain Wallez
> Anyware Technologies Apache Cocoon
> http://www.anyware-tech.com mailto:sylvain@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 releases
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Sylvain Wallez wrote:
> >
> >> As I'm next week on vacation near Paris :) what do you think of
> >> the 1st of July as a release date for 2.0.3?
> >
> >
> > +1
>
>
> +1 also. Want a french guide for your vacation ? ;)
>
Oui, je comprends peu francais...but a french guide (who's also paying),
well, why not :)
> >> And if we are already talking about releases, what do we have to do
> >> for 2.1? It seems that many things are nearly finished, so we can
> >> start to think of a beta phase. I would propose the 15th of July for
> >> the release date of 2.1 beta 1.
> >
> >
> > +0
> >
> >> What do you think?
> >
> >
> > I think that 2.1 features are all the ones we have now in CVS, bsically.
> > We need to :
> > - apply patches
> > - test flowmap + docs + etc
> > - documentation to forrest format
> > - finish example refactoring
> > - finish to move scratchpad stuff in main trunk
> >
>
> Some more issues/todo for 2.1 :
> - switch to Avalon Source everywhere (is it already done ?)
No, there are a few places, but with my last updates to the excalibur
source interface (adding getLastModified() ) we can switch everywhere
without problems now.
> - switch to LogEnabled
> - I have to write the extended sitemap variable substitution, i.e.
> {request:foo}. I'm late on this since my Cocoon time is currently
> devoted to reviewing a book written by people named... Carsten and
> Matthew ;-)
Tell us more about it :) (just a joke)
> - more tests and examples on the flowmap. Seems to me that this
> strategic stuff has been a set a bit aside due to lack of time.
>
> Entering beta state would then allow more people to test this baby !
Yupp!
Carsten
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: Planning the releases
Posted by Sylvain Wallez <sy...@anyware-tech.com>.
Nicola Ken Barozzi wrote:
>
> Carsten Ziegeler wrote:
>
>> Hi Team,
>>
>> I think it's time to recall the "release early release often"
>> paradigma...
>>
>> As others already mentioned over the last weeks, we should try to
>> release a 2.0.3 as soon as possible. For this we should collect the
>> open issues, do them and release (sounds simple, doesn't it?)
>
>
> ;-)
>
> Major thing: make the distro working and tested on Jdk 1.3 *and* 1.4.
> I haven't looked in the linkstatus 1.2 problem yet, lack of time :-/
> What was the code snippet that was giving problems with 1.2?
>
>> As I'm next week on vacation near Paris :) what do you think of
>> the 1st of July as a release date for 2.0.3?
>
>
> +1
+1 also. Want a french guide for your vacation ? ;)
>> And if we are already talking about releases, what do we have to do
>> for 2.1? It seems that many things are nearly finished, so we can
>> start to think of a beta phase. I would propose the 15th of July for
>> the release date of 2.1 beta 1.
>
>
> +0
>
>> What do you think?
>
>
> I think that 2.1 features are all the ones we have now in CVS, bsically.
> We need to :
> - apply patches
> - test flowmap + docs + etc
> - documentation to forrest format
> - finish example refactoring
> - finish to move scratchpad stuff in main trunk
>
Some more issues/todo for 2.1 :
- switch to Avalon Source everywhere (is it already done ?)
- switch to LogEnabled
- I have to write the extended sitemap variable substitution, i.e.
{request:foo}. I'm late on this since my Cocoon time is currently
devoted to reviewing a book written by people named... Carsten and
Matthew ;-)
- more tests and examples on the flowmap. Seems to me that this
strategic stuff has been a set a bit aside due to lack of time.
Entering beta state would then allow more people to test this baby !
Sylvain
--
Sylvain Wallez
Anyware Technologies Apache Cocoon
http://www.anyware-tech.com mailto:sylvain@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 releases
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Jens Lorenz wrote:
> From: "Carsten Ziegeler" <cz...@s-und-n.de>
>>The component uses the java.net.URL getPath() method which is not
>>available in 1.2.
>
>
> Which can be easily overcome by doing something like:
>
> java.net.URL url = ...;
> String path = url.getFile().substring(0,url.getFile().lastIndexOf('?'));
It seems that the path is not needed anyway, and I have a local fix, but
I'm having problems in making Cocoon work at all in Tomcat 4.1 now.
I'll commit ASAP, thanks :-)
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: Planning the releases
Posted by Jens Lorenz <je...@interface-projects.de>.
----- Original Message -----
From: "Carsten Ziegeler" <cz...@s-und-n.de>
To: <co...@xml.apache.org>
Sent: Wednesday, June 12, 2002 10:40 AM
Subject: RE: Planning the releases
>
> Nicola Ken Barozzi wrote:
> >
> > Carsten Ziegeler wrote:
> > > Hi Team,
> > >
> > > I think it's time to recall the "release early release often"
> > paradigma...
Yes, pleeeaaase. IMHO Cocoon 2.0.3 is a long time overdue ...
> > > As others already mentioned over the last weeks, we should try to
> > > release a 2.0.3 as soon as possible. For this we should collect the
> > > open issues, do them and release (sounds simple, doesn't it?)
> >
> > ;-)
> >
> > Major thing: make the distro working and tested on Jdk 1.3 *and* 1.4.
> > I haven't looked in the linkstatus 1.2 problem yet, lack of time :-/
> > What was the code snippet that was giving problems with 1.2?
> >
> The component uses the java.net.URL getPath() method which is not
> available in 1.2.
Which can be easily overcome by doing something like:
java.net.URL url = ...;
String path = url.getFile().substring(0,url.getFile().lastIndexOf('?'));
> >
> Thanks.
>
> Carsten
>
Regards,
Jens Lorenz
--
jens.lorenz at interface-projects dot de
interface:projects GmbH \\|//
Tolkewitzer Strasse 49 (o o)
01277 Dresden ~~~~oOOo~(_)~oOOo~~~~
Germany
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: Planning the releases
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Nicola Ken Barozzi wrote:
>
> Carsten Ziegeler wrote:
> > Hi Team,
> >
> > I think it's time to recall the "release early release often"
> paradigma...
> >
> > As others already mentioned over the last weeks, we should try to
> > release a 2.0.3 as soon as possible. For this we should collect the
> > open issues, do them and release (sounds simple, doesn't it?)
>
> ;-)
>
> Major thing: make the distro working and tested on Jdk 1.3 *and* 1.4.
> I haven't looked in the linkstatus 1.2 problem yet, lack of time :-/
> What was the code snippet that was giving problems with 1.2?
>
The component uses the java.net.URL getPath() method which is not
available in 1.2.
> > As I'm next week on vacation near Paris :) what do you think of
> > the 1st of July as a release date for 2.0.3?
>
> +1
>
> > And if we are already talking about releases, what do we have
> > to do for 2.1? It seems that many things are nearly finished, so
> > we can start to think of a beta phase. I would
> > propose the 15th of July for the release date of 2.1 beta 1.
>
> +0
>
>
> > What do you think?
>
> I think that 2.1 features are all the ones we have now in CVS, bsically.
> We need to :
> - apply patches
> - test flowmap + docs + etc
> - documentation to forrest format
> - finish example refactoring
> - finish to move scratchpad stuff in main trunk
>
Thanks.
Carsten
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: Planning the releases
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Carsten Ziegeler wrote:
> Hi Team,
>
> I think it's time to recall the "release early release often" paradigma...
>
> As others already mentioned over the last weeks, we should try to
> release a 2.0.3 as soon as possible. For this we should collect the
> open issues, do them and release (sounds simple, doesn't it?)
;-)
Major thing: make the distro working and tested on Jdk 1.3 *and* 1.4.
I haven't looked in the linkstatus 1.2 problem yet, lack of time :-/
What was the code snippet that was giving problems with 1.2?
> As I'm next week on vacation near Paris :) what do you think of
> the 1st of July as a release date for 2.0.3?
+1
> And if we are already talking about releases, what do we have
> to do for 2.1? It seems that many things are nearly finished, so
> we can start to think of a beta phase. I would
> propose the 15th of July for the release date of 2.1 beta 1.
+0
> What do you think?
I think that 2.1 features are all the ones we have now in CVS, bsically.
We need to :
- apply patches
- test flowmap + docs + etc
- documentation to forrest format
- finish example refactoring
- finish to move scratchpad stuff in main trunk
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: Planning the releases
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Ivelin Ivanov wrote:
>
> Are Cocoon blocks in or out from 2.1 ?
>
Currently they are out as (AFAIK) noone has started working on it.
But if someone is able to make a concept *and* implement it by
the 15th of July (or the release date of the beta 1) they can
be in.
Personally, I think we shouldn't add blocks to 2.1 to stick to our
"release early, release often" theme...
Carsten
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: Planning the releases
Posted by Ivelin Ivanov <iv...@apache.org>.
Carsten Ziegeler wrote:
> Hi Team,
>
> I think it's time to recall the "release early release often" paradigma...
>
> As others already mentioned over the last weeks, we should try to
> release a 2.0.3 as soon as possible. For this we should collect the
> open issues, do them and release (sounds simple, doesn't it?)
>
> As I'm next week on vacation near Paris :) what do you think of
> the 1st of July as a release date for 2.0.3?
>
> And if we are already talking about releases, what do we have
> to do for 2.1? It seems that many things are nearly finished, so
> we can start to think of a beta phase. I would
> propose the 15th of July for the release date of 2.1 beta 1.
+1
Are Cocoon blocks in or out from 2.1 ?
>
> What do you think?
> What are the open issues (for both releases)?
>
> Carsten
>
> Carsten Ziegeler Chief Architect Open Source Group, S&N AG
> ------------------------------------------------------------------
> Cocoon Consulting, Training and Projects
> ------------------------------------------------------------------
> mailto:cziegeler@s-und-n.de http://www.s-und-n.de
> http://ziegeler.bei.t-online.de
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
>
--
-= Ivelin =-
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org