openerp-community team mailing list archive

[Raphael Valyi <rvalyi@xxxxxxxxx>]

Hello Stefan

Then eventually, in a pure Launchpad scenario, may be the easiest would be
have an automated replica of OCB v7 back into the main official project
(using automatic replay script that won't fail because it's just a replica
of OCB v7).

And then we could merge both from that OCB v7 replica in official project
AND from official v8. Merging from branches both inside the same official
project would make merging possible. If sticking to Launchpad I have the
intuition that this 2 step process would be easier to manage than trying to
mix replay from OCB v7 along with merge conflicts in just one step.

Alternatively, we could have an official v8 replica into the OCB project.
Again the idea is just to have a transparent 2 steps process instead of
just 1 step with both replay and merge.

Eventually people open to make the whole thing on Github can start explore
how feasible that would be. We could have a sprint about that during the
community days, but I'm afraid we should probably take action before about
future v8 (even if going trunk right now is probably suicidal outside from
OpenERP SA as Fabien himself mentioned).
Again, Github has the advantage of being project agnostic and merging
efficiently again no matter what. Had we OCB i18n, we would mirror a Github
branch on LP, get it translated via Rosetta and merge it back to the git
branch daily automatically, not a big deal either.

I know I'm a bit obsessed by that Github move. It's just that I know we
won't die by Launchpad because bzr/LP are dying. Eventually, the sooner we
make the move, the sooner we enjoy a decent productivity again even for
people without fiber Internet. And OCB can make the move letting OpenERP SA
move later at its own pace, we will eventually be able to upstream just as
efficiently as today (in any the case the bottleneck is not the upstreaming
process, but it's the merge of community upstream by OpenERP SA which is
still leaving hundreds of merge proposals un-reviewed).

Regards.

-- 
Raphaël Valyi
Founder and consultant
http://twitter.com/rvalyi <http://twitter.com/#!/rvalyi>
+55 21 2516 2954
www.akretion.com




On Tue, Feb 25, 2014 at 6:13 AM, Stefan <stefan@xxxxxxxx> wrote:

> On 02/25/2014 12:43 AM, Raphael Valyi wrote:
> > Hello Pedro,
> >
> > I think the easiest is to merge official v8 into OCB in a v8 OCB serie
> > branched from the current v7 OCB.
> >
>
> Hi,
>
> the most transparent process IMHO would be to move the OCB series to the
> upstream projects to do away with the branch duplication. Start out with
> a copy of OpenERP 8.0 and have a custom replay process play all the
> specific changes to OCB 7.0 atomically on OCB 8.0 for traceability. The
> few conflicting branches should be revised manually.
>
> That way we ease the maintenance work on OCB and lower the barrier to
> contribute without raising another barrier by moving to a different
> platform than upstream OpenERP. But we would have to ask Olivier Dony if
> we can have project series for OCB 8.0 on the official projects.
>
> Olivier, can we?
>
> Cheers,
> Stefan.
>
> --
> Therp - Maatwerk in open ontwikkeling
>
> Stefan Rijnhart - Ontwerp en implementatie
>
> mail: stefan@xxxxxxxx
> tel: +31 (0) 614478606
> web: http://therp.nl
>
>
> _______________________________________________
> 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
>