Re: [DISCUSSION] Anticipate the end of life of the 13.07 branch and backport some non-bug related changes to the 14.12 and 15.12 branches

2016-06-29 Thread Sharan Foga
Hi Christian Thanks for pointing out something very, very important and I agree with you. I'm wondering if we still have a problem because even if we don't backport the Gradle or start changes, before we can release 14.12 we need to make changes to the way it handles external files (e.g the

Re: [DISCUSSION] Anticipate the end of life of the 13.07 branch and backport some non-bug related changes to the 14.12 and 15.12 branches

2016-06-29 Thread Jacopo Cappellato
On Wed, Jun 29, 2016 at 11:49 AM, Christian Geisert < christian.geis...@isu-gmbh.de> wrote: > ... > My proposal is to release 14.12 ASAP, after that dropping 13.07 and then > trying to do a release 16.x with Gradle. And a release of 15.12in > between wouldn't be bad either ;) > > Thank you

Re: [MARKETING] New Version of Updated OFBiz Logo

2016-06-29 Thread Hans Bakker
+1 https://cwiki.apache.org/confluence/download/attachments/30741803/ofbiz-logo.jpg?version=1=1355116616000=v2 with a (r) sign added to it. On 29/06/16 15:35, Jacques Le Roux wrote: Totally in tune with you Pierre. Jacques Le 29/06/2016 à 10:18, Pierre Smits a écrit : Julien, all, Your

Re: [DISCUSSION] Anticipate the end of life of the 13.07 branch and backport some non-bug related changes to the 14.12 and 15.12 branches

2016-06-29 Thread Michael Brohl
Thanks Christian, for this proposal. I think this would be the best way to go and protect all user who relied on the release branches as base of their projects. +1 Regards, Michael Brohl ecomify GmbH www.ecomify.de Am 29.06.16 um 11:49 schrieb Christian Geisert: While replacing Ant with

RE: Aw: Re: Memcached / central caching

2016-06-29 Thread Nick Rosser
3rd party -- if considered "best of breed" is always preferable, imo. It's the only thing they do so they normally become experts at it. Don't have an opinion as to which one would be considered the best-of-breed. Nick -Original Message- From: Pierre Smits

Re: [DISCUSSION] Anticipate the end of life of the 13.07 branch and backport some non-bug related changes to the 14.12 and 15.12 branches

2016-06-29 Thread gil portenseigne
+1 Gil On 29/06/2016 11:49, Christian Geisert wrote: While replacing Ant with Gradle sounds like a good plan, I don't think it's a good idea to backport these changes. Seriously, when implementing OFBiz at a customer the only sane choice is to use a release branch (even if there is no release

Fwd: [jira] Subscription: Patch Available in OFBiz

2016-06-29 Thread Pierre Smits
FYI, Pierre Smits ORRTIZ.COM OFBiz based solutions & services OFBiz Extensions Marketplace http://oem.ofbizci.net/oci-2/ -- Forwarded message -- From: Date: Fri, Jun 24, 2016 at 2:01 AM Subject: [jira] Subscription: Patch Available in

Re: [DISCUSSION] Anticipate the end of life of the 13.07 branch and backport some non-bug related changes to the 14.12 and 15.12 branches

2016-06-29 Thread Jacques Le Roux
Sounds wise to me, thanks Christian! Jacques Le 29/06/2016 à 11:49, Christian Geisert a écrit : While replacing Ant with Gradle sounds like a good plan, I don't think it's a good idea to backport these changes. Seriously, when implementing OFBiz at a customer the only sane choice is to use a

Re: [DISCUSSION] Anticipate the end of life of the 13.07 branch and backport some non-bug related changes to the 14.12 and 15.12 branches

2016-06-29 Thread Jacques Le Roux
Le 29/06/2016 à 10:39, Jacques Le Roux a écrit : Le 29/06/2016 à 08:33, Paul Piper a écrit : 1) release 14 to get away from 13 Agreed, I also proposed that before Mmm, I re-read it, I actually followed Pierre's proposition about dropping R14 with R13. Sincerely I have not a strong opinion

Re: [DISCUSSION] Anticipate the end of life of the 13.07 branch and backport some non-bug related changes to the 14.12 and 15.12 branches

2016-06-29 Thread Christian Geisert
While replacing Ant with Gradle sounds like a good plan, I don't think it's a good idea to backport these changes. Seriously, when implementing OFBiz at a customer the only sane choice is to use a release branch (even if there is no release yet). The point of a release is to have a stable

Re: [DISCUSSION] Anticipate the end of life of the 13.07 branch and backport some non-bug related changes to the 14.12 and 15.12 branches

2016-06-29 Thread Jacques Le Roux
Inline... Le 29/06/2016 à 08:33, Paul Piper a écrit : 1) release 14 to get away from 13 Agreed, I also proposed that before 2) use 15 for the gradle upgrade +1, seems that we will need to backport start component changes as explained Taher. Not a big deal, it's stable enough. 3) work

Re: [MARKETING] New Version of Updated OFBiz Logo

2016-06-29 Thread Jacques Le Roux
Totally in tune with you Pierre. Jacques Le 29/06/2016 à 10:18, Pierre Smits a écrit : Julien, all, Your questions deserve a split answer, so here goes: Re: Am I against a new logo. In short: no, but when we embarked on this endeavour back in May ( started with [1]), there were 2 options

Re: [MARKETING] New Version of Updated OFBiz Logo

2016-06-29 Thread Pierre Smits
Julien, all, Your questions deserve a split answer, so here goes: Re: Am I against a new logo. In short: no, but when we embarked on this endeavour back in May ( started with [1]), there were 2 options on the table. The majority of hose who voiced their thought opted for [2]. Now, when this

Re: [DISCUSSION] Anticipate the end of life of the 13.07 branch and backport some non-bug related changes to the 14.12 and 15.12 branches

2016-06-29 Thread Divesh Dutta
I agree with both the proposals. i.e : 1) Anticipate the end of life of the release branch 13.07 at now; we would not issue the fourth release as initially planned. 2) Once stabilized, backport to 14.12 and 15.12 all the changes required to build the system and download its dependencies with

Re: [DISCUSSION] Anticipate the end of life of the 13.07 branch and backport some non-bug related changes to the 14.12 and 15.12 branches

2016-06-29 Thread Taher Alkhateeb
Hey Folks, So again another light bulb just hit me. But instead of modifying the build script for the older releases we can just propagate all the changes that happened to the start component because nobody touches the start component that would make the backporting much easier to the older

Re: [DISCUSSION] Anticipate the end of life of the 13.07 branch and backport some non-bug related changes to the 14.12 and 15.12 branches

2016-06-29 Thread Taher Alkhateeb
Hi Folks, I'm sorry I completely forgot to mention this in this thread but after release 15 I think, I completely refactored the start component. This refactoring changed the logic and the syntax for OFBiz startup and server commands. This heavily affect the build system because it executes

Re: [MARKETING] New Version of Updated OFBiz Logo

2016-06-29 Thread Julien NICOLAS
Hi Pierre, Hans, Are you against a new logo or this is only because the proposal doesn't suit you ? Julien. On 29/06/2016 02:59, Hans Bakker wrote: +1 from me too. On 28/06/16 21:53, Pierre Smits wrote: +1 for this logo

Re: [DISCUSSION] Anticipate the end of life of the 13.07 branch and backport some non-bug related changes to the 14.12 and 15.12 branches

2016-06-29 Thread Sharan Foga
Hi Todd I think we'll need to wait for the outcome of this current discussion to understand what will happen to the various 'unreleased releases'. So in response to your question - the simple answer would be yes. Once this discussion is over, we'll know what sort of transition we are looking

Re: [DISCUSSION] Anticipate the end of life of the 13.07 branch and backport some non-bug related changes to the 14.12 and 15.12 branches

2016-06-29 Thread Paul Piper
I don't think that my argument is a selfish one, Jacques. An end-of-life with R13 is not my proposal, and neither are end of life of either 14 and 15. But given the current direction of this conversation I am convinced that a proper release plan is required and beneficial to all. The current

Re: Aw: Re: Memcached / central caching

2016-06-29 Thread Jacques Le Roux
Ah forgot, Moqui is using http://www.ehcache.org/ Le 29/06/2016 à 08:55, Jacques Le Roux a écrit : Thanks Leonard, So it could be indeed that DCC does not support this case well. It would be interesting to know why. Of course using something like memcached is certainly a good way and a

Re: Aw: Re: Memcached / central caching

2016-06-29 Thread Jacques Le Roux
Thanks Leonard, So it could be indeed that DCC does not support this case well. It would be interesting to know why. Of course using something like memcached is certainly a good way and a contribution would be quite welcome! Jacques Le 29/06/2016 à 08:33, Leonard Lin a écrit : Thanks for

Re: [DISCUSSION] Anticipate the end of life of the 13.07 branch and backport some non-bug related changes to the 14.12 and 15.12 branches

2016-06-29 Thread Jacques Le Roux
Hi Paul, I understand your concern, but seems to me that your answer is selfish. What about your comrades who have based their work on R13.07? They are in the same situation than you! OK this is kind of kidding, but see my point? ;) A last point I always want to mention is, IMO, it's always

Aw: Re: Memcached / central caching

2016-06-29 Thread Leonard Lin
Thanks for the input. I have to try to look at logs to see which entities/processes are the high cache clear flow. We are not using our ofbiz as an ecommerce system but as the manufacturing/fulfillment system. We do process a lot of orders and have also custom modules.     Gesendet: