As ofbiz developers, we should all be aligned in providing upstream patches that fix bugs, etc.. to the ofbiz project.
It's in your interest to minimize the differences between your copy of ofbiz and the "official" one. You'll need to be clear about what is "specific" to your application vs core changes. Core changes should be submitted. This strategy just makes it easier for you to deal with the "patch latency" inherent in the ofbiz review-then-commit practise for non-committers. Marc Morin Emforium Group Inc. ALL-IN Software 519-772-6824 ext 201 [email protected] ----- "chris snow" <[email protected]> wrote: > Thanks for the tip Marc. If I have my own svn repository, there > doesn't > seem to be any value to me in providing upstream patches that may not > get > committed? > > On 15 May 2010 12:16, "Marc Morin" <[email protected]> wrote: > > For non committers, like ourselves. You must create your own svn > repository, with a vendor branch to the ofbiz repository. > > Then create your own branch of the raw trunk, to do your own local > changes. > Package up these changes into patches, and post them back to the > ofbiz > project.... they may or may not be accepted. > > But at least you can use your "private" modified version of ofbiz and > it > won't hold you up. > > Marc Morin > Emforium Group Inc. > ALL-IN Software > 519-772-6824 ext 201 > [email protected] > > > ----- "Chris Snow" <[email protected]> wrote: > > > If there is one patch per entity, only o...
