Re: What's about releasing Ignite 2.5 a bit earlier?

Andrey, it's great to see you in a role of 2.5 release engineer! Thanks for stepping in. -- Denis On Tue, Mar 27, 2018 at 8:42 AM, Andrey Gura wrote: > Igniters, > > I'm ready to take care of Apache Ignite 2.5 release. > > I've started preparing wiki pages. There are many

Re: What's about releasing Ignite 2.5 a bit earlier?

Igniters, I'm ready to take care of Apache Ignite 2.5 release. I've started preparing wiki pages. There are many fixes in master branch so I think that we should limit scope of the release soon (e.g. next week) because stabilization and QA activities will also require time. I'll keep the

Re: What's about releasing Ignite 2.5 a bit earlier?

Good, hope that everyone interested has enough time to share an opinion. As a summary of this discussion, the community decided to release Ignite 2.5 on April 30. Most of the changes and features are already in the master. Who is ready to become a release manager of 2.5? We need to prepare a

Re: What's about releasing Ignite 2.5 a bit earlier?

Hi, We already implemented LSQR for linear regression and SVM(support vector machine) algorithms. Also we implement new distributed Datasets. And we want to adapt all our algorithms to this new dataset API. So from my point of view we have enough time for those tasks. So I think that we could

Re: What's about releasing Ignite 2.5 a bit earlier?

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

Re: What's about releasing Ignite 2.5 a bit earlier?

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

Re: What's about releasing Ignite 2.5 a bit earlier?

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 wrote: > > Petr, > > I guess we would need much more

Re: What's about releasing Ignite 2.5 a bit earlier?

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

Re: What's about releasing Ignite 2.5 a bit earlier?

Hi Igniters, There are two tickets I forgot to mention, it is optimisation of Native Persistence: Performing data pages IO outside locks - https://issues.apache.org/jira/browse/IGNITE-7606 - Write removed dirty page during replacement without holding segment write lock -

Re: What's about releasing Ignite 2.5 a bit earlier?

I agree. Fix of LOG_ONLY is critical for Ignite durability and can be done quickly. Another reason to release 2.5 earlier is fix of https://issues.apache.org/jira/browse/IGNITE-7751. It's another critical bug that possibly can lead to checkpoint buffer overflow and corruption of internal data

Re: What's about releasing Ignite 2.5 a bit earlier?

Denis, Java thin client is in the final review stage - I expect it will go to master sometime next week. April 30 release date seems to have enough contingency for this component. Thanks!

Re: What's about releasing Ignite 2.5 a bit earlier?

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

Re: What's about releasing Ignite 2.5 a bit earlier?

Nikolay, Sounds like a good idea. I will do my best to speed up the process and review asap. -Val On Thu, Mar 22, 2018 at 11:37 AM, Nikolay Izhikov wrote: > Hello, guys > > I agree with earlier release. > > I propose to include my task IGNITE-7077 to 2.5 release. > >

Re: What's about releasing Ignite 2.5 a bit earlier?

Hi Igniters, Why not? Let's release it a bit earlier. I think it would be good if Ivan will prepare fix for WAL LOG_ONLY: http://apache-ignite-developers.2346864.n4.nabble.com/Reconsider-default-WAL-mode-we-need-something-between-LOG-ONLY-and-FSYNC-td28165.html Ivan, what do you think? Also it

Re: What's about releasing Ignite 2.5 a bit earlier?

Also, we has new API - ContinuousQueryWithTransformer merged for 2.5 release - [IGNITE-425] В Чт, 22/03/2018 в 21:37 +0300, Nikolay Izhikov пишет: > Hello, guys > > I agree with earlier release. > > I propose to include my task IGNITE-7077 to 2.5 release. > > Valentin, do you have a time slot

Re: What's about releasing Ignite 2.5 a bit earlier?

Hello, guys I agree with earlier release. I propose to include my task IGNITE-7077 to 2.5 release. Valentin, do you have a time slot to review my implementation? В Чт, 22/03/2018 в 10:39 -0700, Denis Magda пишет: > Igniters, > > According to our regular schedule, every new Ignite version

Re: What's about releasing Ignite 2.5 a bit earlier?

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

Re: What's about releasing Ignite 2.5 a bit earlier?

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