Hi, This is a great news. Thanks you all for the the contribution. Perhaps, we can define as a GSOC task to make this code more generic. Something like migrating the default publication to the new lenya. It is just an idea. WDYT?
Best Regards, Antonio Gallardo. >> Richard Frovarp escribió: >>> I think that a colorized diff for the user to look at changes between >>> versions would be a great addition. >> +1. Sounds like a plan. :) >> >> Another idea, what about a migrator script from 1.2.x to 2.0.x? > > Thorsten, Felix, Josias and I implemented a content migration module > for the European Patent Office. We have the permission to commit it, > but it might not be completely generic and will probably need some > tweaking for individual migration scenarios. > > In the same project we implemented modules to execute batch workflow > operations. > > If nobody objects, I'll commit these modules. Shall I put them in the > sandbox or directly in the 2.0.x branch? They are feature-complete and > tested, from my POV the only question is if the migration module is > considered generic enough to be included in the distribution. > > -- Andreas > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
