Re: parent pom env.OAK_INTEGRATION_TESTING

[Chetan Mehrotra]

On Tue, Mar 22, 2016 at 9:49 PM, Davide Giannella  wrote:
> I can't really recall why and if we use this.

Its referred to in main README.md so as to allow a developer to always
enable running of integration test

Chetan Mehrotra

Re: [discuss][scalability] oak:asyncConflictResolution

[Stefan Egli]

Hi,

On 21/03/16 21:23, "Michael Dürig"  wrote:
> There is org.apache.jackrabbit.oak.spi.commit.PartialConflictHandler and
> a couple of its implementations already. Maybe this could be leveraged
> here by somehow connecting it to the mix-ins you propose.

Yes, I think it should be something like a PartialConflictHandler that is
either configurable or customizable.

On 22/03/16 11:35, "Davide Giannella"  wrote:
> I'd go for the mixin, with a default chain/order of conflict resolution
> and allow to define such in a multivalue property. So that in case
> needed the user can define its own chain of conflict resolution, or even
> custom one if needed.

Right, sounds like a mixin rather than (just) a property would be more
appropriate.

Cheers,
Stefan

parent pom env.OAK_INTEGRATION_TESTING

[Davide Giannella]

hello team

I was trying to achieve https://issues.apache.org/jira/browse/OAK-4136
by enabling multiple profiles using the same property when I stumbled
upon the variable `env.OAK_INTEGRATION_TESTING` for the
`integrationTesting` profile

https://github.com/apache/jackrabbit-oak/blob/8af23571f44055ba28b850c45b17de8818fbbff6/oak-parent/pom.xml#L566

I can't really recall why and if we use this.

I didn't find any references in the apache jenkins as well.

Do you think it's something safe to remove? Where is it used if it is?

Thanks
Davide

Re: [VOTE] Release Apache Jackrabbit Oak 1.0.29

[Davide Giannella]

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


Davide

Re: [VOTE] Release Apache Jackrabbit Oak 1.0.29

[Alex Parvulescu]

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

all checks ok

alex

On Tue, Mar 22, 2016 at 1:55 PM, Dominique Jaeggi  wrote:

> A candidate for the Jackrabbit Oak 1.0.29 release is available at:
>
> https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.0.29/
>
> The release candidate is a zip archive of the sources in:
>
> https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.0.29/
>
> The SHA1 checksum of the archive is
> c8061e82f921a9fd946e30f49e3606113bf7bae0.
>
> A staged Maven repository is available for review at:
>
> https://repository.apache.org/
>
> The command for running automated checks against this release candidate is:
>
> $ sh check-release.sh oak 1.0.29
> c8061e82f921a9fd946e30f49e3606113bf7bae0
>
> Please vote on releasing this package as Apache Jackrabbit Oak 1.0.29.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
>
> [ ] +1 Release this package as Apache Jackrabbit Oak 1.0.29
>
> [ ] -1 Do not release this package because...
>
> My vote is +1.
>
> Thanks
> dom.
>

[VOTE] Release Apache Jackrabbit Oak 1.0.29

[Dominique Jaeggi]

A candidate for the Jackrabbit Oak 1.0.29 release is available at:

https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.0.29/

The release candidate is a zip archive of the sources in:

https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.0.29/

The SHA1 checksum of the archive is
c8061e82f921a9fd946e30f49e3606113bf7bae0.

A staged Maven repository is available for review at:

https://repository.apache.org/

The command for running automated checks against this release candidate is:

$ sh check-release.sh oak 1.0.29 c8061e82f921a9fd946e30f49e3606113bf7bae0

Please vote on releasing this package as Apache Jackrabbit Oak 1.0.29.
The vote is open for the next 72 hours and passes if a majority of at
least three +1 Jackrabbit PMC votes are cast.

[ ] +1 Release this package as Apache Jackrabbit Oak 1.0.29

[ ] -1 Do not release this package because...

My vote is +1.

Thanks
dom.

Oak 1.4.1 release plan

[Davide Giannella]

Hello team,

I'm planning to cut Oak 1.4.1 on the 24th of March in the AM GMT.

If there are any objections please let me know. Otherwise I will
re-schedule any non-resolved issue for the next iteration.

Thanks
Davide

Re: [discuss][scalability] oak:asyncConflictResolution

[Davide Giannella]

On 21/03/2016 20:03, Stefan Egli wrote:
> Hi oak-devs,
>
> tl.dr: suggestion is to introduce a new property (or mixin) that enables
> async merge for a subtree in a cluster case while at the same time
> pre-defines conflict resolution, since conflicts currently prevent
> trouble-free async merging.
> ...

Overall I like the idea as it leaves to the repository creator the
ability to define such behaviours.

I'd go for the mixin, with a default chain/order of conflict resolution
and allow to define such in a multivalue property. So that in case
needed the user can define its own chain of conflict resolution, or even
custom one if needed.

Davide

Release plan Oak 1.2.13

[Amit Jain]

Hi Team,

I plan to release Oak 1.2.13 tomorrow early morning and will reschedule any
unresolved issues (currently 2).
Let me know if there is anything urgent that needs to be included.

Thanks
Amit