++1 for testing using JDK11 +0 for switching off support of JDK8 runtimes and class version (unless compilation using JDK11 is done with -target=1.8 our users won't be able to run Ignite using Java 8).
I suggest the following next steps: once tests are completely fine on Teamcity using JDK 11, we start a separate thread named like: "[VOTE] discontinuing JDK 8 since the 2.16 release" to make the issue for end users more obvious. Since Nikita volunteers to be a Release Manager, I suppose that 2.16 will be released quite soon. I personally prefer to switch to newer Java. Using newer runtime helps us to provide speed and scale, since JVM is developed all the time. But I might be unaware of the risks, so let's discuss it later with the entire dev community. Sincerely, Dmitriy Pavlov ср, 30 авг. 2023 г. в 19:09, Ivan Daschinsky <ivanda...@gmail.com>: > +1, sounds reasonable for the open source project. IMHO, Eclipse Temurin > JDK is a rule of thumb choice nowadays. > > ср, 30 авг. 2023 г. в 18:40, Peter Ivanov <mr.wei...@gmail.com>: > > > Hi, Igniters! > > > > As part of this proposal I would also like to discuss the JDK vendors we > > are using on our CI platforms TeamCIty. > > Historically, Ignite 2.x is being built under Oracle's edition - mostly > > because of some features like JFR or similar. > > However today we have pretty much solid alternative represented by > OpenJDK > > and its most popular build Eclipse Temurin, which provides every required > > version for our needs (and especially LTS versions 1.8, 11 and 17) with > all > > necessary updates. > > > > So, I suggest we update our build agents for TeamCity accordingly, > provide > > OpenJDK framework for those 3 major versions and discontinue Oracle's > > builds. > > WDYT? > > > > пт, 25 авг. 2023 г. в 12:13, Ivan Daschinsky <ivanda...@gmail.com>: > > > > > +1. It's time to do it at last. > > > > > > пт, 25 авг. 2023 г. в 12:06, Peter Ivanov <mr.wei...@gmail.com>: > > > > > > > Mostly, yes. > > > > > > > > In other words - proposal is about starting shipping Apache Ignite > > > releases > > > > with JDK11 compiled binaries thus dropping JDK8-10 runtime support. > > > > > > > > пт, 25 авг. 2023 г. в 12:03, Anton Vinogradov <a...@apache.org>: > > > > > > > > > I looks like you're proposing not migration to 2.11 (because it is > > > > already > > > > > supported), but Java 8-9 support dropping. > > > > > > > > > > On Fri, Aug 25, 2023 at 11:54 AM Peter Ivanov <vvei...@apache.org> > > > > wrote: > > > > > > > > > > > Hi, Igniters! > > > > > > > > > > > > > > > > > > I would like to propose the next, if you don't mind me saying, > > > > > > revolutionary step forward in our project: moving Ignite 2.x > > > > compilation > > > > > to > > > > > > JDK11 minimum version. > > > > > > I'd rather not make arguments, pros and cons other that currently > > > exist > > > > > in > > > > > > Java world - you know them better than me. Let's just say that it > > > seems > > > > > > that time has come - consider at least that JDK11 as the LTS > > version > > > is > > > > > > already about 4 and a half years on the go, and Ignite 3.x > started > > > from > > > > > > JDK11 right away. > > > > > > > > > > > > This change may possibly require from us additional efforts on > > > > supporting > > > > > > the last version with JDK8 in terms of releasing additional > patches > > > and > > > > > > hotfixes a bit longer than usual. However, this is up to the > > > community > > > > to > > > > > > decide. > > > > > > > > > > > > Currently, Apache Ignite 2.x (with Extensions as well) is already > > > > > prepared > > > > > > for being compiled with JDK11 and almost all tests are passing. > If > > we > > > > > come > > > > > > to an agreement about this proposal and designate the next > version > > > that > > > > > > will become the first to provide JDK11 compiled binaries - I am > > ready > > > > to > > > > > > start the process of updating the TeamCity building project > > > > accordingly. > > > > > > > > > > > > > > > > > > Please, share your thoughts. > > > > > > > > > > > > > > > > > > > > > > > > -- > > > Sincerely yours, Ivan Daschinskiy > > > > > > > > -- > Sincerely yours, Ivan Daschinskiy >
