Re: [DISCUSS] Cassandra and future Java

2018-05-30 Thread kurt greaves
I suppose so, I guess just highlighting that we shouldn't bother dedicating much testing resources to 4.0 on 11. I will note however that if we wanted to start making changes to support 11 it'd have to be (as Robert alluded to) based off an incomplete 11 as I'm assuming we'd make no further

Re: [DISCUSS] Cassandra and future Java

2018-05-30 Thread Stefan Podkowinski
That's probably not far off what Robert suggested: "The idea here is to default to Java 8, but the code also runs on 11" "Initially, only the combination of C* 4.0 + Java 8 would be labeled as "stable" and the combination of C* 4.0 + Java 11 as "experimental"." If Robert wants to go ahead

Re: [DISCUSS] Cassandra and future Java

2018-05-30 Thread kurt greaves
So for anyone that missed it, Java 11 will be released in September 2018. I'd prefer we target one Java release only. This is purely because we don't have the capacity or capability to test both releases. We hardly do a good enough job as it is of testing and lumping another JVM into the mix is

Re: [DISCUSS] Cassandra and future Java

2018-05-29 Thread Robert Stupp
Ideally, CI would run against both Java 8 and 11. I’ve no clue about b.a.o though. There will definitely be a log of smaller issues - both for OpenJDK 8 and 11. I think, it’s sufficient to deal with the Linux distros' (RH/deb) openjdk dependencies - just making sure, that we’re using the right

Re: [DISCUSS] Cassandra and future Java

2018-05-28 Thread Stefan Podkowinski
The main issue that I see, for supporting both Java 8 + 11, is testing. We should first decide how this would effect builds.apache.org, or how we're going to do CI testing in general for that situation. There are probably also smaller issues that we're not aware of yet, such as which Java

Re: [DISCUSS] Cassandra and future Java

2018-05-25 Thread Jonathan Haddad
Personally I don’t mind dropping support for previsous java versions. On Fri, May 25, 2018 at 6:33 AM J. D. Jordan wrote: > +1 for “Option 3: both 8 + 11” it shouldn’t be too hard to maintain code > wise, and leaves people’s options open. > > -Jeremiah > > > On May

Re: [DISCUSS] Cassandra and future Java

2018-05-25 Thread J. D. Jordan
+1 for “Option 3: both 8 + 11” it shouldn’t be too hard to maintain code wise, and leaves people’s options open. -Jeremiah > On May 25, 2018, at 6:31 AM, Robert Stupp wrote: > > I'd like to bring up the C*/Java discussion again. It's been a while since > we've discussed this.

[DISCUSS] Cassandra and future Java

2018-05-25 Thread Robert Stupp
I'd like to bring up the C*/Java discussion again. It's been a while since we've discussed this. To me it sounds like there's still the question about which version(s) of Java we want to support beginning with C* 4.0. I assume, that it's legit (and probably very necessary) to assume that