openerp-community-reviewer team mailing list archive

[Joël Grand-Guillaume <joel.grandguillaume@xxxxxxxxxxxxxx>]

Dear Niels,


I think you may be misunderstood us there. We already making as you said: trying to push a fix by reporting it to the editor. This is done through LP bug report, merge proposal or through OPW depending on the case. If this not succeed for various reasons or take too much time, we do maintain our own branch of OpenERP and we merge all our suggested fix there. This branch is shared between our customers and maintained by our-self.

What is suggested by Stefan here (or this is what I understood) is to share between us all a branch of the official one that include all those fixes. All of them will refer to a bug report (and MP) on LP. This is a way to have branch that include all fixes that we (as a community) think are mandatory. Obviously, we will always report them to OpenERP and try to have them merge in the core ! Then, we'll merge it into ours.

What is true is that it'll take time and that was my point...vHope it clarify the subject here...

Regards,

Joël

Le 11 févr. 2013 à 13:58, Niels Huylebroeck <nh@xxxxxxxxxx> a écrit :

> 
> ...We at Agaplan take a different approach than your patch-make--private-branch: for each bug however small we file a bugreport and if appropriate create a branch with a fix (using the lowest version according to the DaggyFix principle). We then spend literally hours communicating with OpenERP to get each bug fixed by merging our branches. Some of these happen some are flat out rejected and others are re-invented in surprisingly identical ways... 
> 
> When they are fixed/merged we have contributed (by saving time) to the community for everyone to benefit because it is a validated and officially supported solution to the bug.
> ...
> In fact by asking the community to verify your branch for you, you are burdening the community with a lot more work which could've been avoided by communicating with OpenERP and tracking your own fixes in different branches.
> 
> And yes this is hard process, but compare the amount of work fighting individual issues against the huge branch you are now trying to slap on top of the official addons.
> We too have considered the "private-branch" approach and in fact we found a middle ground, for production installations we install a branch on which we apply our own merge requests if the customer requires a fix urgently, then when OpenERP finally accepts this branch we will never have any trouble re-doing a merge from the official addons.


--

Camptocamp
Innovative Solutions by Open Source Experts

Joël Grand-Guillaume
Division Manager - Business Solutions

www.camptocamp.com