[REF] openerp: move openerp to odoo

[eLBati]

After this commit
odoo/odoo@9e64f9f
I guess the recipe needs changes

[petrus-v]

Yes thanks for the reference! this will be for version 10.0!

@eLBati Do want to work on that one?

[gurneyalex]

see also odoo/odoo#13413

[eLBati]

Do want to work on that one?

@petrus-v
Do you mean working on this issue?
I am afraid I have not enough knowledge of the recipe at the moment.
Maybe you could give me some tips?

[petrus-v]

@eLBati,

Yes I was wondering if you started (or wanted) to work on it?

I'm not the king of the recipe too, I've done so few contribution... Anyway I guess this ticket will be mainly play with imports.

So @gracinet, @ccomb we have to decide is we create a new branch for version 10.0 or if we try/catch each import to support from version 8 to version 10 (or hack somehow to allow importing openerp on v10...)?

A brief of history for others contributors, Once upon a time the anybox.recipe.openerp was located on launchpad we move anybox.recipe.openerp to github about same time odoo moved on github. This repo is still maintains and expected to support openerp from [5.0 to 7.0] versions.

With odoo 8.0 the changing name of openerp we decide to create a new repo, this one anybox.recipe.odoo to support odoo 8.0 and greater.

Unfortunately it make things a bit confusing because anybox.recipe.odoo should almost works with openerp 7.0 we never really clean up the code.

As there is a lot of people getting confusing about what to use when and because a lot of people around odoo works with branches 7.0/8.0/9.0/master... I would suggest to close anybox.recipe.openerp and manage 1 branche per version like odoo! I know that makes some pros and cons! I'm wondering what you think about?

ps: @gracinet is off until the middle of September, he expects to release 1.9.2 by the end of the month, a beta version is already released: https://pypi.python.org/pypi/anybox.recipe.odoo/1.9.2b1

[gracinet]

Hi there, I'm back.

About version policy, the main distribution point for the recipe is PyPI, so that people can just reference it as recipe=anybox.buildbot.odoo:server without any option à la mrdeveloper or gp.vcsdevelop.

This implies that the versioning scheme is (mostly) PEP 440, instead of a branch per Odoo major version. And that's also why, historically, Odoo's name change was an opportunity to start afresh with no ties before version 8.

That being said, it's true that, installation-wise, the gap between 7 and 8 is not huge (all it takes IIRC is to protect calls to the new API). We did some cleanups in anybox.recipe.odoo, but these are mostly of the ugly hacks needed for OpenERP 6.0… 5.0 (urgh), were the risk was perceived as very low.
We should probably axe down more stuff, I'd certainly like to (after 1.9.2)