Hi, yes. JCRVLT-341 will be solved when including the new jackrabbit (JCRVLT-364). Regards, Toby
> On 6 Sep 2019, at 16:35, Konrad Windszus <[email protected]> wrote: > > Hi, > IMHO the issues https://issues.apache.org/jira/browse/JCRVLT-341, > https://issues.apache.org/jira/browse/JCRVLT-352 and > https://issues.apache.org/jira/browse/JCRVLT-364 should be included in the > upcoming list which leaves only two remaining issues open (which can be > deferred to the next version). > I can try to do the release next week. > > Best, > Konrad > >> On 6. Sep 2019, at 09:31, Tobias Bocanegra <[email protected]> wrote: >> >> Hi, >> >> Based on the recent discussion, I would like to cut a new Jackrabbit >> FileVault release next week. >> >> I suggest to: >> >> - rename the current 3.2.10 release in jira [0] to 3.4.0 >> - move the remaining 4 open issues to 3.4.2 >> - update the jackrabbit and oak dependencies [1] >> - create a 3.2.x branch and update the docu that 3.2.8 is the last java 7 >> release. >> >> WDYT? >> >> Regards, Toby >> >> PS: Konrad, Dominik, does any of you want to try and cut the release? It's >> 90% automated and total fun! >> *and* we have a more or less useful release documentation: [2] >> >> [0] https://issues.apache.org/jira/projects/JCRVLT/versions/12345172 >> [1] https://issues.apache.org/jira/browse/JCRVLT-364 >> [2] https://jackrabbit.apache.org/filevault/howto_release.html >> >
