openerp-community team mailing list archive

[Pedro Manuel Baeza Romero <pedro.baeza@xxxxxxxxx>]

Hi, Raphael,

Very interesting the backports and the method you have used. We will look
every new feature (I only make for now an oversight) of WMS trunk to
possible backports, but as you have said, there are some areas that simply
cannot be backported. If we get enough funds - I don't want to repeat
myself too much, but we are doing this without any other customer support -
we will point definitely to use all the v8 potential (without forgetting
v7, as I said previously).

Regards.

2013/11/29 Raphael Valyi <rvalyi@xxxxxxxxx>

> On Fri, Nov 29, 2013 at 9:12 AM, Fabien Pinckaers <fp@xxxxxxxxxxx> wrote:
>
>>
>>
>> On 11/29/2013 11:51 AM, Nhomar Hernández wrote:
>> >
>> > @Fabien: I think it should be great if you share with us the specific
>> > branch in this thread where the new stock is landing please, to be sure
>> > everybody start with it from the same place.
>>
>>
>> http://bazaar.launchpad.net/~openerp-dev/openobject-addons/trunk-wms/revision/9418
>
>
> Hello,
>
> just a word: eventually we don't need to wait Q2 2014 (or later?) to start
> building upon the new things. A few things (only) are possible to backport
> on v7, that will make a smoother transition to v8 when it will be stable.
>
> For instance a project I'm working with should be in production by
> December 31th and it needs the concept of picking waves (that many already
> made similar modules but nothing OCA quality like).
> So instead of going unstable v8 or doing crap again on regular v7, I
> backported the picking wave module here:
> https://github.com/akretion/oe-addons-subtree-stock_picking_wave
>
> By using git and git-subtree (I will eventually post about the whole
> trick), we are able to properly keep in synch with the upstream branch
> without the need to have a folder with all the v8 modules to accommodate to
> the addons-path.
> So the extracted mirror of the trunk-wms is here:
> https://github.com/akretion/oe-addons-subtree-stock_picking_wave/tree/trunk-wms
> and the backported module is a branch of it
> https://github.com/akretion/oe-addons-subtree-stock_picking_wave/tree/backport-7.0
>
> I think OCA could assume working this way for specific module backports
> (if we need a new branch of all modules for every kind of backport, soon
> these branches are simply incompatible and we face an combinatorial
> explosion of unmanageable backports). I'm willing to help setting this up
> in case people are interested.
>
> Now, make no mistake, backporting the new stock quant system to v7 is out
> of question. I also extracted/backported purchase_requisition to v7 that I
> use in another project. And something we could backport to v7 is the saas2
> branch analytic_account module. Or eventually, as v8 isn't for now, we
> could start having a merge of saasX branches into OCB/RS-OCB. I started and
> I can tell the the merge is rather easy, so again I let OCA people bring
> the topic on the table again if they think it makes sense.
>
> That being said, I wish good luck to the funding, I also wish it base on
> V8 stock things as it fixes scalability issues that used to be one of the
> major OpenERP flaw, the kind of thing that was litteraly fueling
> sorryopenerp.com. This is very cool to see v8 finally bringing a lot of
> good work in the WMS area.
>
>
> Best Regards.
>
>
>
> --
> Raphaël Valyi
> Founder and consultant
> http://twitter.com/rvalyi <http://twitter.com/#!/rvalyi>
> +55 21 2516 2954
> www.akretion.com
>
>
>
>
> _______________________________________________
> 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
>
>