On Wed, 21 Nov 2001, Bernhard Huber wrote:

>
>
> Huber Bernhard, email: [EMAIL PROTECTED], homepage:
> members.a1.net/berni_huber/index.html
>
>
>
> > Thank you Bernhard for working on the Velocity documentation. I've
> > beenmeaning to send Carsten the patch this week like I promised,
> > but you beat
> > me to it!
> I didn't know that, didn't read your donation email closely...
> Perhaps you may add some examples? Examples helps other using
> the great VelocityGenerator.
> I have forgotten to add a link to the Veloctiy homepage, helps
> more using Velocity under Cocoon
> just suggestion... :)

Ehm... do we like people to use Velocity because of the
VelocityGenerator? Definitely not! It's the same with the JSPGenerator.
They are made to show people a smooth migration path over to Cocoon :)

Giacomo

> bye bernhard
>
> >
> > Regards,
> >
> > --mike
> >
> > On Wed, 21 Nov 2001, Bernhard Huber wrote:
> >
> > > Hi,
> > > some documentation about cinclude, and xinclude as it is frequentyl
> > > requested.
> > > and i copied from javadoc docu about velocity generator.
> > > docs are zipped up and attached
> > > bye bernhard
> > >
> > > David Crossley wrote:
> > >
> > > >Giacomo Pati wrote:
> > > >
> > > >>Quoting David Crossley <[EMAIL PROTECTED]>:
> > > >>
> > > >>>There are SIX DAYS TO GO until the agreed date for the
> > > >>>final release. We also agreed that the date should not slip.
> > > >>>
> > > >>>In my opinion, 2.0 is not yet fit for release. So there is only
> > > >>>one option ... hold the RT threads and get on with the job.
> > > >>>--David
> > > >>>
> > > >>What is it you think needs to be fixed before releaseing it?
> > > >>Giacomo
> > > >>
> > > >
> > > >** Documentation, documentation, documentation
> > > >- stop apologising for Cocoon 1
> > > >- positive announcement.xml and index.xml
> > > >- both of those docs need a concise overiew at top
> > > >(something less than half-a-page that convinces boss)
> > > >- much of the documentation is old and still talks about
> > > >Cocoon 1 configuration methods and issues
> > > >- much documentation still has "Under construction" notices
> > > >- people will turn away in droves
> > > >
> > > >** cocoon.xconf needs all parameters and components
> > > >listed and briefly explained as internal documentation
> > > >
> > > >** The excellent document "How to Develop Web Applications"
> > > >and the accompanying webapp.tutorial are missing from
> > > >the cocoon_20_branch
> > > >
> > > >** Better stylesheet for xml.apache.org/cocoon2/
> > > >- the slow response of the website will not allow 2.0 to
> > > >make its impact.
> > > >
> > > >Also the following issues are summarised at
> > > >documentation/xdocs/plan/release.xml ...
> > > >
> > > >** We have many open bugs in bugzilla
> > > >** Layout the distribution
> > > >** Ensure that licensing requirements have been met
> > > >** Decide what to backport from the 2.1 head
> > > >
> > > >--David
> > > >
> > > >>>--------------------------
> > > >>>
> > > >>>>Subject: [C2.0] Should we set a date for 2.0 Final Release?
> > > >>>>Date: Thu, 18 Oct 2001 14:55:15 +0200
> > > >>>>From: Martin Man <[EMAIL PROTECTED]>
> > > >>>>To: [EMAIL PROTECTED]
> > > >>>>
> > > >>>>Carsten Ziegeler wrote:
> > > >>>>
> > > >>>>>Ok, yes, I didnt check the calendar. Thanks for the hint!
> > > >>>>>
> > > >>>>>As I still prefer mondays, we should set the dates to
> > > >>>>>5th November: RC2
> > > >>>>>26th November: Final Release
> > > >>>>>
> > > >>>>yep, my +1 also for both dates, BTW: without looking to the
> > > >>>>repository, do we have actualized TODO list... I mean critical
> > > >>>>isuues (not including documentation) to fix ???
> > > >>>>
> > > >>>--------------------------
> > > >>>
> > > >>>>Date: Thu, 18 Oct 2001 14:37:57 +0200
> > > >>>>From: "Carsten Ziegeler" <[EMAIL PROTECTED]>
> > > >>>>To: <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>
> > > >>>>
> > > >>>>you're absolutely right. It's the same problem here.
> > > >>>>Due to the many changes I would propose a RC2.
> > > >>>>But we still need more documentation! So a good
> > > >>>>date could be 1st of November for the RC2 and
> > > >>>>end of november for the final release.
> > > >>>>
> > > >>>>But whatever date we decide on for the final
> > > >>>>release, we *should* stick to it.
> > > >>>>
> > > >>>>Carsten
> > > >>>>Open Source Group                        sunShine - b:Integrated
> > > >>>>================================================================
> > > >>>>Carsten Ziegeler, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
> > > >>>>www.sundn.de                          mailto: [EMAIL PROTECTED]
> > > >>>>================================================================
> > > >>>>
> > > >>>>Dims wrote:
> > > >>>>
> > > >>>>>Team,
> > > >>>>>Should we set a date for 2.0 Final Release? (or the next
> > Release> >>>>>Candidate)? Am a bit tired of
> > > >>>>>hearing from people (in my organization) that we cannot switch
> > > >>>>>from C1.X to C2.0 since it is in
> > > >>>>>Beta/RC Cycle....
> > > >>>>>
> > > >>>>>Thanks,
> > > >>>>>dims
> > > >>>>>=====
> > > >>>>>Davanum Srinivas - http://jguru.com/dims/
> > > >>>>>
> > > >>>
> > > >>>--------------------------------------------------------------
> > -------
> > > >>>To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > >>>For additional commands, email: [EMAIL PROTECTED]
> > > >>>
> > > >>>
> > > >>>
> > > >>
> > > >
> > > >----------------------------------------------------------------
> > -----
> > > >To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > >For additional commands, email: [EMAIL PROTECTED]
> > > >
> > > >
> > >
> > >
> > >
> >
> >
> > -------------------------------------------------------------------
> > --
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, email: [EMAIL PROTECTED]
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to