Hi all, Can we include https://issues.apache.org/jira/browse/IGNITE-12060? This is a https://issues.apache.org/jira/browse/IGNITE-11953
On Fri, Aug 9, 2019 at 10:04 AM Nikolay Izhikov <nizhi...@apache.org> wrote: > Hello, Deni. > > > Nickolay, could you check if that's a quick upgrade? > > Yes, I will take a look. > > > В Чт, 08/08/2019 в 11:08 -0700, Denis Magda пишет: > > Dmitry, > > > > Please add this BTree corruption fix to the scope: > > https://issues.apache.org/jira/browse/IGNITE-11953 > > > > Plus, I would upgrade our Spark integration to version 2.4 as long as 2.3 > > goes with limitations reported by our users: > > https://issues.apache.org/jira/browse/IGNITE-12054 > > > > Nickolay, could you check if that's a quick upgrade? > > > > - > > Denis > > > > > > On Thu, Aug 8, 2019 at 10:40 AM Dmitriy Pavlov <dpav...@apache.org> > wrote: > > > > > Hi Ivan, Ilya, Igniters, > > > > > > > > > > > > I would like this release would be as minimal as possible. > > > > > > > > > > > > According to dates proposed we could freeze scope at 12.08, 4 days is > more > > > than enough to stand up and say, ‘Hey, I have an urgent fix’. But it is > > > also ok for me if we decide to have more relaxed dates. > > > > > > > > > > > > For now, I suppose the following fixed should be cherry-picked: > > > > > > https://issues.apache.org/jira/browse/IGNITE-11767 (Blocker) > > > GridDhtPartitionsFullMessage retains huge maps on heap in exchange > history > > > > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-10451 (Major Bug) .NET: > > > Persistence does not work with custom affinity function > > > > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-9562 (Critical Bug) > Destroyed > > > cache that resurrected on an old offline node breaks PME > > > > > > > > > > > > But I will continue to research JIRA. > > > > > > > > > > > > Sincerely, > > > > > > Dmitriy Pavlov > > > > > > > > > чт, 8 авг. 2019 г. в 17:30, Павлухин Иван <vololo...@gmail.com>: > > > > > > > > What's the scope for this release? > > > > > > > > Same question. > > > > > > > > On the other hand an idea of 2.7.6 release attracts me because having > > > > a practice of doing frequent minor releases can help us to build > > > > reliable and predictable release rails. > > > > > > > > чт, 8 авг. 2019 г. в 15:09, Ilya Kasnacheev < > ilya.kasnach...@gmail.com>: > > > > > > > > > > Hello! > > > > > > > > > > What's the scope for this release? > > > > > > > > > > Regards, > > > > > -- > > > > > Ilya Kasnacheev > > > > > > > > > > > > > > > чт, 8 авг. 2019 г. в 15:07, Dmitriy Pavlov <dpav...@apache.org>: > > > > > > > > > > > Hi Apache Ignite Developers, > > > > > > > > > > > > > > > > > > > > > > > > We seem to be on the same page about 2.8 release, but we’ve > started > > > > > > new > > > > > > practice - minor releases, the first release was 2.7.5. > > > > > > Unfortunately, > > > > > > there is a couple of issues still not fixed in that release, so I > > > > > > would > > > > > > like to propose to prepare one more minor release for Apache > Ignite. > > > > > > > > > > > > > > > > > > > > > > > > I propose my candidacy to be release manager once again. > > > > > > > > > > > > > > > > > > > > > > > > I could (of course with help from Peter Ivanov) do some > additional > > > > > > > > efforts > > > > > > to complete and improve process doc > > > > > > > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process > > > > > > > > > > > > > > > > > > > > > > > > I propose (most optimistic) dates for release stages: > > > > > > > > > > > > Scope Freeze: August 12, 2019 > > > > > > > > > > > > Code Freeze: August 15, 2019 > > > > > > > > > > > > Voting Date: August 22, 2019 > > > > > > > > > > > > Release Date: August 27, 2019 > > > > > > > > > > > > > > > > > > WDYT? > > > > > > > > > > > > > > > > > > If nobody minds, I will create branch 2.7.6 based on 2.7.5 and > set up > > > > > > > > in > > > > > > the TC Bot during the weekend. > > > > > > > > > > > > > > > > > > > > > > > > Sincerely, > > > > > > > > > > > > Dmitriy Pavlov > > > > > > > > > > > > > > > > > > > > > > -- > > > > Best regards, > > > > Ivan Pavlukhin > > > > >
