openerp-community team mailing list archive
Mailing list archive
Re: Buildout recipe nearing release, needs test, and odoo
On 06/10/2014 09:43 AM, Nicolas Bessi wrote:
> Thanks for the HUGE work.
Well, thanks for the kind words :-)
> We will test the recipe carefully on various series of OpenERP/Odoo
> from 6.0 to 8.0
I've not seen blocking bug reports so far, how did it go for you ?
> It is a nice idea to have support of version 8 both on
> anybox.recipe.openerp and anybox.recipe.odoo.
In general, I try and keep a balance between developer effort and user
comfort. In this case, I hope this decision will allow us to sweat a bit
less on the transition. I hope in the long run it won't become a
maintenance burden, but we'll see.
> If I correctly understand your words odoo recipe will goes along with
> series 1.9.
Yes, it'll start from there. That's what I did in my experimental github
repo anyway : bzr import, taking trunk as new master, then creation of
git branches for anybox.recipe.openerp from current trunk and 1.8
branches, allowing the new master to diverge from both, becoming
Now I'll see if it's easy to re-apply a commit from bzr to that.
> No problem to move to github for me, as the pypi eggs you provided
> will remain.
> We shall first wait OpenERP SA to release, before providing a fixed
> Keep up the good job and do not hesitate to ask if you need an hand.
I will ! Cheers,
> 2014-06-09 18:03 GMT+02:00 Georges Racinet <gracinet@xxxxxxxxx
> Hi there, back from the OpenDays, it's been a great experience,
> and I'm especially glad to have met so many of you in real life !
> This message summarizes the current status of
> anybox.recipe.openerp (for short, *a.r.openerp*), future plans for
> Odoo support (*a.r.odoo*), and asks for testing.
> We're open to suggestions, especially for the medium term plans.
> I'll be mostly offline until next monday, 2014-06-16
> a.r.openerp stable release
> We are very close to a 1.8.4 stable version, that'll handle Odoo
> Both bzr branches of the recipe are supposed to work for Github
> versions of
> - Odoo 8
> - OpenERP 7 (odoo repo, branch 7.0)
> or any fork of them, of course.
> (many thanks to the contributors that helped make this happen)
> This is a special time for assembly / packaging tools, so we'll
> try and do it the cautious way.
> If all goes well, release should happen during next week.
> Since it's called a "stable" branch, existing buildouts should run
> smoothly, so, please, give it a try in the context of your
> projects (whatever version of OpenERP or Odoo they use), and
> report any problems on launchpad. I'll look them up once I return.
> Preliminary tests look good, and anybox's buildbot is green, but
> that's never enough.
> Here's a sample config to use the stable (1.8) bzr branch:
> extensions = gp.vcsdevelop
> vcs-extend-develop = bzr+http://bazaar.launchpad.net/~anybox/anybox.recipe.openerp/1.8#egg=aro-1.8
> vcs-update <http://bazaar.launchpad.net/%7Eanybox/anybox.recipe.openerp/1.8#egg=aro-1.8vcs-update> = True
> # in some cases that's needed
> anybox.recipe.openerp =
> (see also
> To check that you are indeed on the correct version (assuming the
> part is called 'openerp'):
> >>> import anybox.recipe.openerp as aro
> >>> aro.__file_
> Simplest Odoo 8 config:
> recipe = anybox.recipe.openerp:server
> version = git http://github.com/odoo/odoo.git odoo master
> reportlab = 2.7
> There should not be a new development branch (1.10 or 2.0) after
> 1.9 (the current trunk) is declared stable.
> As I announced during my talk, there'll be a new recipe for Odoo,
> and we'll take the name change as an opportunity to drop backwards
> compatibility and remove all these nasty workarounds meant to
> support OpenERP from 5.0 onwards.
> So, a.r.odoo will support Odoo 8 and subsequent versions.
> To ease the transition, a.r.openerp should also support Odoo 8.
> If that becomes too much of work, we may change plans about that.
> As for version numbers, they'd start from 1.9.x
> Transition to Github (both recipes)
> So far our plans are to have a reference repository on Github,
> with three branches:
> - master: that's anybox.recipe.odoo, and the work starts from the
> current 1.9 branch of a.r.openerp
> - a.r.openerp-1.8, a.r.openerp-1.9 : current branches of
> anybox.recipe.openerp, imported from launchpad
> It's too early for a stable branch of a.r.odoo, we'll see about
> that later down the road.
> After 1.9 becomes the new stable, all development of a.r.openerp
> will stop on launchpad, in favor of the correct branch in Github.
> That should happen around the end of june. Do we need a precise
> deadline ?
> My current experiment to that effect is at
> Sounds good ?
> Georges Racinet
> Anybox SAS, http://anybox.fr
> Bureau: 09 72 39 50 97 / 09 72 39 13 06
> Portable: 06 51 32 07 27
> GPG: 0x33AB0A35, sur serveurs publics
> Mailing list: https://launchpad.net/~openerp-community
> Post to : openerp-community@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openerp-community
> More help : https://help.launchpad.net/ListHelp
> Nicolas Bessi
> Senior ERP consultant
> Business Solution technical manager
> Camptocamp SA
> PSE A
> CH-1015 Lausanne
> http://openerp.camptocamp.com <http://openerp.camptocamp.com/>
> Direct: +41 21 619 10 26
> Office: +41 21 619 10 10
Anybox SAS, http://anybox.fr
Bureau: 09 72 39 50 97 / 09 72 39 13 06
Portable: 06 51 32 07 27
GPG: 0x33AB0A35, sur serveurs publics