[ANNOUNCE] Apache Jackrabbit Oak 1.2.28 released

The Apache Jackrabbit community is pleased to announce the release of Apache Jackrabbit Oak 1.2.28. The release is available for download at: http://jackrabbit.apache.org/downloads.html See the full release notes below for details about this released: Release Notes -- Apache Jackrabbit Oak

[RESULT][VOTE] Release Apache Jackrabbit Oak 1.2.28

Hi, The vote passes as follows: +1 Julian Reschke +1 Alex Deparvu +1 Andrei Dulceanu +1 Davide Giannella +1 Amit Jain Thanks for voting. I'll push the release out. Regards Amit

Re: Intent to backport OAK-7176

+1 On Thu, Jan 18, 2018 at 5:11 PM, Marcel Reutegger wrote: > Hi, > > I'd like to backport OAK-7176 to maintenance branches 1.8, 1.6 and 1.4. The > issue is only minor and is unlikely to occur in practice, but it is clearly a > violation of the RevisionVector

Intent to backport OAK-7176

Hi, I'd like to backport OAK-7176 to maintenance branches 1.8, 1.6 and 1.4. The issue is only minor and is unlikely to occur in practice, but it is clearly a violation of the RevisionVector contract. The fix is easy and low risk. Regards Marcel

Re: 1.0.40 broken because of missing package exports

+1 On 1/18/2018 11:08 AM, Davide Giannella wrote: On 18/01/2018 05:56, Julian Reschke wrote: So I believe this is fixed now - should we attempt a new release? +1 as 1.0.40 won't be usable in OSGi environment. D.

Re: svn commit: r1821482 [1/7] - in /jackrabbit/site/live/oak/docs: ./ architecture/ coldstandby/ features/ nodestore/ nodestore/document/ nodestore/segment/ oak-mongo-js/ oak_api/ plugins/ query/ sec

Hi, something is wrong here. The Oak Documentation page now says 'Last Published 2017-05-02' and 'Version 1.8-SNAPSHOT'. Did you forget to update before you generated the site? Regards Marcel On 18/01/18 12:08, thom...@apache.org wrote: Author: thomasm Date: Thu Jan 18 11:08:07 2018 New

Oak 1.8.1 release plan

Hello team, I'm planning to cut Oak on Monday 22nd Jan. 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: 1.0.40 broken because of missing package exports

On 18/01/2018 05:56, Julian Reschke wrote: > So I believe this is fixed now - should we attempt a new release? +1 as 1.0.40 won't be usable in OSGi environment. D.

Re: 1.0.40 broken because of missing package exports

On 18/01/18 06:56, Julian Reschke wrote: On 2018-01-17 12:44, Julian Reschke wrote: See    https://issues.apache.org/jira/browse/OAK-7167 So it seems we need to fix this, and start a new release cycle? Feedback appreciated. So I believe this is fixed now - should we attempt a new release?