cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vadim Gritsenko" <vadim.gritse...@verizon.net>
Subject RE: [C2]: Release Candidate 2
Date Thu, 01 Nov 2001 04:33:55 GMT
> -----Original Message-----
> From: Stefano Mazzocchi [mailto:stefano@apache.org]
> Sent: Wednesday, October 31, 2001 6:23 AM
> To: cocoon-dev@xml.apache.org
> Subject: Re: [C2]: Release Candidate 2
> 
> Sylvain Wallez wrote:
> >
> > Carsten Ziegeler a écrit :
> > >
> > > Hi Team,
> > >
> > > some days ago we decided to make the release candidate 2
> > > on next monday (5th of november).
> > >
> > > The question is now, what has to be done until then?
> > >
> > > 1) We have many open bugs in bugzilla. These must be reviewed
> > >    and then solved (or declared invalid etc).
> >
> > Going to nagoya to pick up some ;)
> >
> > > 2) Documentation updates (this area lacks most)
> > >    We could move this to the final release.
> >
> > Documentation is a must have to gain a lot of users, but it's a
> > non-final release that stops big companies from using Cocoon. So
let's
> > not delay the release because of docs.
> 
> Very good point. +1
> 
> Documentation is a must, I agree, but software stability is what many
> are looking for to even start looking at it. We will make docs better,
> but let's follow the release early and often practice a little bit
more
> ok? (it's *TWO* years we are working on Cocoon2, damn it!)
> 
> > > 3) Decide what to backport from the 2.1 head.
> > >    I'm +1 on removing the CodeFactories completly in 2.0, too.
> > >    This would avoid any backcompatibility problems.
> >
> > +1 also, along with the changes on Cocoon/Sitemap that turns it into
a
> > real component.
> 
> +1 as long as it doesn't change current behavior.
> 
> > > 4) Layout the distribution
> > >    This is a point we haven't discussed yet. Currently our
> > >    distribution is a mixture of a source and a binary one.
> > >    We deliver the source and a compiled version, but in order
> > >    to run Cocoon, the user has to build a war file.
> > >    I propose to split this: one source distribution which is
> > >    similar to the current one but without the precompiled
> > >    cocoon jar and a binary distribution containing only the
> > >    war file. This war file should work in most servlet engines,
> > >    perhaps not in all.
> 
> +1 for both solutions.
> 
> 1) the "ready to be deployed - almost-demo-app" (which, IMO, should
also
> contain the cocoon docs in the webapp since they are served by Cocoon
> anyway) packaged as a big WAR file.
> 
> 2) the normal distribution.
> 
> What do you think?

+1 for both. Also, people on user list expressed interest in having
option to download Cocoon bundled with servlet engine, say, Tomcat 4, so
you need only to download it and launch it out of the box. I do
understand that Cocoon is extremely simple to install (especially on
TC4), but we had lots of emails from users being unable to do so (IIRC
there were some classpath configuration problems).

Vadim



---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message