Hi, I'm totally agree with yours thoughts migration to 2.2 IMO it will cause many efforts to not enormous gain.
And what about C3 ? Myself I'm ambiguous on this point : A/ goods reasons - spring - cocoon block - restfull implementation - cool stuffs on SAX - monitoring - maven - wiket (that could help for improve the user experience) B/ bad reasons - many concepts and things to learn (c3, spring, bloc, maven,...) : not really bad thing (more and more apache's projects use them), but may discourage and lost some users/dev - (?very?) BIG development effort - not C3 stable release yet : however, this could be an opportunity to easily pushing some Cocoon level Lenya's requirements Don't hesitate to add yours goods and bads, as we can have a C3 for Lenya benchmark. One part of my body says : "Hey have to go", one other "Hooo calmos, keep cool" :) WDYT ? Have a good day. On Thu, 3 Jun 2010 12:45:47 +0200, Jürgen Ragaller <[email protected]> wrote: > Hi there > > > Am 03.06.2010 um 12:29 schrieb Andreas Hartmann: > > [...] > >> >> That's my CHF 0.02; maybe someone else has a different view, though. > > Not really ;-) - no, seriously thanks for sharing your thoughts! I fully > agree that the (jcr)-backend topic is more important than moving to cocoon > 2.2. > > What the community interest is concerned, here is my view: > I think some people were not participating in the effort because of lack > of interest but rather lack of knowledge about cocoon 2.2. and how to run > or understand what you have done so far in the 2.2 branch (at a quite high > pace) - that for shure was the case for myself. > > > Jürgen > > > > null-oder-eins GmbH Zürich > web & graphic design > > www.null-oder-eins.ch > > [email protected] > Skype: callto://ragaller > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
