Well in fact there are two aspects. The first is the implementator point of view and it is true, we do not migrate our customers at each release, at least not before we are sure the migration will not cause trouble, and we split the cost of testing between our customers.
But we are also provided a range of modules that are used by a lot of users. We have to provide functional versions of these modules that should alway been working with the last stable release, as there are no way to block a module for a release, so we have to ensure the transition of the modules. It is a question of serious. We can not do that now with the actual release policy. The certification will not ensure that the module will work between two minor or major release, and the API will just work. It just says that tiny will do himself the work to adapt the module to the new internal API and modules interactions. By certifying a module you partially (in a kind of way) loose the ownership of the module in favor of Tiny. Then you are not free to orient this module the way you wants. And as there are no real unit test set now, coherence between version is not guarantee. "The first to go here takes the arrows the other the earth" expression really fit the actual situation. I'm working with OpenERP since version 3 when it was still TinyERP and this release aspect has never really evolve till then. Each migration has always been a pain. I hope it will improve now. OpenERP is not anymore a little open source project and it has to adopt policies that fit the new state of the product. This with the serious a project of this size has to manage. Else the reputation product will suffer in middle term Greetings Nicolas ------------------------ Nicolas Bessi PSE A CH-1015 Lausanne www.camptocamp.com / www.cartoweb.org -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=42254#42254 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman2/listinfo/tinyerp-users
