Felix Roethenbacher wrote: > Hi Andreas [ ... ] >> >> I share this opinion. I see good concepts but it is not yet the best >> practice approach. Further the development of 2.2 is a wee bit slower >> since Grzegorz (who took the lead in the dev) stop working on 2.2. >> >> Cocoon 3 is MAYBE the best choice, but IMO it makes sense to keep the >> trunk based on 2.2. up for a while. It would be very interesting to see >> how the performance has developed with using cocoon 2.2. >> IMO Cocoon 3 is far from being stable and recommendable for lenya. >> > > Cocoon 2.2 is THE big step for Lenya moving away from > Avalon to Spring and make use of the Maven build process. I assume > that the move from Cocoon 2.2 to Cocoon 3.0 won't be that much > work if our code is based already on the Spring Framework and Maven. > I see another problem and that is the *compatibility between different versions. We are still on lenya 1.2. Let's assume we would like to upgrade to lenya 2. That means we have to do a lot of work for migration. Now lenya moves to cocoon 2.2. If we would like to upgrade to this version that probably means again a lot of work in order to migrate our publications ... and if we move on to cocoon 3 again migration ....* <http://dict.leo.org/ende?lp=ende&p=thMx..&search=compatibility>
If we decide to move to cocoon 2.2 we should mention that on the website and at least inform current lenya user about the situation and what it means to them if they want to upgrade their installation e.g. wait with the upgrade until the migration to 2.2. is done .... >>>> Alternatively we can develop useful modules and publications to >>>> demonstrate >>>> the power of lenya to the public. >>> That would be very important in any case. >> +1 :-) Jann --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
