I’ve been busy on other projects, but the Java ones are moving towards 11 over 8 due to EoL issues.
Sent from my iThingy > On May 2, 2020, at 20:52, Andrew Gaul <g...@apache.org> wrote: > > On Sat, May 02, 2020 at 12:49:16PM -0400, Andrew Phillips wrote: >>> Some ideas: >>> >>> * spin out components, similar to what we did with jclouds-karaf >>> previously >>> * release from master and stop maintaining release branches, e.g., 2.2.x >>> * reduce the Java compatibility matrix, e.g., Java 8 and newer only >>> * upgrade key dependencies, e.g., BouncyCastle, Guava, to avoid >>> dependency headaches >>> * graduate more providers in labs >> >> These all seem reasonable to me - do you have any gut feel estimate of which >> would reduce the burden the most? > > Dependency interactions are top of mind and something I spent an evening > debugging for 2.2.1. I spent the last few years outside the Java > ecosystem so I lack a nuanced understanding of where the community is > but Java 8 seems table stakes these days. > > -- > Andrew Gaul > http://gaul.org/
