Hi, In general +1 for requiring Java 11 from the next JR release on. Before doing the actual branching I would love to migrate to Git though. That not only eases backporting fixes and switching between branches but hopefully also encourages external contributions (although we do already have the GitHub mirror). It becomes harder nowadays to find good tooling for SVN. WDYT? I am volunteering for doing the actual SVN -> Git migration with the help of ASF INFRA. Konrad
> On 11. Oct 2023, at 19:21, Julian Reschke <[email protected]> wrote: > > Hi there, > > I believe we should consider requiring Java 11 for trunk work, and when > done, create a new maintenance branch from it. > > Reasons: > > - some of our dependencies now require Java 11 > > - we currently use Jackrabbit 2.20 (Java 8) in both Oak 1.22 (Java 8) > and Oak 1.58 ("latest stable", Java 11); on the other hand, we > *implement* jackrabbit API from Oak, and haven't been able to update > that since Oak switched to 11 > > Other thoughts: > > - we currently have only one maintenance branch, so adding another one > which is mostly identical shouldn't create a lot of work > > - we'll need to maintain 2.20 (Java 8) until Oak 1.22 switches to Java > 11 (or some new Oak maintenance branch for Java 11 is created) > > Proposal: > > - make one more unstable release, removing RMI support > (https://issues.apache.org/jira/browse/JCR-4972) (ca December) > > - branch 2.22 and release 2.22.0 from trunk around February > > Questions: > > - apart from RMI, is there anything else we could discontinue? JCA maybe? > > Feeback appreciated, Julian >
