openerp-community team mailing list archive

[Nicolas Bessi <nicolas.bessi@xxxxxxxxxxxxxx>]

Hello,

Thanks for the HUGE work.

We will test the recipe carefully on various series of OpenERP/Odoo from
6.0 to 8.0

It is a nice idea to have support of version 8 both on
anybox.recipe.openerp and anybox.recipe.odoo.

If I correctly understand your words odoo recipe will goes along with
series 1.9.

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
deadline.

Keep up the good job and do not hesitate to ask if you need an hand.

Regards

Nicolas


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 properly.
>
> 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:
>
> [buildout]
> 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/~anybox/anybox.recipe.openerp/1.8#egg=aro-1.8vcs-update> = True
>
> [versions]
> # in some cases that's needed
> anybox.recipe.openerp =
>
>  (see also
> http://pythonhosted.org/anybox.recipe.openerp/contributing.html#using-a-development-version
> )
>
> To check that you are indeed on the correct version (assuming the part is
> called 'openerp'):
>
> bin/python_openerp
> >>> import anybox.recipe.openerp as aro
> >>> aro.__file_
>
>  Simplest Odoo 8 config:
>
> [odoo]
> recipe = anybox.recipe.openerp:server
> version = git http://github.com/odoo/odoo.git odoo master
>
> [versions]
> 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.
> anybox.recipe.odoo 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
> https://github.com/gracinet/a.r.odoo-testimport
>
> Sounds good ?
>
>
> Regards,
>
> --
> 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

Direct:   +41 21 619 10 26
Office:   +41 21 619 10 10