Community mailing list archives
Re: Version 10 ODOOby
ADINS sprl, Christophe HANON
I am not talking about replacing anything,
We know the story, the scripts were released in the past - so does Tryton btw. And were as much as possible modular.... so is open-upgrade.
What I regret is that energy is lost for writing scripts that already exist....
I know that migration will never be 100% automated, but anythng that can minimize the pain is welcome as it is usually a pain to sell to customers.
On Mon, Jul 11, 2016 at 12:12 PM, Dominique Chabord <firstname.lastname@example.org> wrote:
2016-07-11 11:38 GMT+02:00 Christophe Hanon <email@example.com>: > In my opinion that is the deception point as far how the product is > managed... > > In the past migration scripts were released. Here we simply loose our time > reversing what is already done. The state-of-the-art solution is well known and proven on other projects: each component should take care of its own upgrade. Implementing it on Odoo would impact all core components. It has also an impact on the way addons are developed, in particular regarding inheritance. Therefore it is not going to happen on Odoo and we have to live with that weakness. TinyERP and OpenERP did not implement component based upgrade policy and faced themselves the difficulty to reverse-engineer migration scripts. Such scripts just never worked on general case. So you have to target a well known set of modules and address special cases by hand-crafting. This led to Odoo migration service offering as we know it today. OpenUpgrade is the way that has been chosen to stabilize upgrade procedures on a product and its unmanaged set of addons which have never been designed to be easily upgraded. Even if Odoo were publishing the scripts they use, it wouldn't replace OpenUpgrade. > > > Have a great day, > > > Christophe > >