For Spark and ML components the best dates should be moved to one month later, what's about? There are a lot of features there, but a lot of bugs and minor improvements in JIRA too
Also I support you as a release manager Scope Freeze: December 4, 2019 Code Freeze: December 18, 2019 Voting Date: January 10, 2019 Release Date: January 17, 2019 пт, 20 сент. 2019 г. в 14:44, Maxim Muzafarov <mmu...@apache.org>: > Igniters, > > > It's almost a year has passed since the last major Apache Ignite 2.7 > has been released. We've accumulated a lot of performance improvements > and a lot of new features which are waiting for their release date. > Here is my list of the most interesting things from my point since the > last major release: > > Service Grid, > Monitoring, > Recovery Read > BLT auto-adjust, > PDS compression, > WAL page compression, > Thin client: best effort affinity, > Thin client: transactions support (not yet) > SQL query history > SQL statistics > > I think we should no longer wait and freeze the master branch anymore > and prepare the next major release by the end of the year. > > > I propose to discuss Time, Scope of Apache Ignite 2.8 release and also > I want to propose myself to be the release manager of the planning > release. > > Scope Freeze: November 4, 2019 > Code Freeze: November 18, 2019 > Voting Date: December 10, 2019 > Release Date: December 17, 2019 > > > WDYT? >
