Re: Apache Ignite 2.7. Last Mile

Vyacheslav, thank you for remark. I've tried to launch test on the 2.7 version and it is fine. I changed priority of the ticket from "Blocker" to "Major" and fix version to 2.8. пн, 3 дек. 2018 г. в 13:53, Vladimir Ozerov : > Confirming. Test never failed in AI 2.7 even though it contains

Re: Apache Ignite 2.7. Last Mile

Confirming. Test never failed in AI 2.7 even though it contains mentioned MVCC commit. On Mon, Dec 3, 2018 at 1:36 PM Vyacheslav Daradur wrote: > Guys, I checked that `testAtomicOnheapTwoBackupAsyncFullSync` failed > in the master (as described Ivan), but it passes in branch ignite-2.7 > (tag

Re: Apache Ignite 2.7. Last Mile

Guys, I checked that `testAtomicOnheapTwoBackupAsyncFullSync` failed in the master (as described Ivan), but it passes in branch ignite-2.7 (tag 2.7.0-rc2), so this shouldn't block the release. Ivan, were you able to reproduce this issue in ignite-2.7 branch? On Mon, Dec 3, 2018 at 1:03 PM Ivan

Re: Apache Ignite 2.7. Last Mile

Nikolay, I think that end-user may face the problem during call IgniteCache#invoke on a cache with registered continious query if cache's configuration is as in the failed test: [PARTITIONED, ATOMIC, FULL_SYNCH, 2 backups]. I've found that failure has been introduced by MVCC commit [1]. As I

Re: Apache Ignite 2.7. Last Mile

Ivan, please, clarify. How your investigation are related to 2.7 release? Do you think it's a release blocker? If yes, please, describe impact to users and how users can reproduce this issue. пн, 3 дек. 2018 г., 9:30 Ivan Fedotov ivanan...@gmail.com: > I've created the PR

Re: Apache Ignite 2.7. Last Mile

I've created the PR which includes changes just before integration MVCC with Continuous Query and from the TeamCity

Re: Apache Ignite 2.7. Last Mile

Igor, thank you for explanation. Now it seems that when the one thread tries to invoke GridCacheMapEntry#touch, the another one makes GridCacheProcessor#stopCache. If I am wrong, please feel free to correct me. But it still does not clear for me why this fail appears after commit

Re: Apache Ignite 2.7. Last Mile

Nikolay, I couldn't quickly find the root cause of this problem because I'm not an expert in the binary metadata flow. I think community should decide whether this is a release blocker or not. -- Kind Regards Roman Kondakov On 30.11.2018 13:23, Nikolay Izhikov wrote: Hello, Roman. Is

Re: Apache Ignite 2.7. Last Mile

Hello, Roman. Is this issue blocks the 2.7 release? пт, 30 нояб. 2018 г., 13:19 Roman Kondakov kondako...@mail.ru.invalid: > Hi all! > > I've reproduced this problem locally and attached the log to the ticket > in my comment [1]. > > As Igor noted, NPE there is caused by node stop in the end of

Re: Apache Ignite 2.7. Last Mile

Hi all! I've reproduced this problem locally and attached the log to the ticket in my comment [1]. As Igor noted, NPE there is caused by node stop in the end of the test. The real problem here seems to be in the binary metadata registration flow. [1]

Re: Apache Ignite 2.7. Last Mile

Null pointer there due to cache stop. Look at GridCacheContext#cleanup (GridCacheContext.java:2050) which is called by GridCacheProcessor#stopCache (GridCacheProcessor.java:1372) That's why at the time GridCacheMapEntry#touch (GridCacheMapEntry.java:5063) invoked there is no eviction manager.

Re: Apache Ignite 2.7. Last Mile

Ivan. Please, provide a link for a ticket with NPE stack trace attached. I've looked at IGNITE-10376 and can't see any attachments. пт, 30 нояб. 2018 г., 10:14 Ivan Fedotov ivanan...@gmail.com: > Igor, > NPE is available in a full log, now I also attached it in the ticket. > > IGNITE-7953 > < >

Re: Apache Ignite 2.7. Last Mile

Igor, NPE is available in a full log, now I also attached it in the ticket. IGNITE-7953 was commited on the 15 October. I could not take a look on the testAtomicOnheapTwoBackupAsyncFullSync before this date,

Re: Apache Ignite 2.7. Last Mile

Ivan, Could you provide a bit more details? I don't see any NPE among all available logs. I don't think the issue is caused by changes in scope of IGNITE-7953. The test fails both before

Re: Apache Ignite 2.7. Last Mile

Denis, It looks like the failing test is related to existing ATOMIC caches but it was broken by the MVCC commit, so it is a regression. Let's wait for Vladimir Ozerov or Igor Seliverstov to comment. чт, 29 нояб. 2018 г. в 19:32, Nikolay Izhikov : > Hello, Denis. > > Nothing blocks now. > I

Re: Apache Ignite 2.7. Last Mile

Hello, Denis. Nothing blocks now. I preparing vote artifacts right now. There are some issues with TC tasks. I think I resolve them in a couple of hours. чт, 29 нояб. 2018 г., 19:30 Denis Magda dma...@apache.org: > I think that it's not a blocker since MVCC is in the beta state and some of >

Re: Apache Ignite 2.7. Last Mile

I think that it's not a blocker since MVCC is in the beta state and some of the APIs might not work well with it yet. Apart from that, are we done with the stabilization and ready to start the vote? What blocks us from that? -- Denis On Thu, Nov 29, 2018 at 7:43 AM Yakov Zhdanov wrote: >

Re: Apache Ignite 2.7. Last Mile

Vladimir, can you please take a look at https://issues.apache.org/jira/browse/IGNITE-10376? --Yakov

Re: Apache Ignite 2.7. Last Mile

Hello Igniters. During my work at the ticket IGNITE-10376 I found that it started to fail after integration Continuous Query with MVCC. I launched CacheContinuousQueryOrderingEventTest.testAtomicOnheapTwoBackupAsyncFullSync before

Re: Apache Ignite 2.7. Last Mile

Fixed. Thank you for noting it. On Wed, Nov 28, 2018 at 6:22 AM Alexey Kuznetsov wrote: > Hi, > > We found a regression https://issues.apache.org/jira/browse/IGNITE-10432 > > Please take a look. > > -- > Alexey Kuznetsov >

Re: Apache Ignite 2.7. Last Mile

Hi, We found a regression https://issues.apache.org/jira/browse/IGNITE-10432 Please take a look. -- Alexey Kuznetsov

Re: Apache Ignite 2.7. Last Mile

Hello, Igniters. Changes regarding to GridToStringBuilder reverted in ignite-2.7 branch: * IGNITE-8493 * IGNITE-9209 * IGNITE-602 We have 1 ticket for 2.7: IGNITE-10393: DataStreamer failed with NPE for MVCC caches which is unassigned. Who can fix it? В Вт, 20/11/2018 в 12:38 +0300, Dmitrii

Re: Apache Ignite 2.7. Last Mile

Yes, revert both. вт, 20 нояб. 2018 г., 11:52 Vladimir Ozerov voze...@gridgain.com: > +1 for reverting both. > > On Tue, Nov 20, 2018 at 9:43 AM Nikolay Izhikov > wrote: > > > Hello, Dmitrii. > > > > I see 2 tickets for this improvement: > > > > IGNITE-602 - [Test] GridToStringBuilder is

Re: Apache Ignite 2.7. Last Mile

+1 for reverting both. On Tue, Nov 20, 2018 at 9:43 AM Nikolay Izhikov wrote: > Hello, Dmitrii. > > I see 2 tickets for this improvement: > > IGNITE-602 - [Test] GridToStringBuilder is vulnerable for > StackOverflowError caused by infinite recursion [1] > IGNITE-9209 -

Re: Apache Ignite 2.7. Last Mile

Hello, Dmitrii. I see 2 tickets for this improvement: IGNITE-602 - [Test] GridToStringBuilder is vulnerable for StackOverflowError caused by infinite recursion [1] IGNITE-9209 - GridDistributedTxMapping.toString() returns broken string [2] Should we revert both commits? [1]

Re: Apache Ignite 2.7. Last Mile

I agree to revert and make fix for 2.8. So, we will have more time to test it. пн, 19 нояб. 2018 г., 10:53 Vladimir Ozerov voze...@gridgain.com: > +1 for revert. > > On Sun, Nov 18, 2018 at 11:31 PM Dmitriy Pavlov > wrote: > > > I personally don't mind. > > > > But I would like Dmitry Ryabov

Re: Apache Ignite 2.7. Last Mile

+1 for revert. On Sun, Nov 18, 2018 at 11:31 PM Dmitriy Pavlov wrote: > I personally don't mind. > > But I would like Dmitry Ryabov and Alexey Goncharuck share their opinions. > > вс, 18 нояб. 2018 г., 20:43 Nikolay Izhikov : > > > Yes, I think so. > > > > вс, 18 нояб. 2018 г., 20:34 Denis

Re: Apache Ignite 2.7. Last Mile

I personally don't mind. But I would like Dmitry Ryabov and Alexey Goncharuck share their opinions. вс, 18 нояб. 2018 г., 20:43 Nikolay Izhikov : > Yes, I think so. > > вс, 18 нояб. 2018 г., 20:34 Denis Magda dma...@apache.org: > > > Sounds good to me. Are we starting the vote then? > > > >

Re: Apache Ignite 2.7. Last Mile

Yes, I think so. вс, 18 нояб. 2018 г., 20:34 Denis Magda dma...@apache.org: > Sounds good to me. Are we starting the vote then? > > Denis > > > > On Sun, Nov 18, 2018 at 8:25 AM Nikolay Izhikov > wrote: > > > Hello, Igniters. > > > > This issue is the only ticket that blocks 2.7 release. > > >

Re: Apache Ignite 2.7. Last Mile

Sounds good to me. Are we starting the vote then? Denis On Sun, Nov 18, 2018 at 8:25 AM Nikolay Izhikov wrote: > Hello, Igniters. > > This issue is the only ticket that blocks 2.7 release. > > I looked at IGNITE-602 PR and GridToStringBuilder. > The code looks complicated for me. > And it's

Re: Apache Ignite 2.7. Last Mile

Ok, I'll check the issue. пт, 16 нояб. 2018 г. в 17:52, Alexey Goncharuk : > > Igniters, > > I've just found that S.toString() implementation is broken in ignite-2.7 and > master [1]. It leads to a message > Wrapper [p=Parent [a=0]Child [b=0, super=]] > being formed instead of > Wrapper [p=Child

Re: Apache Ignite 2.7. Last Mile

Igniters, I've just found that S.toString() implementation is broken in ignite-2.7 and master [1]. It leads to a message *Wrapper [p=Parent [a=0]Child [b=0, super=]]* being formed instead of *Wrapper [p=Child [b=0, super=Parent [a=0]]]* for classes with inheritance that use

Re: Apache Ignite 2.7. Last Mile

Hello, Igniters. We still have 5 tickets for 2.7: IGNITE-10052Andrew Mashenkov Restart node during TX causes vacuum error. IGNITE-10170Unassigned .NET: Services.ServicesTestAsync fails IGNITE-10196Maxim Pudov Remove kafka-clients-*-test dependency IGNITE-10154Andrey

Re: Apache Ignite 2.7. Last Mile

I'm OK with this. чт, 8 нояб. 2018 г., 13:44 Andrey Gura ag...@apache.org: > Long, long way to release :) > > Guys, we have a breaking change in Ignite 2.7 so we must add > IGNITE-10154 [1] fix to the release. > > [1] https://issues.apache.org/jira/browse/IGNITE-10154 > On Tue, Nov 6, 2018 at

Re: Apache Ignite 2.7. Last Mile

Long, long way to release :) Guys, we have a breaking change in Ignite 2.7 so we must add IGNITE-10154 [1] fix to the release. [1] https://issues.apache.org/jira/browse/IGNITE-10154 On Tue, Nov 6, 2018 at 6:30 PM Igor Sapego wrote: > > Guys, > > I've found the following issue: [1]. It is quite

Re: Apache Ignite 2.7. Last Mile

Guys, I've found the following issue: [1]. It is quite local (only affects Ignite C++ Linux build system) but quite critical too. I think it should be included in 2.7. What do you think? [1] - https://issues.apache.org/jira/browse/IGNITE-10147 Best Regards, Igor On Tue, Oct 30, 2018 at 4:35

Re: Apache Ignite 2.7. Last Mile

Hello Nikolay, Igniters, It seems that we lost the following commit that should be included in 'ignite-2.7' branch (It looks like the change was not accidentally cherry-picked from 'master' to 'ignite-2.7') - https://github.com/apache/ignite/commit/6e0ff06f8e309657a16c94da605348d9c3b804ad The

Re: Apache Ignite 2.7. Last Mile

Hello, guys. For today we have 11 tickets mapped to 2.7 IGNITE-10010 Alexey Goncharuk Node halted if second node was stopped, then cache destroyed, then second node returned IGNITE-10015 Alexey Goncharuk Sporadic JVM crash due to restart nodes IGNITE-10013 Unassigned Node restart may lead to NPE

Re: Apache Ignite 2.7. Last Mile

Hi Nikolay, I do not know. We need to investigate them first. These are all regressions, so decision about impact and urgency should be made separately for every ticket. On Fri, Oct 26, 2018 at 9:57 AM Nikolay Izhikov wrote: > Hello, Igniters. > > We have *9* tickets mapped to 2.7 today > >

Re: Apache Ignite 2.7. Last Mile

Hello, Igniters. We have *9* tickets mapped to 2.7 today Vladimir, do you think 1 week delay will be enough to resolve all this tickets? IGNITE-9828 Roman Kondakov MVCC: Continuous query failover. IGNITE-9928 Igor SeliverstovMVCC TX: Late affinity assignment support.

Re: Apache Ignite 2.7. Last Mile

Hello, Igniters. We have 3 ticket mapped to 2.7 today: Igor Seliverstov - IGNITE-9892 - MVCC: Exchange hangs on mvcc coordinator fail Roman Kondakov - IGNITE-9828 - MVCC: Continuous query failover. Roman Kondakov - IGNITE-9928 - MVCC TX: Bug in SQL query mapping. В Вт, 23/10/2018 в 15:01

Re: Apache Ignite 2.7. Last Mile

Hello, Dmitriy. I'm OK with including this patch to 2.7. Can you ensure it completely fix the issue? I left comment in ticket. https://issues.apache.org/jira/browse/IGNITE-9854?focusedCommentId=16660516=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16660516 В Вт,

Re: Apache Ignite 2.7. Last Mile

Nikolay, I have an issue which I want to include in 2.7 release, https://issues.apache.org/jira/browse/IGNITE-9854 It is a very small fix but very important, it protects us from NPE in some race scenario. Changes already in master, but the issue still not resolve, need your approval for

Re: Apache Ignite 2.7. Last Mile

Igniters, There are still tickets in the scope as we continue finding new issues during QA. I propose the following plan: if there are still opened issues by Friday, then shift vote date for 1 week, to 2nd November. This is needed to ensure that product quality is sufficient. But if the backlog

Re: Apache Ignite 2.7. Last Mile

Hello, Igniters. We have 7 tickets mapped to 2.7 today. Igov Seliverstov - IGNITE-9892 - MVCC: Exchange hangs on mvcc coordinator fail Igor Seliverstov - IGNITE-9911 - CacheMvccSelectForUpdateQueryAbstractTest#testSelectForUpdateAfterAbortedTx periodically hangs Roman Kondakov-

Re: Apache Ignite 2.7. Last Mile

Hell, Denis. I just filter all 2.7 tickets without documentation.

Re: Apache Ignite 2.7. Last Mile

Nikolay, Where do you track those 8 blockers? Can't find them on this wiki page: https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.7 -- Denis On Sat, Oct 20, 2018 at 11:31 AM Nikolay Izhikov wrote: > Hello, Denis. > > As a first time release manager I'm trying to rely on

Re: Apache Ignite 2.7. Last Mile

Hello, Denis. As a first time release manager I'm trying to rely on Ignite veterans opinion. Guys told me that we must fix all blockers and only after it make the release. Let's fix them all. What do you think? > When are we sending a release candidate for vote? When all blocker bugs will be

Re: Apache Ignite 2.7. Last Mile

Guys, as a side observer of the current release, this all looks like a never ending story :) When are we sending a release candidate for vote? -- Denis On Fri, Oct 19, 2018 at 4:39 AM Nikolay Izhikov wrote: > Hello, Igniters. > > We have 6 tickets for 2.7 > > Roman Kondakov - IGNITE-9892,

Re: Apache Ignite 2.7. Last Mile

Hello, Igniters. We have 6 tickets for 2.7 Roman Kondakov - IGNITE-9892, IGNITE-9663, IGNITE-9928 Igor Seliverstov - IGNITE-9911 Ivan Pavlukhin - IGNITE-5935, IGNITE-9944 В Чт, 18/10/2018 в 15:40 +0300, Andrey Kuznetsov пишет: > I have got one more potential 2.7 blocker [1] with straightforward

Re: Apache Ignite 2.7. Last Mile

I have got one more potential 2.7 blocker [1] with straightforward fix. I beleive it will not break any production use case, but it leads to test suite hang, thus affecting other urgent issues. [1] https://issues.apache.org/jira/browse/IGNITE-9932 чт, 18 окт. 2018 г. в 14:59, Ivan Daschinsky :

Re: Apache Ignite 2.7. Last Mile

Hi! Is it possible to merge IGNITE-9854? Fix is pretty simple, but quite important. ср, 17 окт. 2018 г. в 17:49, Andrey Gura : > JFYI > > IGNITE-9737 and IGNITE-9710 are merged to release branch. > On Wed, Oct 17, 2018 at 5:41 PM Pavel Tupitsyn > wrote: > > > > Thank you. Fix has been merged to

Re: Apache Ignite 2.7. Last Mile

JFYI IGNITE-9737 and IGNITE-9710 are merged to release branch. On Wed, Oct 17, 2018 at 5:41 PM Pavel Tupitsyn wrote: > > Thank you. Fix has been merged to master and cherry-picked to ignite-2.7. > > On Wed, Oct 17, 2018 at 1:26 PM Nikolay Izhikov wrote: > > > Pavel. > > > > Ok, I agree to

Re: Apache Ignite 2.7. Last Mile

Thank you. Fix has been merged to master and cherry-picked to ignite-2.7. On Wed, Oct 17, 2018 at 1:26 PM Nikolay Izhikov wrote: > Pavel. > > Ok, I agree to include this ticket into 2.7 > Let's do it. > > В Ср, 17/10/2018 в 13:20 +0300, Pavel Tupitsyn пишет: > > Nikolay, > > > > It completely

Re: Apache Ignite 2.7. Last Mile

Pavel. Ok, I agree to include this ticket into 2.7 Let's do it. В Ср, 17/10/2018 в 13:20 +0300, Pavel Tupitsyn пишет: > Nikolay, > > It completely breaks a major feature under certain conditions. I would > consider it a blocker. > > On Wed, Oct 17, 2018 at 1:00 PM Nikolay Izhikov wrote: > >

Re: Apache Ignite 2.7. Last Mile

Nikolay, It completely breaks a major feature under certain conditions. I would consider it a blocker. On Wed, Oct 17, 2018 at 1:00 PM Nikolay Izhikov wrote: > Hello, Pavel. > > Is it a blocker? > > В Ср, 17/10/2018 в 12:58 +0300, Pavel Tupitsyn пишет: > > Hi Igniters, > > > > I'd like to

Re: Apache Ignite 2.7. Last Mile

Hello, Pavel. Is it a blocker? В Ср, 17/10/2018 в 12:58 +0300, Pavel Tupitsyn пишет: > Hi Igniters, > > I'd like to include IGNITE-9877 in 2.7, can we do that? > The fix is ready, I'm waiting for TC run. > > Pavel > > On Wed, Oct 17, 2018 at 11:45 AM Павлухин Иван wrote: > > > Hi NIkolay, >

Re: Apache Ignite 2.7. Last Mile

Hi Igniters, I'd like to include IGNITE-9877 in 2.7, can we do that? The fix is ready, I'm waiting for TC run. Pavel On Wed, Oct 17, 2018 at 11:45 AM Павлухин Иван wrote: > Hi NIkolay, > > Thank you for keeping everybody focused! Regarding to my ticket > IGNITE-5935. > It is in final stage

Re: Apache Ignite 2.7. Last Mile

Hi NIkolay, Thank you for keeping everybody focused! Regarding to my ticket IGNITE-5935. It is in final stage now. Tests look good. I believe that it will be merged in couple of days (at most). ср, 17 окт. 2018 г. в 11:39, Nikolay Izhikov : > Hello, Igniters. > > 9 tickets to go! > > Alexey

Re: Apache Ignite 2.7. Last Mile

Hello, Igniters. 9 tickets to go! Alexey Goncharuk - IGNITE-9784 Dmitriy Govorukhin - IGNITE-9898 Andrey Kuznetsov - IGNITE-9737, IGNITE-9710 Taras Ledkov - IGNITE-9882 Petr Ivanov - IGNITE-9852 Ivan Pavlukhin - IGNITE-5935 Roman Kondakov - IGNITE-9663 Alexey Stelmak - IGNITE-9776 В

Re: Apache Ignite 2.7. Last Mile

Hi, I've found that IGNITE-9723 was resolved but didn't cherry picked to ignite-2.7 branch. So I'll do it. On Tue, Oct 16, 2018 at 2:30 PM Nikolay Izhikov wrote: > > Hello, Igniters. > > We have 13 tickets mapped to 2.7. > All tickets assigned to some contributor. > > Alexey Gonchruk -

Re: Apache Ignite 2.7. Last Mile

Hello, Igniters. We have 13 tickets mapped to 2.7. All tickets assigned to some contributor. Alexey Gonchruk - IGNITE-9784, IGNITE-9895 Vladimir Ozerov - IGNITE-9887 Dmitriy Govorukhin - IGNITE-9898 Andrey Kuznetsov - IGNITE-9737, IGNITE-9710 Petr Ivanov - IGNITE-9852 Ivan Pavlukhin -

Re: Apache Ignite 2.7. Last Mile

Nikolay, I'm looking at IGNITE-9737 and IGNITE-9710 which are critical issues from my point of view. I need some time for review, possible fixes and merge. I will keep you informed. On Mon, Oct 15, 2018 at 1:46 PM Igor Sapego wrote: > > Guys, Python client is in the master and ignite-2.7

Re: Apache Ignite 2.7. Last Mile

Guys, Python client is in the master and ignite-2.7 already. Best Regards, Igor On Mon, Oct 15, 2018 at 11:33 AM Vladimir Ozerov wrote: > Nikolay, > > AI 2.7 will include Python thin client. TC suite is crucial part of this > feature, so we should keep the ticket in AI 2.7 scope. > > On Mon,

Re: Apache Ignite 2.7. Last Mile

Nikolay, AI 2.7 will include Python thin client. TC suite is crucial part of this feature, so we should keep the ticket in AI 2.7 scope. On Mon, Oct 15, 2018 at 10:57 AM Nikolay Izhikov wrote: > Hello, Igniters. > > There is no progress till Friday. > We have 14 tickets mapped to 2.7. > > В

Re: Apache Ignite 2.7. Last Mile

Hello, Igniters. There is no progress till Friday. We have 14 tickets mapped to 2.7. В Пт, 12/10/2018 в 08:29 +0300, Nikolay Izhikov пишет: > Hello, Igniters. > > We made some progress yesterday. > > Please, note, we have 1 new ticket mapped to 2.7 "IGNITE-9852: Create > TeamCity suite for

Re: Apache Ignite 2.7. Last Mile

Hello, Igniters. We made some progress yesterday. Please, note, we have 1 new ticket mapped to 2.7 "IGNITE-9852: Create TeamCity suite for Python thin client" This ticket doesn't sound like a blocker to me. Let's exclude it from release scope. Thoughts? Here is the list of remaining

Re: Apache Ignite 2.7. Last Mile

Alexey, we all agreed to merge in 2.7 blockers only. Is this a blocker? Anyway, you are more experienced Igniter that I am. If you think we should include this ticket to 2.7 - please, do it. В Чт, 11/10/2018 в 13:08 +0300, Alexey Goncharuk пишет: > Nikolay, > > I am waiting for final benchmark

Re: Apache Ignite 2.7. Last Mile

Nikolay, I am waiting for final benchmark results for 9784, after that I will merge the change. On the subject of Ignite 2.7 scope, our fellow Igniter Alexey Platonov have found another case when a failure handler is incorrectly called on node stop:

Re: Apache Ignite 2.7. Last Mile

Hello, Igniters. We made a good progress yesterday. Here is the list of remaining tickets(17) mapped to 2.7: Alexey Goncharuk - IGNITE-9784 Taras Ledkov - IGNITE-9171 Andrey Kuznetsov - IGNITE-9737, IGNITE-9710 Peter Ivanov - IGNITE-9583, IGNITE-9823, IGNITE-9685 Igor

Re: Apache Ignite 2.7. Last Mile

What kind of help is needed? On Wed, Oct 10, 2018 at 11:51 PM Dmitriy Setrakyan wrote: > Vladimir Ozerov, > > Can you help with the unassigned MVCC tickets? > > D. > > On Wed, Oct 10, 2018 at 3:32 AM Nikolay Izhikov > wrote: > > > Hello, Igniters. > > > > I list all contributors that assigned

Re: Apache Ignite 2.7. Last Mile

Vladimir Ozerov, Can you help with the unassigned MVCC tickets? D. On Wed, Oct 10, 2018 at 3:32 AM Nikolay Izhikov wrote: > Hello, Igniters. > > I list all contributors that assigned to the 2.7 tickets. > If you can help them to finish that tickets - please, do. > Assigners, if you need any