On Tue, 2009-03-10 at 11:05 +0100, Jann Forrer wrote: > Felix Roethenbacher wrote: > > Hi Andreas ... > 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.
I am not sure about the automated update in lenya currently (reading about the spring cleaning), but I have been on a project with becompany.ch where we wrote a migration routine that was eliminating lots of work. Not sure whether becompany.ch can release it here but there are solutions that can help migrating from 1.2 to 2.0.x. > 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 ... That depends. I used cocoon 2.2 and had to change only minor things in my cocoon app. I have not tried lenya 2.2 but I think it should be possible to use your 2.0.x pub nearly as is. The move to spring is not forced you can still use your old Avalon components. However Andreas can comment better on this. > and if we move on to cocoon 3 again > migration .... Here we need still some experience to say something of value. > * > <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 .... ATM 2.2 needs to see some other eyes then the one from Andreas to see whether we want to go for it or not (as least this is what I understand from this mail). Before we have not decided to really go for it IMO there is no immediate need to inform the users. salu2 -- Thorsten Scherler <thorsten.at.apache.org> Open Source <consulting, training and solutions> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
