My concern is only in fact, that Ignite is currently not tested under Java9/10 as thorough as it is under Java8.
As I mentioned before - I agree with no blocker on this matter and have no other problems to report for now. I guess I’ll start a new thread about the scheme of supporting future Java versions. On Sat, 24 Mar 2018 at 07:29, Denis Magda <dma...@apache.org> wrote: > Petr, > > I think your statement in regards the non-readiness for the production > usage is too strong :) The issue you listed treated as usability ones by > me. Agree that it's inconvenient to inject ‘--add-modules’ here and there > but it doesn't lead to failures at runtime. > > If I'm still missing something and there are the bugs that might affect the > stability of the clusters at runtime, then please share them with us. > You're more aware than anyone else. > > -- > Denis > > On Fri, Mar 23, 2018 at 8:50 PM, Petr Ivanov <mr.wei...@gmail.com> wrote: > > > Agree with no blocker. > > > > Then as developers we just have to send a clear message that "we making > it > > towards Java9/10 honest support, but do not use it yet on prod > > environments” :) > > > > > > > On 23 Mar 2018, at 22:41, Denis Magda <dma...@apache.org> wrote: > > > > > > Petr, > > > > > > I guess we would need much more time to handle all Java 9/10 tasks. > Since > > > none of them looks like a blocker to me, I would suggest us not to rush > > and > > > target the tasks for 2.4 release. > > > > > > Overall, I see that we're in an agreement in regards the earlier date > of > > > 2.5 release. I'll let the rest of the community to speak out until the > > > beginning of the next week. > > > > > > -- > > > Denis > > > > > > > > > > > > On Thu, Mar 22, 2018 at 8:24 PM, Petr Ivanov <mr.wei...@gmail.com> > > wrote: > > > > > >> I’ll do my best to deliver packages in time. > > >> > > >> > > >> Concerning Java 9/10 — AFAIK there are limitations how do we support > it: > > >> * compilation is supported with scala_2.10 modules switched off (due > to > > >> scala support Java 9 itself starting from 2.12.x+ versions); > > >> * also compilation and run is possible only with lots of > ‘--add-modules’ > > >> hacks — I think that to say we support Java 9 we have to add modules > > info > > >> to every package; > > >> * tests (project ‘Ignite Tests 2.4+ (Java 9)’) also require attention, > > >> because there are some problems with theirs run. > > >> > > >> > > >> > > >>> On 22 Mar 2018, at 21:09, Denis Magda <dma...@apache.org> wrote: > > >>> > > >>> Petr, > > >>> > > >>> Java Thin client, GA Grid, COPY command are the most significant > > >> additions > > >>> to the release (if to talk about the features). Aside from that, I > see > > >> many > > >>> valuable optimizations and fixes that have been sitting in the master > > >> for a > > >>> while (some of them were merged in January). It's preferable to > release > > >>> them. > > >>> > > >>> As for Java 10 and DEB, if you feel you can't make them to the > release, > > >>> then it can wait till 2.6. > > >>> > > >>> Speaking of Java 9, what's left? I thought it's already fully > > supported. > > >>> > > >>> -- > > >>> Denis > > >>> > > >>> On Thu, Mar 22, 2018 at 10:47 AM, Petr Ivanov <mr.wei...@gmail.com> > > >> wrote: > > >>> > > >>>> Will there be a major new feature or this release will concentrate > on > > >>>> stability and optimisations? > > >>>> > > >>>> Also, I guess, we will have to include into 2.5 release full support > > for > > >>>> Java 9 and Java 10 (that WILL require some developers time). > > >>>> And RPM / DEB packages stage II phase will require lots of testing > and > > >>>> infrastructure preparations: place to store package, RPM / DEB build > > >>>> inclusion into release process and so on. > > >>>> > > >>>> Apr 30 sounds good, but I’d have a “place for manoeuvre” in case all > > >> those > > >>>> activities are not finished in time. > > >>>> > > >>>> > > >>>> > > >>>>> On 22 Mar 2018, at 20:39, Denis Magda <dma...@apache.org> wrote: > > >>>>> > > >>>>> Igniters, > > >>>>> > > >>>>> According to our regular schedule, every new Ignite version usually > > >> goes > > >>>>> public once in 3 months. As you remember, the latest 2.4 release, > > which > > >>>>> took us 5 months to improve and roll out, was based on the version > of > > >> the > > >>>>> source code dated by January. > > >>>>> > > >>>>> Since that time the master branch went far ahead and already > > >> incorporates > > >>>>> many valuable fixes and capabilities such as: > > >>>>> > > >>>>> - Fixes provided as a part of "Gree Team City" activity. > > >>>>> - Persistence: page replacement algorithm and throttling > > >> optimizations, > > >>>>> out of memory in checkpointing buffer corrections, etc. Alex G and > > >>>> Ivan can > > >>>>> shed more light here. > > >>>>> - Data loading optimizations for SQL: streaming for JDBC thin > driver > > >>>> and > > >>>>> copy command > > >>>>> - Genetic Algorithms Grid Contribution! > > >>>>> - Java Thin Client developed by Alexey Kukushkin > > >>>>> > > >>>>> > > >>>>> - the list goes on and on... Please share the contributions you are > > >>>>> ready to release. > > >>>>> > > >>>>> So, why don't we go ahead and release the current master and > possibly > > >>>> extra > > >>>>> tickets that are in the review state earlier? What's about April 30 > > as > > >>>> the > > >>>>> next release date? > > >>>>> > > >>>>> -- > > >>>>> Densi > > >>>> > > >>>> > > >> > > >> > > > > >
