Community mailing list archives

community@mail.odoo.com

Re: [Openerp-community] Use of new odoo API when porting OCA addons

by
Anubía, soluciones en la nube, S.L., Alejandro Santana
- 08/12/2014 03:53:51
+1 Raphael.

I would encourage to use new API in v8 (for those early adopters, specially), but do not force to do it.


--
Alejandro Santana
· · · · · · · · · · · · · · · · · · · · · · · · · · · · ·

ANUBÍA, soluciones en la nube, S.L.

Plaza Fernando Conde Montero Ríos, 9
36201, Vigo (Pontevedra)

www.anubia.es


anubía_logo_2014_i_o_140x140.pngodoo_logo_odoo_ready_140x140.png




2014-08-12 9:35 GMT+02:00 <stephane.bidoul@acsone.eu>:
Hello Nicolas,

In my opinion, there is no urgency to mandate porting existing modules to the new API.

In the short to medium term I see benefits to keeping modules compatible / similar between 7.0 and 8.0 branches.

Same argument for new modules that start their life on the 7.0 branch.

Best regards,

-sbi


On Tue, Aug 12, 2014 at 8:14 AM, Nicolas Bessi <nicolas.bessi@camptocamp.com> wrote:
Dear community,

In order to avoid multiple sterile debate on Github and unilateral commits,
community should define a new guideline about the usage of new API.
Should it be a prerequisite when proposing addons port or new addons on OCA project for v8 and above?

It would be nice if OCA board can organize a poll on this topic.

My two cents

Nicolas 

--
Nicolas Bessi
Senior ERP consultant
Business Solution technical manager

Camptocamp SA
PSE A
CH-1015 Lausanne

_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : openerp-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp


_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-59
Post to: mailto:community@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe