Re: Aw: Re: Memcached / central caching

[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 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: Montag, 27. Juni 2016 um 15:46 Uhr
Von: "Jacques Le Roux" 
An: user@ofbiz.apache.org
Betreff: Re: Memcached / central caching
I can confirm this behaviour (working well and better with more instances to 
support the growing load) for a configuration of 5 OFBiz machines against
a cluster of 3 Postgres machines (using PgPool II).

It was also for an ecommerce application for a major Internet provider. I then 
I wrote the wiki page about DCC. As say Nick, you may indeed have a
specific issue we did not cross...

Jacques


Le 27/06/2016 à 15:11, Nick Rosser a écrit :

Leonard,

We have clients using distributed cache -- we used ActiveMQ to synchronize any cache 
modifications from one server to the other(s). Worked very well -- and we saw a 
significant performance uptick when adding additional "slave" instances.

Our implementations are typically for eCommerce -- with minimal cache-clear 
events.

Which entities are subject to high volume cache-clear events for you? Perhaps 
you could consider removing caching for those entities?

Nick

-Original Message-
From: Leonard Lin [mailto:leonard@gmx.net]
Sent: Monday, June 27, 2016 6:24 AM
To: user@ofbiz.apache.org
Subject: Memcached / central caching

Hi,

I would like to ask if someone has already investigated or implemented an 
adapter for OFBiz to use a central caching system like memcached, redis or the 
like.

I know for OFBiz cluster setup there is the distributed cache clear mechanism.

I did use that in the past but have found that with more than 2 instances it 
impacts performance of OFBiz adversely.
Symptoms we started to see in production:
- We started to see long running transaction locks, General Entity operations 
slower (might be a combination of load and clustering)
- Other idle hosts were 5%-15% busy only to process the cache-clear events 
without doing anything else
- Especially with higher load, the whole thing becomes even slower

More load -> More cluster instances -> more cache clear events -> more cycles used to 
process cache mgmt. -> general requests/operations slower -> so we need even more instances 
-> you see where it’s going
That’s why I was thinking if someone has tried to integrate with a central 
cache.

For single host installation the local in-memory cache is surely faster, even 
perhaps with a 2host cluster setup, but with 3 or more hosts, I think a central 
cache might scale better.

Also interested to hear about any thoughts on the idea and architecture.

Otherwise, any pointers where in the code to look at would be appreciated.
I'm thinking to implement it as an adaptor/driver you can switch on if you want 
it.

Thanks
Best
Leo


  

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

[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 better to use a branch by directly connecting your work with svn than using a packaged 
version. So a compromise would be that instead of using the packaged release, people in your situation could consider connecting their work to svn at 
the point (revision) the package they use was created. They would then get the same situation but iwould be able to easier follow the work done by the 
community. We would then continue to backport in these branches, opinions?


Cheers

Jacques


Le 28/06/2016 à 22:58, Paul Piper a écrit :

Hi all,

Not releasing 14 wouldn't make sense to me. Skipping releases never looks
good, as it either means that there hasn't been enough contributions or that
there are no proper release strategies in place. Neither make the community
or the or the product look good to outsiders.

I can understand that one would want to drop support for 13, but i would
argue that at least 14 should be kept as it seems stable and could act as a
version that eases the transition to gradle. Then 15 would be 14 + gradle
support and 16 a proper new release.

The reason i argue for this is also that our client installations rely on
some sort of migration plan. Just calling end-of-life on a product and then
moving forwards is hell for them, as it practically means that they will
have to pay for a more stressful migration if they want to keep receiving
security bugfixes.

So i hope i can convince the rest of you to think this over.

Regards,
Paul




--
View this message in context: 
http://ofbiz.135035.n4.nabble.com/DISCUSSION-Anticipate-the-end-of-life-of-the-13-07-branch-and-backport-some-non-bug-related-changes-s-tp4686668p4686803.html
Sent from the OFBiz - User mailing list archive at Nabble.com.

Aw: Re: Memcached / central caching

[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: Montag, 27. Juni 2016 um 15:46 Uhr
Von: "Jacques Le Roux" 
An: user@ofbiz.apache.org
Betreff: Re: Memcached / central caching
I can confirm this behaviour (working well and better with more instances to 
support the growing load) for a configuration of 5 OFBiz machines against
a cluster of 3 Postgres machines (using PgPool II).

It was also for an ecommerce application for a major Internet provider. I then 
I wrote the wiki page about DCC. As say Nick, you may indeed have a
specific issue we did not cross...

Jacques


Le 27/06/2016 à 15:11, Nick Rosser a écrit :
> Leonard,
>
> We have clients using distributed cache -- we used ActiveMQ to synchronize 
> any cache modifications from one server to the other(s). Worked very well -- 
> and we saw a significant performance uptick when adding additional "slave" 
> instances.
>
> Our implementations are typically for eCommerce -- with minimal cache-clear 
> events.
>
> Which entities are subject to high volume cache-clear events for you? Perhaps 
> you could consider removing caching for those entities?
>
> Nick
>
> -Original Message-
> From: Leonard Lin [mailto:leonard@gmx.net]
> Sent: Monday, June 27, 2016 6:24 AM
> To: user@ofbiz.apache.org
> Subject: Memcached / central caching
>
> Hi,
>
> I would like to ask if someone has already investigated or implemented an 
> adapter for OFBiz to use a central caching system like memcached, redis or 
> the like.
>
> I know for OFBiz cluster setup there is the distributed cache clear mechanism.
>
> I did use that in the past but have found that with more than 2 instances it 
> impacts performance of OFBiz adversely.
> Symptoms we started to see in production:
> - We started to see long running transaction locks, General Entity operations 
> slower (might be a combination of load and clustering)
> - Other idle hosts were 5%-15% busy only to process the cache-clear events 
> without doing anything else
> - Especially with higher load, the whole thing becomes even slower
>
> More load -> More cluster instances -> more cache clear events -> more cycles 
> used to process cache mgmt. -> general requests/operations slower -> so we 
> need even more instances -> you see where it’s going
> That’s why I was thinking if someone has tried to integrate with a central 
> cache.
>
> For single host installation the local in-memory cache is surely faster, even 
> perhaps with a 2host cluster setup, but with 3 or more hosts, I think a 
> central cache might scale better.
>
> Also interested to hear about any thoughts on the idea and architecture.
>
> Otherwise, any pointers where in the code to look at would be appreciated.
> I'm thinking to implement it as an adaptor/driver you can switch on if you 
> want it.
>
> Thanks
> Best
> Leo
>
>
 

Re: [MARKETING] New Version of Updated OFBiz Logo

[Hans Bakker]

+1 from me too.

On 28/06/16 21:53, Pierre Smits wrote:

+1 for this logo
https://cwiki.apache.org/confluence/download/attachments/30741803/ofbiz-logo.jpg?version=1&modificationDate=1355116616000&api=v2
  with a (r) sign added to it.

Best regards,

Pierre SmitsRegards,


Hans Bakker
CEO, http://antwebsystems.com

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

[Paul Piper]

Hi all,

Not releasing 14 wouldn't make sense to me. Skipping releases never looks
good, as it either means that there hasn't been enough contributions or that
there are no proper release strategies in place. Neither make the community
or the or the product look good to outsiders. 

I can understand that one would want to drop support for 13, but i would
argue that at least 14 should be kept as it seems stable and could act as a
version that eases the transition to gradle. Then 15 would be 14 + gradle
support and 16 a proper new release. 

The reason i argue for this is also that our client installations rely on
some sort of migration plan. Just calling end-of-life on a product and then
moving forwards is hell for them, as it practically means that they will
have to pay for a more stressful migration if they want to keep receiving
security bugfixes. 

So i hope i can convince the rest of you to think this over. 

Regards,
Paul




--
View this message in context: 
http://ofbiz.135035.n4.nabble.com/DISCUSSION-Anticipate-the-end-of-life-of-the-13-07-branch-and-backport-some-non-bug-related-changes-s-tp4686668p4686803.html
Sent from the OFBiz - User mailing list archive at Nabble.com.

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

[Jacques Le Roux]

Hi Pierre,

This is not orthodox, but after being surprised by the idea of not releasing 
R14, I think it make as much sense as not releasing R13.

We could then focus entirely on R15 and I'd even ask if we could not backport 
the files moves, now only in trunk, to R15.
So we could then easily backport the changes in those files. It seems those moves went well, which is actually not surprising since apart typos we 
could not expect much issues.


Another possibility would be to soon freeze a R16 branch, once the Gradle use 
will have been validated for instance.

Opinions?

Jacques

Le 28/06/2016 à 20:09, Pierre Smits a écrit :

+1 on putting the r13.07 branch out to the pasture, and bring the focus
towards r15 branch to cut a release soon.

+1 on putting the r14 branch out to the pasture, and bring the focus
towards r15 branch to cut a release soon.

+1 on focusing on getting the release from r15 out ASAP

Best regards,

Pierre Smits

ORRTIZ.COM 
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

On Tue, Jun 28, 2016 at 7:32 PM, Todd Thorner 
wrote:


Thanks for this, Mr. Foga.  The Downloads page of the ofbiz.apache.org
site mentions 14.x and 15.x only as part of the project's tentative release
schedule.  Would end user newcomers be wise to wait out the transition?




On 16-06-28 09:55 AM, Sharan Foga wrote:


Thanks Jacopo for the details and summary.

I know that some people might think it a bit strange that this discussion
is happening on the user list rather than the dev list, but I think these
topics are something that our users may have an opinion on and want to
comment.

+1 for suggestion #1

13.07 has been around a while so I think that ending it now rather than
next year will help us to focus on other work (e.g. refactoring and clean
up)

+1 for suggestion #2

I think the work we are currently doing to improve the trunk build system
isn't really that visible to our users, but it will make a big difference
to developers and people who administer the system. Pushing those technical
benefits back to 14.12 and 15.12 (if we still want to call them that!) will
help.

Also OFBiz has changed a lot since the 14.12 and even 15.12 branches were
created. We've incorporated so much new functionality that it would be a
good thing to try and get some of this into our next release. Essentially
it would mean more functionality for our users.

Thanks
Sharan

On 2016-06-28 12:26 (+0200), Jacopo Cappellato <
jacopo.cappell...@hotwaxsystems.com> wrote:


Hi all,

as you may know we are working at migrating the build scripts of the
OFBiz
trunk from Ant to Gradle.
Together with this important change we are also modifying, for policy
reasons, the way we distribute the external dependencies (i.e., the jar
files needed by OFBiz): the required jars will be downloaded at build
time.
Since these changes are not bug fixes, the current plan is to do these
changes only in the trunk and do not backport them to the active
branches,
that are currently:

* 13.07
* 14.12
* 15.12

However, we will still have to modify these branches by removing the
external jar files and download them using Ivy.

The first concern is that we will have to work on and stabilize two
fronts:
Ivy for the 3 current release branches and Gradle for the trunk and the
future branches.
The second concern is that, as a consequence, we will have, for several
years, significant differences in the setup/build steps between the old
releases and the new ones that could cause confusion and regressions when
bugs are backported.

We have already issued 3 releases from the 13.07 branch and we have a
tentative plan to issue one more release around February 2017 that would
be
the last release of this series.
As regards 14.12 and 15.12 branches, no releases have been issued yet.

Based on these details I would like you to consider the following
decisions:

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 Gradle

Please express your opinion on each of them separately, since they are
independent (i.e., you could agree/disagree on the first/second/both).

Thanks,

Jacopo

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

[Pierre Smits]

+1 on putting the r13.07 branch out to the pasture, and bring the focus
towards r15 branch to cut a release soon.

+1 on putting the r14 branch out to the pasture, and bring the focus
towards r15 branch to cut a release soon.

+1 on focusing on getting the release from r15 out ASAP

Best regards,

Pierre Smits

ORRTIZ.COM 
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

On Tue, Jun 28, 2016 at 7:32 PM, Todd Thorner 
wrote:

> Thanks for this, Mr. Foga.  The Downloads page of the ofbiz.apache.org
> site mentions 14.x and 15.x only as part of the project's tentative release
> schedule.  Would end user newcomers be wise to wait out the transition?
>
>
>
>
> On 16-06-28 09:55 AM, Sharan Foga wrote:
>
>> Thanks Jacopo for the details and summary.
>>
>> I know that some people might think it a bit strange that this discussion
>> is happening on the user list rather than the dev list, but I think these
>> topics are something that our users may have an opinion on and want to
>> comment.
>>
>> +1 for suggestion #1
>>
>> 13.07 has been around a while so I think that ending it now rather than
>> next year will help us to focus on other work (e.g. refactoring and clean
>> up)
>>
>> +1 for suggestion #2
>>
>> I think the work we are currently doing to improve the trunk build system
>> isn't really that visible to our users, but it will make a big difference
>> to developers and people who administer the system. Pushing those technical
>> benefits back to 14.12 and 15.12 (if we still want to call them that!) will
>> help.
>>
>> Also OFBiz has changed a lot since the 14.12 and even 15.12 branches were
>> created. We've incorporated so much new functionality that it would be a
>> good thing to try and get some of this into our next release. Essentially
>> it would mean more functionality for our users.
>>
>> Thanks
>> Sharan
>>
>> On 2016-06-28 12:26 (+0200), Jacopo Cappellato <
>> jacopo.cappell...@hotwaxsystems.com> wrote:
>>
>>> Hi all,
>>>
>>> as you may know we are working at migrating the build scripts of the
>>> OFBiz
>>> trunk from Ant to Gradle.
>>> Together with this important change we are also modifying, for policy
>>> reasons, the way we distribute the external dependencies (i.e., the jar
>>> files needed by OFBiz): the required jars will be downloaded at build
>>> time.
>>> Since these changes are not bug fixes, the current plan is to do these
>>> changes only in the trunk and do not backport them to the active
>>> branches,
>>> that are currently:
>>>
>>> * 13.07
>>> * 14.12
>>> * 15.12
>>>
>>> However, we will still have to modify these branches by removing the
>>> external jar files and download them using Ivy.
>>>
>>> The first concern is that we will have to work on and stabilize two
>>> fronts:
>>> Ivy for the 3 current release branches and Gradle for the trunk and the
>>> future branches.
>>> The second concern is that, as a consequence, we will have, for several
>>> years, significant differences in the setup/build steps between the old
>>> releases and the new ones that could cause confusion and regressions when
>>> bugs are backported.
>>>
>>> We have already issued 3 releases from the 13.07 branch and we have a
>>> tentative plan to issue one more release around February 2017 that would
>>> be
>>> the last release of this series.
>>> As regards 14.12 and 15.12 branches, no releases have been issued yet.
>>>
>>> Based on these details I would like you to consider the following
>>> decisions:
>>>
>>> 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 Gradle
>>>
>>> Please express your opinion on each of them separately, since they are
>>> independent (i.e., you could agree/disagree on the first/second/both).
>>>
>>> Thanks,
>>>
>>> Jacopo
>>>
>>>
>

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

[Todd Thorner]

Thanks for this, Mr. Foga.  The Downloads page of the ofbiz.apache.org 
site mentions 14.x and 15.x only as part of the project's tentative 
release schedule.  Would end user newcomers be wise to wait out the 
transition?




On 16-06-28 09:55 AM, Sharan Foga wrote:

Thanks Jacopo for the details and summary.

I know that some people might think it a bit strange that this discussion is 
happening on the user list rather than the dev list, but I think these topics 
are something that our users may have an opinion on and want to comment.

+1 for suggestion #1

13.07 has been around a while so I think that ending it now rather than next 
year will help us to focus on other work (e.g. refactoring and clean up)

+1 for suggestion #2

I think the work we are currently doing to improve the trunk build system isn't 
really that visible to our users, but it will make a big difference to 
developers and people who administer the system. Pushing those technical 
benefits back to 14.12 and 15.12 (if we still want to call them that!) will 
help.

Also OFBiz has changed a lot since the 14.12 and even 15.12 branches were 
created. We've incorporated so much new functionality that it would be a good 
thing to try and get some of this into our next release. Essentially it would 
mean more functionality for our users.

Thanks
Sharan

On 2016-06-28 12:26 (+0200), Jacopo Cappellato 
 wrote:

Hi all,

as you may know we are working at migrating the build scripts of the OFBiz
trunk from Ant to Gradle.
Together with this important change we are also modifying, for policy
reasons, the way we distribute the external dependencies (i.e., the jar
files needed by OFBiz): the required jars will be downloaded at build time.
Since these changes are not bug fixes, the current plan is to do these
changes only in the trunk and do not backport them to the active branches,
that are currently:

* 13.07
* 14.12
* 15.12

However, we will still have to modify these branches by removing the
external jar files and download them using Ivy.

The first concern is that we will have to work on and stabilize two fronts:
Ivy for the 3 current release branches and Gradle for the trunk and the
future branches.
The second concern is that, as a consequence, we will have, for several
years, significant differences in the setup/build steps between the old
releases and the new ones that could cause confusion and regressions when
bugs are backported.

We have already issued 3 releases from the 13.07 branch and we have a
tentative plan to issue one more release around February 2017 that would be
the last release of this series.
As regards 14.12 and 15.12 branches, no releases have been issued yet.

Based on these details I would like you to consider the following decisions:

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 Gradle

Please express your opinion on each of them separately, since they are
independent (i.e., you could agree/disagree on the first/second/both).

Thanks,

Jacopo

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

[Sharan Foga]

Thanks Jacopo for the details and summary.

I know that some people might think it a bit strange that this discussion is 
happening on the user list rather than the dev list, but I think these topics 
are something that our users may have an opinion on and want to comment.

+1 for suggestion #1

13.07 has been around a while so I think that ending it now rather than next 
year will help us to focus on other work (e.g. refactoring and clean up)

+1 for suggestion #2

I think the work we are currently doing to improve the trunk build system isn't 
really that visible to our users, but it will make a big difference to 
developers and people who administer the system. Pushing those technical 
benefits back to 14.12 and 15.12 (if we still want to call them that!) will 
help.

Also OFBiz has changed a lot since the 14.12 and even 15.12 branches were 
created. We've incorporated so much new functionality that it would be a good 
thing to try and get some of this into our next release. Essentially it would 
mean more functionality for our users.

Thanks 
Sharan

On 2016-06-28 12:26 (+0200), Jacopo Cappellato 
 wrote: 
> Hi all,
> 
> as you may know we are working at migrating the build scripts of the OFBiz
> trunk from Ant to Gradle.
> Together with this important change we are also modifying, for policy
> reasons, the way we distribute the external dependencies (i.e., the jar
> files needed by OFBiz): the required jars will be downloaded at build time.
> Since these changes are not bug fixes, the current plan is to do these
> changes only in the trunk and do not backport them to the active branches,
> that are currently:
> 
> * 13.07
> * 14.12
> * 15.12
> 
> However, we will still have to modify these branches by removing the
> external jar files and download them using Ivy.
> 
> The first concern is that we will have to work on and stabilize two fronts:
> Ivy for the 3 current release branches and Gradle for the trunk and the
> future branches.
> The second concern is that, as a consequence, we will have, for several
> years, significant differences in the setup/build steps between the old
> releases and the new ones that could cause confusion and regressions when
> bugs are backported.
> 
> We have already issued 3 releases from the 13.07 branch and we have a
> tentative plan to issue one more release around February 2017 that would be
> the last release of this series.
> As regards 14.12 and 15.12 branches, no releases have been issued yet.
> 
> Based on these details I would like you to consider the following decisions:
> 
> 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 Gradle
> 
> Please express your opinion on each of them separately, since they are
> independent (i.e., you could agree/disagree on the first/second/both).
> 
> Thanks,
> 
> Jacopo
> 

Re: [MARKETING] New Version of Updated OFBiz Logo

[Pierre Smits]

+1 for this logo
https://cwiki.apache.org/confluence/download/attachments/30741803/ofbiz-logo.jpg?version=1&modificationDate=1355116616000&api=v2
 with a (r) sign added to it.

Best regards,

Pierre Smits

ORRTIZ.COM 
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

On Mon, Jun 27, 2016 at 11:24 AM, Sharan Foga  wrote:

> Hi Jacopo
>
> I agree and will make sure that it's included.
>
> Thanks
> Sharan
>
> On 2016-06-27 11:18 (+0200), Jacopo Cappellato <
> jacopo.cappell...@hotwaxsystems.com> wrote:
> > Thanks, they were good to me.
> > However I think we should use the name "Apache OFBiz" because this is the
> > official name that was registered.
> >
> > Jacopo
> >
> > On Mon, Jun 27, 2016 at 8:57 AM, Sharan Foga 
> wrote:
> >
> > > Hi  Everyone
> > >
> > > Thank you all very much for your feedback. As it seems to have been a
> > > little mixed, some liking the general idea and others not, I'll go
> back to
> > > Kenneth and we'll see what other options we can come up with.
> > >
> > > Thanks
> > > Sharan
> > >
> > > On 2016-06-23 17:16 (+0200), "Sharan Foga"
> wrote:
> > > > Hi Everyone
> > > >
> > > > I've got an example of a proposed updated OFBiz logo to share with
> > > everyone.
> > > >
> > > >
> > >
> https://cwiki.apache.org/confluence/download/attachments/61317052/OFBiz%20Logo.png?api=v2
> > > >
> > > > In fact there are two of them, one with the word Apache and one
> without.
> > > I've uploaded the sample logo here and it's the first one (i.e. the top
> > > line) with the white background that we are looking at.
> > > >
> > > > For those who recognise it \u2013 we've gone a bit retro and picked
> up
> > > this circle icon from the original OFBiz logo when the project first
> came
> > > to Apache. Instead of using the original blue colour, we've
> incorporated
> > > the same (orange, red and purple) colour scheme as the new Apache
> feather.
> > >   http://apache.org/
> > > >
> > > > We've also changed the OFBiz lettering to orange as it seemed to go
> well
> > > with the new Apache colours.
> > > >
> > > > For information we've also included some examples of what it would
> look
> > > like on different coloured backgrounds with white and black lettering.
> > > >
> > > > Anyway please take a look and let me have your comments and feedback.
> > > >
> > > > Thanks
> > > > Sharan
> > > >
> > >
> >
>

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

[Julien NICOLAS]

+1 for the first
+1 for the second

It's important to keep consistency between projects !

On 28/06/2016 12:26, Jacopo Cappellato wrote:

Hi all,

as you may know we are working at migrating the build scripts of the OFBiz
trunk from Ant to Gradle.
Together with this important change we are also modifying, for policy
reasons, the way we distribute the external dependencies (i.e., the jar
files needed by OFBiz): the required jars will be downloaded at build time.
Since these changes are not bug fixes, the current plan is to do these
changes only in the trunk and do not backport them to the active branches,
that are currently:

* 13.07
* 14.12
* 15.12

However, we will still have to modify these branches by removing the
external jar files and download them using Ivy.

The first concern is that we will have to work on and stabilize two fronts:
Ivy for the 3 current release branches and Gradle for the trunk and the
future branches.
The second concern is that, as a consequence, we will have, for several
years, significant differences in the setup/build steps between the old
releases and the new ones that could cause confusion and regressions when
bugs are backported.

We have already issued 3 releases from the 13.07 branch and we have a
tentative plan to issue one more release around February 2017 that would be
the last release of this series.
As regards 14.12 and 15.12 branches, no releases have been issued yet.

Based on these details I would like you to consider the following decisions:

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 Gradle

Please express your opinion on each of them separately, since they are
independent (i.e., you could agree/disagree on the first/second/both).

Thanks,

Jacopo

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

[Deepak Dixit]

Making perfect sense.

+1 for #1
+1 for #2

Thanks & Regards
--
Deepak Dixit
www.hotwaxsystems.com

On Tue, Jun 28, 2016 at 5:19 PM, Ashish Vijaywargiya <
ashish.vijaywarg...@hotwaxsystems.com> wrote:

> +1 for #1.
> +1 for #2.
>
> Thanks Jacopo for the detailed email. It is very helpful!
>
> Kind Regards
> Ashish Vijaywargiya
> HotWax Systems - est. 1997
>
> On Tue, Jun 28, 2016 at 3:56 PM, Jacopo Cappellato <
> jacopo.cappell...@hotwaxsystems.com> wrote:
>
> > Hi all,
> >
> > as you may know we are working at migrating the build scripts of the
> OFBiz
> > trunk from Ant to Gradle.
> > Together with this important change we are also modifying, for policy
> > reasons, the way we distribute the external dependencies (i.e., the jar
> > files needed by OFBiz): the required jars will be downloaded at build
> time.
> > Since these changes are not bug fixes, the current plan is to do these
> > changes only in the trunk and do not backport them to the active
> branches,
> > that are currently:
> >
> > * 13.07
> > * 14.12
> > * 15.12
> >
> > However, we will still have to modify these branches by removing the
> > external jar files and download them using Ivy.
> >
> > The first concern is that we will have to work on and stabilize two
> fronts:
> > Ivy for the 3 current release branches and Gradle for the trunk and the
> > future branches.
> > The second concern is that, as a consequence, we will have, for several
> > years, significant differences in the setup/build steps between the old
> > releases and the new ones that could cause confusion and regressions when
> > bugs are backported.
> >
> > We have already issued 3 releases from the 13.07 branch and we have a
> > tentative plan to issue one more release around February 2017 that would
> be
> > the last release of this series.
> > As regards 14.12 and 15.12 branches, no releases have been issued yet.
> >
> > Based on these details I would like you to consider the following
> > decisions:
> >
> > 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 Gradle
> >
> > Please express your opinion on each of them separately, since they are
> > independent (i.e., you could agree/disagree on the first/second/both).
> >
> > Thanks,
> >
> > Jacopo
> >
>

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

[Ashish Vijaywargiya]

+1 for #1.
+1 for #2.

Thanks Jacopo for the detailed email. It is very helpful!

Kind Regards
Ashish Vijaywargiya
HotWax Systems - est. 1997

On Tue, Jun 28, 2016 at 3:56 PM, Jacopo Cappellato <
jacopo.cappell...@hotwaxsystems.com> wrote:

> Hi all,
>
> as you may know we are working at migrating the build scripts of the OFBiz
> trunk from Ant to Gradle.
> Together with this important change we are also modifying, for policy
> reasons, the way we distribute the external dependencies (i.e., the jar
> files needed by OFBiz): the required jars will be downloaded at build time.
> Since these changes are not bug fixes, the current plan is to do these
> changes only in the trunk and do not backport them to the active branches,
> that are currently:
>
> * 13.07
> * 14.12
> * 15.12
>
> However, we will still have to modify these branches by removing the
> external jar files and download them using Ivy.
>
> The first concern is that we will have to work on and stabilize two fronts:
> Ivy for the 3 current release branches and Gradle for the trunk and the
> future branches.
> The second concern is that, as a consequence, we will have, for several
> years, significant differences in the setup/build steps between the old
> releases and the new ones that could cause confusion and regressions when
> bugs are backported.
>
> We have already issued 3 releases from the 13.07 branch and we have a
> tentative plan to issue one more release around February 2017 that would be
> the last release of this series.
> As regards 14.12 and 15.12 branches, no releases have been issued yet.
>
> Based on these details I would like you to consider the following
> decisions:
>
> 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 Gradle
>
> Please express your opinion on each of them separately, since they are
> independent (i.e., you could agree/disagree on the first/second/both).
>
> Thanks,
>
> Jacopo
>

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

[Pranay Pandey]

Hi Jacopo,

Making perfect sense to move this way-
+1 for #1
+1 for #2 as well.


Best regards,

Pranay Pandey
HotWax Systems
http://www.hotwaxsystems.com/

On Tue, Jun 28, 2016 at 3:56 PM, Jacopo Cappellato <
jacopo.cappell...@hotwaxsystems.com> wrote:

> Hi all,
>
> as you may know we are working at migrating the build scripts of the OFBiz
> trunk from Ant to Gradle.
> Together with this important change we are also modifying, for policy
> reasons, the way we distribute the external dependencies (i.e., the jar
> files needed by OFBiz): the required jars will be downloaded at build time.
> Since these changes are not bug fixes, the current plan is to do these
> changes only in the trunk and do not backport them to the active branches,
> that are currently:
>
> * 13.07
> * 14.12
> * 15.12
>
> However, we will still have to modify these branches by removing the
> external jar files and download them using Ivy.
>
> The first concern is that we will have to work on and stabilize two fronts:
> Ivy for the 3 current release branches and Gradle for the trunk and the
> future branches.
> The second concern is that, as a consequence, we will have, for several
> years, significant differences in the setup/build steps between the old
> releases and the new ones that could cause confusion and regressions when
> bugs are backported.
>
> We have already issued 3 releases from the 13.07 branch and we have a
> tentative plan to issue one more release around February 2017 that would be
> the last release of this series.
> As regards 14.12 and 15.12 branches, no releases have been issued yet.
>
> Based on these details I would like you to consider the following
> decisions:
>
> 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 Gradle
>
> Please express your opinion on each of them separately, since they are
> independent (i.e., you could agree/disagree on the first/second/both).
>
> Thanks,
>
> Jacopo
>

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

[Jacques Le Roux]

Thanks Jacopo for the thorough explanation.

I totally agree, R13.07 was born dead anyway and it will be less work to 
backport.

I think though that we should release R14.12 ASAP in replacement of R13.07. 
It's already waiting for 1.5 year...

+1 for the idea!

Jacques



Le 28/06/2016 à 13:07, Taher Alkhateeb a écrit :

Hi Jacopo,

+1 for the first suggestion
+1 for the second suggestion

Although it is a bit more difficult to implement, it is beneficial on the
long run because it means a unified build system for all supported OFBiz
versions AND you also solve the ASF jar license issue. So strike two birds
with one stone

Cheers,

Taher Alkhateeb

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

[Taher Alkhateeb]

Hi Jacopo,

+1 for the first suggestion
+1 for the second suggestion

Although it is a bit more difficult to implement, it is beneficial on the
long run because it means a unified build system for all supported OFBiz
versions AND you also solve the ASF jar license issue. So strike two birds
with one stone

Cheers,

Taher Alkhateeb

[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

[Jacopo Cappellato]

Hi all,

as you may know we are working at migrating the build scripts of the OFBiz
trunk from Ant to Gradle.
Together with this important change we are also modifying, for policy
reasons, the way we distribute the external dependencies (i.e., the jar
files needed by OFBiz): the required jars will be downloaded at build time.
Since these changes are not bug fixes, the current plan is to do these
changes only in the trunk and do not backport them to the active branches,
that are currently:

* 13.07
* 14.12
* 15.12

However, we will still have to modify these branches by removing the
external jar files and download them using Ivy.

The first concern is that we will have to work on and stabilize two fronts:
Ivy for the 3 current release branches and Gradle for the trunk and the
future branches.
The second concern is that, as a consequence, we will have, for several
years, significant differences in the setup/build steps between the old
releases and the new ones that could cause confusion and regressions when
bugs are backported.

We have already issued 3 releases from the 13.07 branch and we have a
tentative plan to issue one more release around February 2017 that would be
the last release of this series.
As regards 14.12 and 15.12 branches, no releases have been issued yet.

Based on these details I would like you to consider the following decisions:

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 Gradle

Please express your opinion on each of them separately, since they are
independent (i.e., you could agree/disagree on the first/second/both).

Thanks,

Jacopo