One of the solutions is to create brach on github, https://github.com/apache/ofbiz. A feature can be developed on Github and then a final patch can be submitted to Ofbiz Jira.
Regards Anil Patel On Jan 4, 2013, at 9:17 AM, Jacques Le Roux <[email protected]> wrote: > I was reading this article and suddenly thought: why not giving access to > branches in OFBiz project to people who need more than a patch to submit in a > Jira (clearly Tom and I would have loved that)? > http://prng.blogspot.fr/2009/02/commit-access-its-social-problem.html > > Opinions? > > Jacques > > From: "Jacques Le Roux" <[email protected]> >> Yes thanks! >> >> Jacques >> >> From: "Jacopo Cappellato" <[email protected]> >>> >>> On Dec 16, 2012, at 9:07 AM, Jacques Le Roux wrote: >>> >>>> I even wonder if Jacopo did not make a more recent (and flexible) >>>> proposition with which I totaly agreed (during fall, it seems to me but, I >>>> can't find it), Jacopo? >>> >>> Do you mean the following? >>> >>> ======================== >>> BTW, some time ago I also proposed an alternative path: see email with >>> subject "[PROPOSAL] from specialpurpose to extras": to that I can add that >>> we could provide two set of ant scripts, one similar to the one we have >>> that builds/tests everything (framework+applications+specialpurpose) and >>> one (the default) that only builds/tests the framework+applications; the >>> release branches may only contain the framework+applications and separate >>> releases of specialpurpose applications could be voted/released at >>> different time. This approach may reach two goals: >>> 1) slim down the "main" code that the community is more focused to >>> improve/maintain/release >>> 2) keep under the OFBiz community the ownership of all the other >>> specialpurpose components; if one of them will get more attention and >>> interest and could grow in quality or it is generic enough we could decide >>> to move it to the release branch (maybe move it to applications) >>> ======================== >>> >>> Jacopo >>> >>> >>
