Personally, I'd planned to upgrade to 4.0 on JDK8 but only wait a few weeks before starting to update to JDK11 afterwards. Everything else we run's been updated to JDK11, so the Cassandra clusters are the odd one out at this point.
On Mon, Jul 13, 2020 at 12:19 PM Jordan West <jw...@apache.org> wrote: > Thanks for bringing this up Jon! My current thinking is we should > officially support both 8 and 11. That increases the surface area we need > to test but I think its hard to predict what different users will run given > the current transition in the Java landscape. > > Jordan > > On Mon, Jul 13, 2020 at 11:42 AM Jon Haddad <j...@jonhaddad.com> wrote: > > > Support for Java 11 was added a long time ago, and it's been about 2 > years > > since it was released (Sept 2018). Had we released Cassandra 4 close to > > that date, I'd be fine with keeping the status as experimental, but at > this > > point I'm wondering if releasing a new major version of C* that's > primarily > > targeting Java 8 as the only "official" supported version is a good idea. > > > > To those of you that are planning on rolling out C* 4.0, are you planning > > on using Java 8 still, or moving to 11? Speaking for myself, I can say I > > don't think I'd want to use 8 anymore. If most folks are testing with 11 > > at this point, I think we should consider making 11 the recommended > version > > and really only encouraging Java 8 for legacy purposes - teams who have a > > restriction that prevents them from upgrading. > > > > To those of you planning on moving to 4.0 soon after it's release, are > you > > planning on deploying to JDK 11 or 8? > > > > [1] > https://www.oracle.com/java/technologies/java-se-support-roadmap.html > > >
