On Fri, 23 Mar 2018 15:52:51 +0000, you wrote: >Java 8 was marked as EOL in the middle of last year, I hope we wouldn't >require it for Cassandra 4. At this point I feel like we should already be >targeting Java 10 at a minimum.
Given that the last messages indicated aiming Cassandra 4 for the 3rd/4th quarter it is a bit of quandary. Perhaps the answer is to aim for Q4 by for now building and testing on Java 10, and then when Java 11 is released switching to that for testing only, with the hope of getting Cassandra 4 out a couple of months after Java 11 (assuming Java 11 is on time, but one of the hoped for effects of a 6 month cadence is you don't run into big changes that delay things). With Java 11 you then get the latest LTS which Oracle and I would assume Red Hat and other supporting for years instead of months. Essentially, if organizations are going to go through the process of a significant upgrade in Cassandra then let them at least at the same time have the option of getting onto the lastest LTS Java so they can mimize future disruptions. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
