Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Avatar

Re: The future of OCB

by
Tecnativa. S. L., Pedro M. Baeza
- 20/10/2016 08:59:01
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 <joel.grandguillaume@camptocamp.com>:
+1 if it is released

On Thu, Oct 20, 2016 at 8:37 AM, Stefan Rijnhart <stefan@opener.amsterdam> 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: stefan@opener.am
tel: +31 (0) 20 3090 139
web: https://opener.am

_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe




--


camptocamp
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

Joël Grand-Guillaume
Division Manager


_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe


Reference