Re: the broken JCR locking

2017-04-05 Thread Angela Schreiber
Hi Julian Yes... trunk only... I don't think there will be an urgent request for backport... but I might be mistaken. As far as the existing broken impl is concerned: I don't have a strong opinion here. We could remove it to give room for a proper implementation... some times it's easier to

Re: the broken JCR locking

2017-04-05 Thread Julian Reschke
On 2017-04-05 15:34, Bertrand Delacretaz wrote: hi Angela, On Wed, Apr 5, 2017 at 3:18 PM, Angela Schreiber wrote: ...Does no reply mean that everyone agrees with the proposed steps? :-)... I missed it but as an Oak user +1 to the below suggestion, it makes things clear

Re: the broken JCR locking

2017-04-05 Thread Bertrand Delacretaz
hi Angela, On Wed, Apr 5, 2017 at 3:18 PM, Angela Schreiber wrote: > ...Does no reply mean that everyone agrees with the proposed steps? :-)... I missed it but as an Oak user +1 to the below suggestion, it makes things clear ;-) > On 22/03/17 10:35, "Angela Schreiber"

Re: the broken JCR locking

2017-04-05 Thread Angela Schreiber
Hi Does no reply mean that everyone agrees with the proposed steps? :-) Kind regards Angela On 22/03/17 10:35, "Angela Schreiber" wrote: >Hi Oak-Devs > >I just had another discussion with a colleague of mine asking why JCR >locking is not properly implemented in Oak.