Community mailing list archives
RE: Should Odoo keep the old API for v10?by
I voted to make the old API to fully obsolete too.
Odoo still supported it on version 8 and 9; and I think its enough.
It will help the newcomer developer too, so they don’t need to learn again the old api.
Expert in Finance, Information System & Business Intelligence
Odoo Gold Partner
Tel. 13670137019 (China - Shenzhen)
From: Paul Catinean [mailto:email@example.com]
Sent: Tuesday, May 03, 2016 4:58 PM
To: Community <firstname.lastname@example.org>
Subject: Re: Should Odoo keep the old API for v10?
Thanks for polling the community on this, I think it's a very nice gesture to include the public opinion on this matter.
I submitted the survey and think it's a very good idea to deprecate the old API. OCA already enforces this for V9 to my knowledge and V10 is already the third version with the new API.
Migration should be done IMO with new API anyway and for people who want an upgrade and still keep old API there's V9. A small sacrifice for a greater benefit, just like Launchpad to Github. And the API move is way more gradual than the collaboration platform one.
My 2 cents,
On Tue, May 3, 2016 at 11:48 AM, Fabien Pinckaers <email@example.com> wrote:
In Odoo 10, all official modules should be ported to the new API.
So, we face the choice to remove the old API to clean the code and speed up the software, or keep it to help the community port old modules to v10.
If we keep the old API:
- it's easier to port community modules to v10, if they are not ported to the new API yet
If we remove the old API:
- Odoo will run about 10% faster
- Tracebacks are cleaner for developers (ORM code is lighter too)
Since it mostly impacts community modules, we'd like the community to vote here:
We will close the votes on monday 9 and share the results.
Can someone from the OCA relay this poll to OCA members? Since they contributed to a lot of modules, their vote matters.