Contributors mailing list archives
Re: The future of OCBby
Tecnativa. S. L., Pedro M. Baeza
I prefer to do that on other branch, or we will have the same possible incompatibilities than expressed in the OCX variant (DB layout changes, method signature changes...), but this time with the "excuse" that they're in the version N+1 of Odoo.Regards.
2016-10-20 8:53 GMT+02:00 Joël Grand-Guillaume <firstname.lastname@example.org>:
+1 if it is releasedOn Thu, Oct 20, 2016 at 8:37 AM, Stefan Rijnhart <email@example.com> wrote:On 19-10-16 20:23, Daniel Reis wrote: > Hello again, > > Does anyone support a policy change for OCB so that it allows back porting changes introduced in later Odoo versions? If it is released, yes. If it is in master and it is a big change, the result can be unpredictable because the change in master could still be refactored in an incompatible manner. Note, that when the data model is altered in the change, this affects the migration procedure. People with an Enterprise contract might not be able to use the migration service, and in OpenUpgrade care needs to be taken to maintain compatibility with both OCB and core Odoo. Regards, Stefan. -- Opener B.V. - Business solutions driven by open source collaboration Stefan Rijnhart - Consultant/developer mail: firstname.lastname@example.org tel: +31 (0) 20 3090 139 web: https://opener.am--