On Tue, 2017-09-05 at 16:11 +0200, Julian Reschke wrote: > On 2017-09-05 13:50, Robert Munteanu wrote: > > On Tue, 2017-09-05 at 12:21 +0200, Julian Reschke wrote: > > > On 2017-09-05 10:56, Robert Munteanu wrote: > > > > Hi, > > > > > > > > Is there any tentative timeline for releasing Jackrabbit > > > > 2.14.3? > > > > I'm > > > > interested in a couple of fixes for the Sling 10 release, > > > > namely: > > > > > > > > - https://issues.apache.org/jira/browse/JCR-4179 ( fixed, > > > > backported ) > > > > - https://issues.apache.org/jira/browse/JCR-4173 ( fixed, not > > > > backported ) > > > > > > > > I can do the missing backport myself, but the release is > > > > probably > > > > too > > > > big a hat for me :-) > > > > > > I was planning to, but wanted to release 2.15.* first. > > > > > > Can you test & confirm that the fix for JCR-4173 in trunk > > > addresses > > > the > > > problem that you discovered? > > > > Yes, the fix for JCR-4173 unblocks the test fix. > > ... > > OK, the release for 2.6.* is currently in process. I'll follow up > with a > trunk release later this week (see release plan mail), and then do > 2.14.3 once that is done. > > Is that quick enough? (I can speed things up more, but would prefer > not > to do more than one release at once)
That should be fine. For context, we are aiming to get Sling 10 out by September 21st, when Java 9 is out. Do do that, we probably need the Jackrabbit 2.14.3 release done by the 18th of September. Is that doable with your current schedule? Robert
