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
