Alexey Z., Could you please answer some of the questions
> - IGNITE-11942 IGFS and Hadoop Accelerator Discontinuation [2]. > Probably should be moved to the next release due to dependency on > Tensorflow. Need to check. (Andrey Gura) Can we decouple Tensorflow from the IGFS? Mark all the issues related to ML, Spark 2.4, Monitoring major > features and track their comletion to be sure on there is no > unfinished major changes will be present in 2.8 release. > - ML (Alexey Zinoviev) Are there any other ML contributors who will be helping you with this release? - Denis On Tue, Oct 1, 2019 at 6:56 AM Maxim Muzafarov <mmu...@apache.org> wrote: > Igniters, > > > Here is the list of activities we've agreed on to prepare the Apache > Ignite 2.8 release. > > 1. > Preliminary release dates with the ability to shift them if some of > the planned activities will not be finalized. But anyway we should > build our engagement based on these dates. > > Scope Freeze: November 5, 2019 > Code Freeze: December 2, 2019 > Voting Date: January 10, 2020 > Release Date: January 17, 2020 > > 2. > Mark all the issues related to ML, Spark 2.4, Monitoring major > features and track their comletion to be sure on there is no > unfinished major changes will be present in 2.8 release. > - ML (Alexey Zinoviev) > - Spark [1] [4] (Alexey Zinoviev) > - Monitoring (Nikolay Izhikov) > > 3. > Review and mark all the partially completed major issues currently > present in the master branch. > - major IEPs e.g. IEP-18, non-blocking PME (Maxim Muzafarov) > - review major commits in the master branch (Maxim Muzafarov) > > 4. > Review blocker issues currently pinned to 2.8 release. > - IGNITE-11942 IGFS and Hadoop Accelerator Discontinuation [2]. > Probably should be moved to the next release due to dependency on > Tensorflow. Need to check. (Andrey Gura) > - IGNITE-9489 CorruptedTreeException on index create [3]. Check all > the issues releated to this. Some of them already fixed by GridGain. > Need to check. (Andrey Gura) > - IGNITE-12181 Rebalance hangs on BLT change. The cause has been > found. Will be fixed. (Maxim Muzafarov) > - Need to check all the other blocker issues (Maxim Muzafarov) > > 5. > QA regression (2.7 -> 2.8). I'll provide additional details when I'll get > them. > Review and check test-cases, optioannly schedule meeting (Maxim Muzafarov) > > 6. > (optional) Need to create an INFRA ticket to add `Epic` JIRA issue > type to the Apache Ignite JIRA. The issue [6] has been created but not > sure that I have the right permission to do so. > > [1] > http://apache-ignite-developers.2346864.n4.nabble.com/The-Spark-2-4-support-td43777.html > [2] https://issues.apache.org/jira/browse/IGNITE-11942 > [3] https://issues.apache.org/jira/browse/IGNITE-9489 > [4] https://issues.apache.org/jira/browse/IGNITE-12054 > [5] https://issues.apache.org/jira/browse/IGNITE-12181 > [6] https://issues.apache.org/jira/browse/INFRA-19164 > > On Mon, 30 Sep 2019 at 12:14, Ivan Pavlukhin <vololo...@gmail.com> wrote: > > > > Maxim, Folks, > > > > Could you please share a results of the Slack discussion from Sep 25? > > > > ср, 25 сент. 2019 г. в 15:50, Dmitriy Pavlov <dpav...@apache.org>: > > > > > > Hi Maxim, > > > > > > Thank you for preparing the release page! > > > > > > Could you please add Require release notes filter? You can find an > example > > > in > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.7.6 > > > > > > Sincerely > > > Dmitriy Pavlov > > > > > > ср, 25 сент. 2019 г. в 11:58, Maxim Muzafarov <mmu...@apache.org>: > > > > > > > Igniters, > > > > > > > > > > > > It's true that we are still discussing the release dates. But > > > > nevertheless, all the release blockers are important since some of > > > > them may require more than one month to be fixed. Let's discuss today > > > > how we will handle these issues and track Monitoring and ML major > > > > features to get them into the next release. > > > > > > > > The meeting already scheduled. We will use the ASF Slack on September > > > > 25-th, 17-00 (MSK). > > > > I've created the channel [2] #ignite-release-2_8 please, join. > > > > (Discussion will be on Russin language). > > > > > > > > > > > > > > > > Please, also note that I've created the 2.8 release confluence page > > > > [1] with additional information. I will review all the issues we have > > > > and will move some of them to 2.9. > > > > But currently, we've had pinned to 2.8: > > > > > > > > - 604 open issues > > > > - 57 in progress issues > > > > - 34 patch available issues > > > > > > > > - 17 issues marked as the release blockers > > > > - 4 of release blocker issues are unassigned > > > > > > > > > > > > [1] > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8 > > > > [2] https://app.slack.com/client/T4S1WH2J3/CNQ51M4FQ > > > > > > > > On Wed, 25 Sep 2019 at 10:21, Dmitriy Pavlov <dpav...@apache.org> > wrote: > > > > > > > > > > Hi Igniters, > > > > > > > > > > I suppose discussion is still at phase 0-Initializing > > > > > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process > > > > > > > > > > So it is probably no reason to discuss particular blockers. It > would make > > > > > sense when the process of removal irrelevant tickets starts (phase > 1.2) > > > > and > > > > > till phase 4-Release candidate building. > > > > > > > > > > Sincerely, > > > > > Dmitriy Pavlov > > > > > > > > > > вт, 24 сент. 2019 г. в 18:53, Anton Kalashnikov <kaa....@yandex.ru > >: > > > > > > > > > > > Hello, Igniters. > > > > > > > > > > > > I want to notice one more blocker for release [1]. This bug can > lead to > > > > > > some incorrect baseline default enabled flag calculation(more > details > > > > in > > > > > > the ticket). > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-12227 > > > > > > > > > > > > -- > > > > > > Best regards, > > > > > > Anton Kalashnikov > > > > > > > > > > > > > > > > > > 24.09.2019, 17:01, "Andrey Gura" <ag...@apache.org>: > > > > > > > Sergey, > > > > > > > > > > > > > > As I know, scope freeze is not announced yet. > > > > > > > > > > > > > > On Tue, Sep 24, 2019 at 4:41 PM Sergey Antonov > > > > > > > <antonovserge...@gmail.com> wrote: > > > > > > >> Hi, I would add to release scope my ticket [1]. > > > > > > >> > > > > > > >> Any objections? > > > > > > >> > > > > > > >> [1] https://issues.apache.org/jira/browse/IGNITE-12225 > > > > > > >> > > > > > > >> вт, 24 сент. 2019 г. в 09:21, Nikolay Izhikov < > nizhi...@apache.org > > > > >: > > > > > > >> > > > > > > >> > > merge to master only fully finished features > > > > > > >> > > > > > > > >> > It's already true for Ignite master branch. > > > > > > >> > > > > > > > >> > > > > > > > >> > В Вт, 24/09/2019 в 09:03 +0300, Alexey Zinoviev пишет: > > > > > > >> > > The planned before 2_3 months release dates are good > defender > > > > from > > > > > > >> > > partially merged features, In my opinion > > > > > > >> > > > > > > > > >> > > Or we should have Master and dev branch separetely, and > merge > > > > to > > > > > > master > > > > > > >> > > only fully finished features > > > > > > >> > > > > > > > > >> > > пн, 23 сент. 2019 г., 20:27 Maxim Muzafarov < > mmu...@apache.org > > > > >: > > > > > > >> > > > > > > > > >> > > > Andrey, > > > > > > >> > > > > > > > > > >> > > > Agree with you. It can affect the user impression. > > > > > > >> > > > > > > > > > >> > > > Can you advise, how can we guarantee in our case when > we > > > > > > complete with > > > > > > >> > > > current partially merged features that someone will not > > > > partially > > > > > > >> > > > merge the new one? Should we monitor the master branch > > > > commits > > > > > > for > > > > > > >> > > > such purpose? > > > > > > >> > > > > > > > > > >> > > > On Mon, 23 Sep 2019 at 20:18, Andrey Gura < > ag...@apache.org> > > > > > > wrote: > > > > > > >> > > > > > > > > > > >> > > > > Maxim, > > > > > > >> > > > > > > > > > > >> > > > > > > From my point, if some components will not be > ready by > > > > > > >> > > > > > > previously discussed `scope freeze` date it is > > > > absolutely > > > > > > OK to > > > > > > >> > > > > > > perform the next (e.g. 2.8.1, 2.8.2) releases. > > > > > > >> > > > > > > > > > > >> > > > > It is good approach if partial implemented features > aren't > > > > > > merged to > > > > > > >> > > > > master branch. Unfortunately this is not our case. > > > > > > >> > > > > > > > > > > >> > > > > I don't see any reasons to force new Apache Ignite > release. > > > > > > Time is > > > > > > >> > > > > not driver for release. If we want release Ignite > > > > periodically > > > > > > we > > > > > > >> > must > > > > > > >> > > > > significantly review the process. And most valuable > change > > > > in > > > > > > this > > > > > > >> > > > > process is feature branches that will not block new > > > > release by > > > > > > >> > design. > > > > > > >> > > > > > > > > > > >> > > > > On Mon, Sep 23, 2019 at 8:12 PM Andrey Gura < > > > > ag...@apache.org> > > > > > > >> > wrote: > > > > > > >> > > > > > > > > > > > >> > > > > > > > From my point of view monitoring isn't ready > for > > > > release. > > > > > > >> > > > > > > Can you clarify, what exactly is not ready? > > > > > > >> > > > > > > Can we track planned changes somehow? > > > > > > >> > > > > > > > > > > > >> > > > > > We have too many not resolved tickets under IEP-35 > label > > > > > > [1]. Also > > > > > > >> > it > > > > > > >> > > > > > makes sense to do some usability testing: JMX beans > > > > > > interfaces, > > > > > > >> > system > > > > > > >> > > > > > views, etc. > > > > > > >> > > > > > > > > > > > >> > > > > > > > > > > > >> > > > > > [1] > > > > > > >> > > https://issues.apache.org/jira/issues/?jql=labels%20%3D%20IEP-35 > > > > > > >> > > > > > > > > > > > >> > > > > > On Mon, Sep 23, 2019 at 6:04 PM Nikolay Izhikov < > > > > > > >> > nizhi...@apache.org> > > > > > > >> > > > > > > > > > >> > > > wrote: > > > > > > >> > > > > > > > > > > > > >> > > > > > > Hello, Andrey. > > > > > > >> > > > > > > > > > > > > >> > > > > > > > From my point of view monitoring isn't ready > for > > > > release. > > > > > > >> > > > > > > > > > > > > >> > > > > > > Can you clarify, what exactly is not ready? > > > > > > >> > > > > > > Can we track planned changes somehow? > > > > > > >> > > > > > > > > > > > > >> > > > > > > > > > > > > >> > > > > > > В Пн, 23/09/2019 в 17:59 +0300, Andrey Gura > пишет: > > > > > > >> > > > > > > > Igniters, > > > > > > >> > > > > > > > > > > > > > >> > > > > > > > From my point of view monitoring isn't ready > for > > > > > > release. So it > > > > > > >> > > > > > > > > > >> > > > would > > > > > > >> > > > > > > > be great to return to this discussion later. > It seems > > > > > > that > > > > > > >> > > > > > > > > > >> > > > beginning > > > > > > >> > > > > > > > of November is good time for it. > > > > > > >> > > > > > > > > > > > > > >> > > > > > > > On Mon, Sep 23, 2019 at 5:37 PM Alexey > Zinoviev < > > > > > > >> > > > > > > > > > >> > > > zaleslaw....@gmail.com> wrote: > > > > > > >> > > > > > > > > > > > > > > >> > > > > > > > > Nikolay Izhikov, ok, let's arrange the talk > in ASF > > > > > > slack > > > > > > >> > between > > > > > > >> > > > > > > > > > >> > > > 16 and 19 > > > > > > >> > > > > > > > > MSK, is it possible? > > > > > > >> > > > > > > > > > > > > > > >> > > > > > > > > пн, 23 сент. 2019 г. в 17:35, Alexey > Zinoviev < > > > > > > >> > > > > > > > > > >> > > > zaleslaw....@gmail.com>: > > > > > > >> > > > > > > > > > > > > > > >> > > > > > > > > > Ok, I'll clarify the situation > > > > > > >> > > > > > > > > > > > > > > > >> > > > > > > > > > 1. Currently, the ML module is like a > black box > > > > for > > > > > > me. > > > > > > >> > What > > > > > > >> > > > > > > > > > >> > > > exactly > > > > > > >> > > > > > > > > > we are expected to get by the code freeze > date? > > > > Do > > > > > > we have > > > > > > >> > > > > > > > > > >> > > > tickets we > > > > > > >> > > > > > > > > > should address to? > > > > > > >> > > > > > > > > > > > > > > > >> > > > > > > > > > - Yes, we have a few epics that are not > finished > > > > > > yet, due > > > > > > >> > to > > > > > > >> > > > > > > > > > >> > > > limited free > > > > > > >> > > > > > > > > > time the planned dates were written earlier > > > > > > >> > > > > > > > > > > > > > > > >> > > > > > > > > > 2. I think we can move code freeze date to > > > > December > > > > > > 11-th > > > > > > >> > but, > > > > > > >> > > > > > > > > > >> > > > from > > > > > > >> > > > > > > > > > your side, do you think that 2-weeks of > > > > > > stabilization and > > > > > > >> > > > > > > > > > >> > > > regression > > > > > > >> > > > > > > > > > will be enough for the master branch living > > > > without > > > > > > release > > > > > > >> > > > > > > > > > >> > > > for a > > > > > > >> > > > > > > > > > year? > > > > > > >> > > > > > > > > > > > > > > > >> > > > > > > > > > Ok, I've ready to move code freeze to your > dates > > > > but > > > > > > not > > > > > > >> > to 1 > > > > > > >> > > > > > > > > > >> > > > November, it > > > > > > >> > > > > > > > > > sounds weird (why we should go so fast if > haven't > > > > > > released > > > > > > >> > > > > > > > > > >> > > > during the year) > > > > > > >> > > > > > > > > > I'm against fast releasing without planned > dates. > > > > > > >> > > > > > > > > > > > > > > > >> > > > > > > > > > 3. What do you think about that we will > make the > > > > > > huge 2.8 > > > > > > >> > > > > > > > > > >> > > > release in > > > > > > >> > > > > > > > > > November with long period of branch > stabilization > > > > > > and an > > > > > > >> > > > > > > > > > >> > > > additional > > > > > > >> > > > > > > > > > 2.8.1 release with ML component in > January? Such > > > > an > > > > > > >> > approach > > > > > > >> > > > > > > > > > >> > > > have some > > > > > > >> > > > > > > > > > advantages like we will not rush the > development > > > > of > > > > > > ML > > > > > > >> > > > > > > > > > >> > > > components. > > > > > > >> > > > > > > > > > > > > > > > >> > > > > > > > > > The best idea here is ability to merge the > last > > > > ML > > > > > > changes > > > > > > >> > > > > > > > > > >> > > > during > > > > > > >> > > > > > > > > > stabilization period (bug fixing, tests > and so > > > > on), > > > > > > is it > > > > > > >> > ok > > > > > > >> > > > > > > > > > >> > > > for you? > > > > > > >> > > > > > > > > > > > > > > > >> > > > > > > > > > 2.8.1 could be a good point, but remind you > > > > guys, the > > > > > > >> > normal > > > > > > >> > > > > > > > > > >> > > > practice to > > > > > > >> > > > > > > > > > plan release for 2 months and ask another > > > > > > maintainers about > > > > > > >> > > > > > > > > > >> > > > another modules > > > > > > >> > > > > > > > > > maybe the need additional clarification > from > > > > another > > > > > > >> > > > > > > > > > >> > > > committers. > > > > > > >> > > > > > > > > > > > > > > > >> > > > > > > > > > пн, 23 сент. 2019 г. в 13:35, Nikolay > Izhikov < > > > > > > >> > > > > > > > > > >> > > > nizhi...@apache.org>: > > > > > > >> > > > > > > > > > > > > > > > >> > > > > > > > > > > +1 to start releasing 2.8 in November or > even > > > > in > > > > > > the end > > > > > > >> > of > > > > > > >> > > > > > > > > > >> > > > October. > > > > > > >> > > > > > > > > > > > > > > > > >> > > > > > > > > > > Alex, can we schedule some quick > meetings in > > > > the > > > > > > new > > > > > > >> > Ignite > > > > > > >> > > > > > > > > > >> > > > Slack chat > > > > > > >> > > > > > > > > > > and discuss all release date details? > > > > > > >> > > > > > > > > > > Wendseday, 25 September is good for you? > > > > > > >> > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > >> > > > > > > > > > > В Пн, 23/09/2019 в 13:31 +0300, Maxim > Muzafarov > > > > > > пишет: > > > > > > >> > > > > > > > > > > > Alexey, > > > > > > >> > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > Can you, please, clarify some > questions. > > > > > > >> > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > 1. Currently, the ML module is like a > black > > > > box > > > > > > for me. > > > > > > >> > > > > > > > > > >> > > > What exactly > > > > > > >> > > > > > > > > > > > we are expected to get by the code > freeze > > > > date? > > > > > > Do we > > > > > > >> > have > > > > > > >> > > > > > > > > > >> > > > tickets we > > > > > > >> > > > > > > > > > > > should address to? > > > > > > >> > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > 2. I think we can move code freeze > date to > > > > > > December > > > > > > >> > 11-th > > > > > > >> > > > > > > > > > >> > > > but, from > > > > > > >> > > > > > > > > > > > your side, do you think that 2-weeks of > > > > > > stabilization > > > > > > >> > and > > > > > > >> > > > > > > > > > >> > > > regression > > > > > > >> > > > > > > > > > > > will be enough for the master branch > living > > > > > > without > > > > > > >> > > > > > > > > > >> > > > release for a > > > > > > >> > > > > > > > > > > > year? > > > > > > >> > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > 3. What do you think about that we > will make > > > > the > > > > > > huge > > > > > > >> > 2.8 > > > > > > >> > > > > > > > > > >> > > > release in > > > > > > >> > > > > > > > > > > > November with long period of branch > > > > > > stabilization and > > > > > > >> > an > > > > > > >> > > > > > > > > > >> > > > additional > > > > > > >> > > > > > > > > > > > 2.8.1 release with ML component in > January? > > > > Such > > > > > > an > > > > > > >> > > > > > > > > > >> > > > approach have some > > > > > > >> > > > > > > > > > > > advantages like we will not rush the > > > > development > > > > > > of ML > > > > > > >> > > > > > > > > > >> > > > components. > > > > > > >> > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > On Fri, 20 Sep 2019 at 17:24, Alexey > > > > Zinoviev < > > > > > > >> > > > > > > > > > >> > > > zaleslaw....@gmail.com> > > > > > > >> > > > > > > > > > > > > > > > > >> > > > > > > > > > > wrote: > > > > > > >> > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > I wrote about code freeze at > December 18, > > > > > > 2019, ok, > > > > > > >> > we > > > > > > >> > > > > > > > > > >> > > > can move one > > > > > > >> > > > > > > > > > > > > > > > > >> > > > > > > > > > > week > > > > > > >> > > > > > > > > > > > > earlier to 11 December > > > > > > >> > > > > > > > > > > > > Voting + Release could be after 10th > > > > January. > > > > > > >> > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > пт, 20 сент. 2019 г. в 15:43, Maxim > > > > Muzafarov < > > > > > > >> > > > > > > > > > >> > > > mmu...@apache.org>: > > > > > > >> > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > Alexey, > > > > > > >> > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > It is not a problem to shift > release a > > > > bit > > > > > > later or > > > > > > >> > > > > > > > > > >> > > > earlier, but I'm > > > > > > >> > > > > > > > > > > > > > strictly against having `code > freeze` > > > > stage > > > > > > on > > > > > > >> > > > > > > > > > >> > > > holidays (the > > > > > > >> > > > > > > > > > > > > > > > > >> > > > > > > > > > > Christmas > > > > > > >> > > > > > > > > > > > > > holidays at the end of December > and New > > > > Year > > > > > > >> > holidays > > > > > > >> > > > > > > > > > >> > > > at the > > > > > > >> > > > > > > > > > > > > > > > > >> > > > > > > > > > > beginning > > > > > > >> > > > > > > > > > > > > > of January). From my point, it's > better > > > > to > > > > > > have it > > > > > > >> > > > > > > > > > >> > > > completed `code > > > > > > >> > > > > > > > > > > > > > freeze` stage before December 23th > or > > > > > > started after > > > > > > >> > > > > > > > > > >> > > > 10th January. > > > > > > >> > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > Thoughts? > > > > > > >> > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > On Fri, 20 Sep 2019 at 15:09, > Dmitriy > > > > Pavlov > > > > > > < > > > > > > >> > > > > > > > > > >> > > > dpav...@apache.org> > > > > > > >> > > > > > > > > > > > > > > > > >> > > > > > > > > > > wrote: > > > > > > >> > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > +1 For Maxim as release manager. > > > > > > >> > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > Maxim, > > > > > > >> > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > It is a good thing that you have > > > > committer > > > > > > >> > rights, > > > > > > >> > > > > > > > > > >> > > > and most of > > > > > > >> > > > > > > > > > > > > > > > > >> > > > > > > > > > > the steps > > > > > > >> > > > > > > > > > > > > > > you will be able to complete > yourself. > > > > > > >> > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > But please engage one from PMC > member > > > > to > > > > > > complete > > > > > > >> > > > > > > > > > >> > > > steps from the > > > > > > >> > > > > > > > > > > > > > > > > >> > > > > > > > > > > release > > > > > > >> > > > > > > > > > > > > > > process where PMC rights are > required > > > > > > >> > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > >> > > > > > > > > > >> > > > > > > > > > > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process At > > > > > > >> > > > > > > > > > > > > > > least, access to docker and > nuget creds > > > > > > requires > > > > > > >> > PMC > > > > > > >> > > > > > > > > > >> > > > membership. > > > > > > >> > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > Feel free to ping me, I will > assist, as > > > > > > well. > > > > > > >> > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > Sincerely, > > > > > > >> > > > > > > > > > > > > > > Dmitriy Pavlov > > > > > > >> > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > пт, 20 сент. 2019 г. в 14:59, > Alexey > > > > > > Zinoviev < > > > > > > >> > > > > > > > > > > > > > > > > >> > > > > > > > > > > zaleslaw....@gmail.com>: > > > > > > >> > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > 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? > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > >> > > > > > > > >> > > > > > > >> -- > > > > > > >> BR, Sergey Antonov > > > > > > > > > > > > > > > > > > -- > > Best regards, > > Ivan Pavlukhin >
