[Oak origin/trunk] Apache Jackrabbit Oak matrix - Build # 1237 - Still Failing

The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build #1237) Status: Still Failing Check console output at https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/1237/ to view the results. Changes: [reschke] OAK-4951: UpdateOp without set operation for _id:

[Oak origin/1.4] Apache Jackrabbit Oak matrix - Build # 1236 - Still Failing

The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build #1236) Status: Still Failing Check console output at https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/1236/ to view the results. Changes: [reschke] OAK-4988: JournalGarbageCollector: re-order method

How does having lot of ACL (for different principals) on a single node affect performance

Hi, In a project I'm working, we have a some personas which represent the kind of operations member of those personas are allowed to do over a given node. The most trivial idea was to have a synthetic-group-per-persona-per-such-node and add/remove members to these groups. This approach has

[Oak origin/trunk] Apache Jackrabbit Oak matrix - Build # 1235 - Still Failing

The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build #1235) Status: Still Failing Check console output at https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/1235/ to view the results. Changes: [tomekr] OAK-4970: Optimize the version copying performance

Re: segment-tar depending on oak-core

Wow, quite some replies :) See in-line, trying to replying to everyone in one email On 21/10/2016 13:08, Thomas Mueller wrote: > I would prefer if we get oak-segment-tar in line with the rest of oak > (release it at the same time and so on). I understand, there are some > disadvantages. But I

Re: segment-tar depending on oak-core

Sorry, my email client made a mess. Resending my text only On 24/10/16 13:48, "Michael Marth" wrote: >Hi Tommaso, > >I agree with your assessment that this discussion is actually about the >delivery granularity and user’s consumption of Oak. Taking the freedom to

Re: Oak 1.5.13 release plan

Done. Michael On 24.10.16 1:43 , Michael Dürig wrote: I would like to upgrade the dependency to Oak Segment Tar to 0.0.16. Give me an hour to try. Otherwise we bump it. Michael On 20.10.16 3:37 , Davide Giannella wrote: Hello team, I'm planning to cut Oak 1.5.13 on Monday 24th. If

Re: segment-tar depending on oak-core

Hi Tommaso, In my opinion what we're discussing is our view on how Oak should be architectured, either as a big (layered) blackbox or as a set of reusable (and interoperable) software components. The "release all at once with version x.y" approach sounds to me more inline with the former while

Re: Oak 1.5.13 release plan

I would like to upgrade the dependency to Oak Segment Tar to 0.0.16. Give me an hour to try. Otherwise we bump it. Michael On 20.10.16 3:37 , Davide Giannella wrote: Hello team, I'm planning to cut Oak 1.5.13 on Monday 24th. If there are any objections please let me know. Otherwise I

Re: Oak 1.5.13 release plan

On Mon, Oct 24, 2016 at 4:53 PM, Julian Reschke wrote: > Chetan: I see that you marked OAK-3036 as "blocker" for this release -- but > then, do we have a plan to resolve it in a timely manner? Missed that. Moved it to next release and would try get it resolved by that

Re: Oak 1.5.13 release plan

On 2016-10-20 15:37, Davide Giannella wrote: Hello team, I'm planning to cut Oak 1.5.13 on Monday 24th. If there are any objections please let me know. Otherwise I will re-schedule any non-resolved issue for the next iteration. Thanks Davide Chetan: I see that you marked OAK-3036 as

[Oak origin/trunk] Apache Jackrabbit Oak matrix - Build # 1234 - Failure

The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build #1234) Status: Failure Check console output at https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/1234/ to view the results. Changes: [amitj] OAK-4979: Caching sub-system implementation for DataStore

[RESULT][VOTE] Release Apache Jackrabbit Oak Segment Tar version 0.0.16

Hi, The vote passes as follows: +1 Michael Dürig +1 Francesco Mari +1 Davide Giannella +1 Alex Parvulescu Thanks for voting. I'll push the release out.

Re: segment-tar depending on oak-core

Il giorno ven 21 ott 2016 alle ore 16:08 Thomas Mueller ha scritto: > Hi, > > >The release process in Oak is a joke. > > I don't think it's a joke. > > > Releasing every two weeks by > >using version numbers as counters just for the sake of it is > >embarrassing. > > Why? It's

Re: Oak 1.5.13 release plan

I would like to have OAK-4975 included. Marked that issue as blocker. I hope to resolve that today itself Chetan Mehrotra On Thu, Oct 20, 2016 at 7:07 PM, Davide Giannella wrote: > Hello team, > > I'm planning to cut Oak 1.5.13 on Monday 24th. > > If there are any objections

Re: [VOTE] Release Apache Jackrabbit Oak 1.4.9

[X] +1 Release this package as Apache Jackrabbit Oak 1.4.9 Davide

Re: segment-tar depending on oak-core

On 21.10.16 3:04 , Julian Sedding wrote: an arguably simpler solution would be to give oak-run and oak-upgrade a separate lifecycle. They are consumers of both segment-tar and oak-core (+ other bundles with same release cycle). Hence they require interoperable releases of both *before* they