Re: Intent to backport to 1.6 and 1.4: OAK-5741

2017-05-22 Thread Julian Reschke 

On 2017-05-22 10:26, Michael Dürig wrote:


Back to the list, which I unintentionally dropped.


On 22.05.17 10:19, Julian Reschke wrote:

On 2017-05-22 10:16, Michael Dürig wrote:


AFIK this is a new feature, why are we backporting this?

Michael


Because OAK-5704 relies on it.


But why should we backport that on? It is a minor improvement. Unless 
there is a strong reason to do otherwise we should only backport bugs.

...


Why should we backport OAK-5704? It's a significant performance 
improvement, which, in some cases, can make the difference whether a 
VersionGC finishes within its time window or not.


That said, I disagree a *lot* with the statement:

"Unless there is a strong reason to do otherwise we should only backport 
bugs."


It's certainly not covered by what we discussed a few weeks ago and what 
led to 



Best regards, Julian

Re: Intent to backport to 1.6 and 1.4: OAK-5741

2017-05-22 Thread Michael Dürig 


Back to the list, which I unintentionally dropped.


On 22.05.17 10:19, Julian Reschke wrote:

On 2017-05-22 10:16, Michael Dürig wrote:


AFIK this is a new feature, why are we backporting this?

Michael


Because OAK-5704 relies on it.


But why should we backport that on? It is a minor improvement. Unless 
there is a strong reason to do otherwise we should only backport bugs.


Michael

Re: Intent to backport to 1.6 and 1.4: OAK-5741

2017-05-19 Thread Julian Reschke 

On 2017-05-19 09:13, Julian Reschke wrote:

On 2017-05-19 08:16, Chetan Mehrotra wrote:

On Thu, May 18, 2017 at 5:51 PM, Julian Reschke
 wrote:

(needed for a subsequent backport of OAK-5704)


Probably we should wait for OAK-5704 for sometime after 1.7.0 is cut
and that build is subjected some longevity testing before backporting
it to branched

Chetan Mehrotra


Marcel left me with the task to get it into the next cut of 1.4 before
going on PTO...

FWIW, we should have cut 1.7.0 months ago...


So,

- proposed date for 1.7.0 is IMHO early next week -- how long do we want 
to wait after that?


- trunk contains way more changes to Version Garbage Collection than 
those in OAK-5741 - so whatever testing of 1.7.0 reveals has limited 
applicability to what I intend to backport


While we're discussing, I'll start looking at the differences between 
1.6 and 1.4, which will have to be backported anyway.


Best regards, Julian

Re: Intent to backport to 1.6 and 1.4: OAK-5741

2017-05-19 Thread Julian Reschke 

On 2017-05-19 08:16, Chetan Mehrotra wrote:

On Thu, May 18, 2017 at 5:51 PM, Julian Reschke  wrote:

(needed for a subsequent backport of OAK-5704)


Probably we should wait for OAK-5704 for sometime after 1.7.0 is cut
and that build is subjected some longevity testing before backporting
it to branched

Chetan Mehrotra


Marcel left me with the task to get it into the next cut of 1.4 before 
going on PTO...


FWIW, we should have cut 1.7.0 months ago...

Re: Intent to backport to 1.6 and 1.4: OAK-5741

2017-05-19 Thread Chetan Mehrotra 
On Thu, May 18, 2017 at 5:51 PM, Julian Reschke  wrote:
> (needed for a subsequent backport of OAK-5704)

Probably we should wait for OAK-5704 for sometime after 1.7.0 is cut
and that build is subjected some longevity testing before backporting
it to branched

Chetan Mehrotra

Intent to backport to 1.6 and 1.4: OAK-5741

2017-05-18 Thread Julian Reschke 

https://issues.apache.org/jira/browse/OAK-5741

(needed for a subsequent backport of OAK-5704)