From dev-return-45716-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Mon Apr 15 15:39:34 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 89EB918064C for ; Mon, 15 Apr 2019 17:39:34 +0200 (CEST) Received: (qmail 60280 invoked by uid 500); 15 Apr 2019 15:39:33 -0000 Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list dev@ignite.apache.org Received: (qmail 60269 invoked by uid 99); 15 Apr 2019 15:39:33 -0000 Received: from Unknown (HELO mailrelay1-lw-us.apache.org) (10.10.3.159) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Apr 2019 15:39:33 +0000 Received: from mail-qk1-f177.google.com (mail-qk1-f177.google.com [209.85.222.177]) by mailrelay1-lw-us.apache.org (ASF Mail Server at mailrelay1-lw-us.apache.org) with ESMTPSA id A20339A11 for ; Mon, 15 Apr 2019 15:39:29 +0000 (UTC) Received: by mail-qk1-f177.google.com with SMTP id a71so10132234qkg.2 for ; Mon, 15 Apr 2019 08:39:29 -0700 (PDT) X-Gm-Message-State: APjAAAWOJ6zGmm39cFIR+VDmdHmFIauJf7z/bLG16BIx4qfH8lDcBWXc W4LV3FOfFsoYHwrVzzXKL6G9nRGKgxGje4r+5Zo= X-Google-Smtp-Source: APXvYqz3puhkqeavPLJ27ofuygBAVeUV65mjSA6e1beiS8HVkjbmt1EhswBW4YxtOm88vmA4JosEM0gJyHPpP61avDg= X-Received: by 2002:a37:c15:: with SMTP id 21mr56439892qkm.50.1555342769167; Mon, 15 Apr 2019 08:39:29 -0700 (PDT) MIME-Version: 1.0 References: <1553598474.845418022@f548.i.mail.ru> <2088013353.12659243.1553735904201@mail.yahoo.com> In-Reply-To: From: Dmitriy Pavlov Date: Mon, 15 Apr 2019 18:39:17 +0300 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Ignite 2.7.5 Release scope To: dev Content-Type: multipart/alternative; boundary="00000000000042a26a0586937510" --00000000000042a26a0586937510 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Igniters, Unfortunately, Ignite C++ examples cannot build without https://issues.apache.org/jira/browse/IGNITE-11195 So this issue should be included in the scope. Sincerely, Dmitriy Pavlov =D0=BF=D1=82, 12 =D0=B0=D0=BF=D1=80. 2019 =D0=B3. =D0=B2 13:53, Dmitriy Pav= lov : > Hi Igniters, > > A bit of update: Last change fixing GridUnsafe for Java 12 was merged to > master and to 2.7.5 > > Overnight run contains a number of failures considered as blockers by > Apache Ignite Teamcity Bot (comparing to 2.7): > - Platform .NET (Inspections) always failed- Critical F.R.: 100,0% > - Platform C++ (Linux Clang) & Platform C++ (Linux)* failed in most cases > - Critical F.R.: 60,0% > - Disk Page Compressions - Module is N/A in 2.7.5 > - [Inspections] Core - always failed > - Hibernate 5.3 - Module is N/A in 2.7.5 > - Platform C++ (Win x64 | Release) - also failed in 2.7 > > And 2 more tests failure considered as blockers (now it is in re-run > state). If re-run shows these tests are passing I proceed with RC > preparation. > > Sincerely, > Dmitriy Pavlov > > =D0=B2=D1=82, 9 =D0=B0=D0=BF=D1=80. 2019 =D0=B3. =D0=B2 10:03, Dmitriy Pa= vlov : > >> Hi, Nikolay, >> >> thanks for offering help. >> >> Performance testing of new fix seems to be almost done. >> >> After merging of the last ticket (I hope it will be tomorrow) I will >> continue with RC building. There can be some issues related to scripts. >> >> Sincerely, >> Dmitriy Pavlov >> >> =D0=B2=D1=82, 9 =D0=B0=D0=BF=D1=80. 2019 =D0=B3. =D0=B2 09:53, Nikolay I= zhikov : >> >>> Hello, Dmitriy. >>> >>> Any news about release? >>> Do you need assistance with it? >>> >>> =D0=B2=D1=82, 2 =D0=B0=D0=BF=D1=80. 2019 =D0=B3. =D0=B2 20:04, Dmitriy = Pavlov : >>> >>> > Ivan P., it seems the netty approach you've proposed works well. Than= k >>> you. >>> > >>> > Igniters, please take a look at following fix: >>> > https://github.com/apache/ignite/pull/6384 >>> > It allows us to start under Java 12 and under Java 11- (as it). >>> > >>> > Sincerely, >>> > Dmitriy Pavlov >>> > >>> > =D0=BF=D1=82, 29 =D0=BC=D0=B0=D1=80. 2019 =D0=B3. =D0=B2 22:57, Dmitr= iy Pavlov : >>> > >>> > > Denis, the issue here is that we don't know for sure. We see just o= ne >>> > > blocking issue with accessing NioAccessObject. >>> > > >>> > > And there are 3 different scenario related to this issue fix: >>> > > - fixes won't help, and we should find out other options on how to >>> create >>> > > a direct buffer from pointer - needed for durable memory, Java 12 >>> goes >>> > to a >>> > > later release. >>> > > - some fix would help, but other issues come, Java 12 goes to some >>> later >>> > > release >>> > > - some from proposed fixes works, nothing else needs to be done - 1= -2 >>> > days >>> > > >>> > > If it latest scenario, I would include as much as we can (1-2 days >>> extra >>> > > are comparable with minimal voting time). >>> > > >>> > > BTW, I've checked scripts it does not work for me, I will ask Andre= y >>> > > G/Peter for advice on Monday. >>> > > >>> > > Sincerely, >>> > > Dmitriy Pavlov >>> > > >>> > > >>> > > =D0=BF=D1=82, 29 =D0=BC=D0=B0=D1=80. 2019 =D0=B3. =D0=B2 20:47, Den= is Magda : >>> > > >>> > >> Folks, >>> > >> >>> > >> What are the efforts to support Java 12? Let's do 2.7.6 shortly if >>> the >>> > >> fixes are time-consuming. >>> > >> >>> > >> - >>> > >> Denis >>> > >> >>> > >> >>> > >> On Fri, Mar 29, 2019 at 10:08 AM Dmitriy Pavlov >> > >>> > >> wrote: >>> > >> >>> > >> > Hi Igniters, >>> > >> > >>> > >> > I would like to announce code freeze for 2.7.5. Only one open >>> ticket >>> > is >>> > >> > there (reopened): >>> https://issues.apache.org/jira/browse/IGNITE-11600 >>> > >> (if >>> > >> > we >>> > >> > can't start using Java 12 we should clearly state it in >>> scripts/code). >>> > >> > >>> > >> > We're entering to Stabilization phase for >>> > >> > >>> > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.7.= 5 >>> > >> and >>> > >> > only blockers may be included into scope. See >>> > >> > >>> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process >>> > for >>> > >> > more >>> > >> > details. >>> > >> > >>> > >> > Sincerely, >>> > >> > Dmitriy Pavlov >>> > >> > >>> > >> > =D0=BF=D1=82, 29 =D0=BC=D0=B0=D1=80. 2019 =D0=B3. =D0=B2 13:51, = Dmitriy Pavlov : >>> > >> > >>> > >> > > Hi Denis, >>> > >> > > >>> > >> > > I'm not talking about months. In this discussion, Andrey and >>> Ivan >>> > >> > proposed >>> > >> > > a couple of fixes that may help. >>> > >> > > >>> > >> > > It will require a day or two to check if it helps. If it not >>> helpful >>> > >> then >>> > >> > > we should modify startup scripts to say clearly that Java 12 i= s >>> not >>> > >> > > supported. >>> > >> > > >>> > >> > > Now under Java 12 Ignite suggests to set startup parameters, b= ut >>> > even >>> > >> > with >>> > >> > > correct parameters, it fails and says please set parameters. >>> Totally >>> > >> > > unclear for end-user. >>> > >> > > >>> > >> > > I've reopened >>> https://issues.apache.org/jira/browse/IGNITE-11600 >>> > >> > > >>> > >> > > Sincerely, >>> > >> > > Dmitriy Pavlov >>> > >> > > >>> > >> > > =D1=87=D1=82, 28 =D0=BC=D0=B0=D1=80. 2019 =D0=B3. =D0=B2 18:51= , Denis Magda : >>> > >> > > >>> > >> > >> If the failure handler improvements will lower down a number = of >>> > >> > >> false-positive cluster shutdowns then I'm for the fix >>> inclusion to >>> > >> the >>> > >> > >> release. >>> > >> > >> >>> > >> > >> As for Java 12, I would put to the next release that we can >>> make >>> > >> shortly >>> > >> > >> after this one. We don't need to wait for months if there are >>> some >>> > >> > urgent >>> > >> > >> fixes. >>> > >> > >> >>> > >> > >> - >>> > >> > >> Denis >>> > >> > >> >>> > >> > >> >>> > >> > >> On Thu, Mar 28, 2019 at 8:46 AM Dmitriy Pavlov < >>> dpavlov@apache.org >>> > > >>> > >> > >> wrote: >>> > >> > >> >>> > >> > >> > Denis, I also +1 for python fix. Today is the planned date = of >>> > code >>> > >> > >> freeze, >>> > >> > >> > so today or tomorrow I'll announce it. >>> > >> > >> > >>> > >> > >> > Only one thing was suggested is the fix for failure >>> handlers. I >>> > >> don't >>> > >> > >> > deeply understand the pros and cons, but I'm sure we should >>> > >> courteous >>> > >> > >> > enough for wait experienced folks to come to a consensus. >>> > >> > >> > >>> > >> > >> > One more thing I suggest to check after code freeze, it is >>> Java >>> > >> 12. It >>> > >> > >> does >>> > >> > >> > not work now, but with thanks to Andrey G and Ivan P. we >>> probably >>> > >> have >>> > >> > >> not >>> > >> > >> > very complex solution for this. >>> > >> > >> > >>> > >> > >> > So these 2 fixes are last candidates to come to scope. WDYT= ? >>> > >> > >> > >>> > >> > >> > Sincerely, >>> > >> > >> > Dmitriy Pavlov >>> > >> > >> > >>> > >> > >> > =D1=87=D1=82, 28 =D0=BC=D0=B0=D1=80. 2019 =D0=B3. =D0=B2 18= :10, Denis Magda >> >: >>> > >> > >> > >>> > >> > >> > > Yes, the Python example's fix makes sense - that's a >>> usability >>> > >> issue >>> > >> > >> and >>> > >> > >> > > doesn't affect the core components. >>> > >> > >> > > >>> > >> > >> > > In general, I would suggest us to do a code freeze and pu= sh >>> > other >>> > >> > >> changes >>> > >> > >> > > to another release. We can't include everything. >>> > >> > >> > > >>> > >> > >> > > - >>> > >> > >> > > Denis >>> > >> > >> > > >>> > >> > >> > > >>> > >> > >> > > On Thu, Mar 28, 2019 at 3:01 AM Ilya Kasnacheev < >>> > >> > >> > ilya.kasnacheev@gmail.com >>> > >> > >> > > > >>> > >> > >> > > wrote: >>> > >> > >> > > >>> > >> > >> > > > Hello! >>> > >> > >> > > > >>> > >> > >> > > > How about adding >>> > >> > https://issues.apache.org/jira/browse/IGNITE-11366 >>> > >> > >> > > which >>> > >> > >> > > > fixes Python's release directory? >>> > >> > >> > > > >>> > >> > >> > > > I have stumbled on this issue personally. >>> > >> > >> > > > >>> > >> > >> > > > Regards, >>> > >> > >> > > > -- >>> > >> > >> > > > Ilya Kasnacheev >>> > >> > >> > > > >>> > >> > >> > > > >>> > >> > >> > > > =D1=87=D1=82, 28 =D0=BC=D0=B0=D1=80. 2019 =D0=B3. =D0= =B2 04:19, Roman Shtykh >>> > >> > >> > >> > >> >: >>> > >> > >> > > > >>> > >> > >> > > > > Dmitriy, the probability of having nodes down with >>> these >>> > bugs >>> > >> > >> under >>> > >> > >> > > heavy >>> > >> > >> > > > > load conditions is pretty high. Good candidate for >>> > >> > cherry-picking. >>> > >> > >> > > > > >>> > >> > >> > > > > [1] >>> https://issues.apache.org/jira/browse/IGNITE-9803[2] >>> > >> > >> > > > > https://issues.apache.org/jira/browse/IGNITE-11127 >>> > >> > >> > > > > -- Roman >>> > >> > >> > > > > >>> > >> > >> > > > > >>> > >> > >> > > > > On Wednesday, March 27, 2019, 2:11:49 a.m. GMT+9, >>> > Dmitriy >>> > >> > >> Pavlov >>> > >> > >> > < >>> > >> > >> > > > > dpavlov@apache.org> wrote: >>> > >> > >> > > > > >>> > >> > >> > > > > Hi, >>> > >> > >> > > > > >>> > >> > >> > > > > I've cherry-picked this commit. It seems it is critic= al >>> > >> because >>> > >> > it >>> > >> > >> > also >>> > >> > >> > > > > fixes storage corruption. >>> > >> > >> > > > > >>> > >> > >> > > > > Sincerely, >>> > >> > >> > > > > Dmitriy Pavlov >>> > >> > >> > > > > >>> > >> > >> > > > > =D0=B2=D1=82, 26 =D0=BC=D0=B0=D1=80. 2019 =D0=B3. =D0= =B2 14:14, Zhenya Stanilovsky >>> > >> > >> > > > >> > >> > >> > > > > >: >>> > >> > >> > > > > >>> > >> > >> > > > > > I suppose this ticket [1] : is very useful too. >>> > >> > >> > > > > > >>> > >> > >> > > > > > >>> > >> > >> > > > > > [1] >>> https://issues.apache.org/jira/browse/IGNITE-10873 [ >>> > >> > >> > > > > > CorruptedTreeException during simultaneous cache pu= t >>> > >> > operations >>> > >> > >> ] >>> > >> > >> > > > > > >>> > >> > >> > > > > > > >>> > >> > >> > > > > > > >>> > >> > >> > > > > > >------- Forwarded message ------- >>> > >> > >> > > > > > >From: "Alexey Goncharuk" < >>> alexey.goncharuk@gmail.com > >>> > >> > >> > > > > > >To: dev < dev@ignite.apache.org > >>> > >> > >> > > > > > >Cc: >>> > >> > >> > > > > > >Subject: Re: Ignite 2.7.5 Release scope >>> > >> > >> > > > > > >Date: Tue, 26 Mar 2019 13:42:59 +0300 >>> > >> > >> > > > > > > >>> > >> > >> > > > > > >Hello Ilya, >>> > >> > >> > > > > > > >>> > >> > >> > > > > > >I do not see any issues with the mentioned test. I >>> see >>> > the >>> > >> > >> > following >>> > >> > >> > > > > > output >>> > >> > >> > > > > > >in the logs: >>> > >> > >> > > > > > > >>> > >> > >> > > > > > >[21:41:44] : [Step 4/5] [2019-03-22 >>> 21:41:44,970][INFO >>> > >> > >> > ][main][root] >>> > >> > >> > > > >>> >>> > >> > >> > > > > > >Stopping test: >>> > >> > >> > > > > > >>> > >> > >> > > > > > >>> > >> > >> > > > > >>> > >> > >> > > > >>> > >> > >> > > >>> > >> > >> > >>> > >> > >> >>> > >> > >>> > >> >>> > >>> >TcpDiscoveryCoordinatorFailureTest#testCoordinatorFailedNoAddFinishedM= essageStartOneNode >>> > >> > >> > > > > > >in 37768 ms <<< >>> > >> > >> > > > > > >[21:41:44] : [Step 4/5] [2019-03-22 >>> 21:41:44,971][INFO >>> > >> > >> > ][main][root] >>> > >> > >> > > > >>> >>> > >> > >> > > > > > >Stopping test class: >>> TcpDiscoveryCoordinatorFailureTest >>> > >> <<< >>> > >> > >> > > > > > >[21:41:44] : [Step 4/5] [2019-03-22 >>> 21:41:44,971][INFO >>> > >> > >> > ][main][root] >>> > >> > >> > > > >>> >>> > >> > >> > > > > > >Starting test class: IgniteClientConnectTest <<< >>> > >> > >> > > > > > > >>> > >> > >> > > > > > >The issue with Windows may be long connection >>> timeouts, >>> > in >>> > >> > this >>> > >> > >> > case >>> > >> > >> > > > we >>> > >> > >> > > > > > >should either split the suite into multiple ones o= r >>> > >> decrease >>> > >> > >> the >>> > >> > >> > SPI >>> > >> > >> > > > > > >timeouts. >>> > >> > >> > > > > > > >>> > >> > >> > > > > > >=D0=BF=D0=BD, 25 =D0=BC=D0=B0=D1=80. 2019 =D0=B3. = =D0=B2 11:24, Ilya Kasnacheev < >>> > >> > >> > > > > ilya.kasnacheev@gmail.com >>> > >> > >> > > > > > >: >>> > >> > >> > > > > > > >>> > >> > >> > > > > > >> Hello! >>> > >> > >> > > > > > >> >>> > >> > >> > > > > > >> It seems that I can no longer test this case, on >>> > >> account of >>> > >> > >> > > > > > >> >>> > >> > >> > > > > > >> >>> > >> > >> > > > > > >>> > >> > >> > > > > >>> > >> > >> > > > >>> > >> > >> > > >>> > >> > >> > >>> > >> > >> >>> > >> > >>> > >> >>> > >>> TcpDiscoveryCoordinatorFailureTest#testClusterFailedNewCoordinatorIniti= alized >>> > >> > >> > > > > > >> hanging every time under Java 11 on Windows. >>> > >> > >> > > > > > >> >>> > >> > >> > > > > > >> Alexey, Ivan, can you please take a look? >>> > >> > >> > > > > > >> >>> > >> > >> > > > > > >> >>> > >> > >> > > > > > >> >>> > >> > >> > > > > > >>> > >> > >> > > > > >>> > >> > >> > > > >>> > >> > >> > > >>> > >> > >> > >>> > >> > >> >>> > >> > >>> > >> >>> > >>> https://ci.ignite.apache.org/viewType.html?buildTypeId=3DIgniteTests24J= ava8_SpiWindows&tab=3DbuildTypeStatusDiv&branch_IgniteTests24Java8=3D__all_= branches__ >>> > >> > >> > > > > > >> >>> > >> > >> > > > > > >> Regards, >>> > >> > >> > > > > > >> >>> > >> > >> > > > > > >> -- >>> > >> > >> > > > > > >> Ilya Kasnacheev >>> > >> > >> > > > > > >> >>> > >> > >> > > > > > >> >>> > >> > >> > > > > > >> =D0=BF=D1=82, 22 =D0=BC=D0=B0=D1=80. 2019 =D0=B3= . =D0=B2 16:59, Ilya Kasnacheev < >>> > >> > >> > > > > > ilya.kasnacheev@gmail.com >: >>> > >> > >> > > > > > >> >>> > >> > >> > > > > > >> > Hello! >>> > >> > >> > > > > > >> > >>> > >> > >> > > > > > >> > Basically there is a test that explicitly >>> highlights >>> > >> this >>> > >> > >> > > problem, >>> > >> > >> > > > > > that >>> > >> > >> > > > > > >> is >>> > >> > >> > > > > > >> > running SSL tests on Windows + Java 11. They >>> will >>> > >> hang on >>> > >> > >> > Master >>> > >> > >> > > > but >>> > >> > >> > > > > > >> pass >>> > >> > >> > > > > > >> > with this patch. >>> > >> > >> > > > > > >> > >>> > >> > >> > > > > > >> > I have started that on TC, results will >>> probably be >>> > >> > >> available >>> > >> > >> > > > later >>> > >> > >> > > > > > >> today: >>> > >> > >> > > > > > >> > >>> > >> > >> > > > > > >> > >>> > >> > >> > > > > > >> >>> > >> > >> > > > > > >>> > >> > >> > > > > >>> > >> > >> > > > >>> > >> > >> > > >>> > >> > >> > >>> > >> > >> >>> > >> > >>> > >> >>> > >>> https://ci.ignite.apache.org/viewType.html?buildTypeId=3DIgniteTests24J= ava8_SpiWindows&tab=3DbuildTypeStatusDiv&branch_IgniteTests24Java8=3D__all_= branches__ >>> > >> > >> > > > > > >> > (mind the Java version). >>> > >> > >> > > > > > >> > >>> > >> > >> > > > > > >> > Regards, >>> > >> > >> > > > > > >> > -- >>> > >> > >> > > > > > >> > Ilya Kasnacheev >>> > >> > >> > > > > > >> > >>> > >> > >> > > > > > >> > >>> > >> > >> > > > > > >> > =D0=BF=D1=82, 22 =D0=BC=D0=B0=D1=80. 2019 =D0= =B3. =D0=B2 14:13, Maxim Muzafarov < >>> > >> > >> > > maxmuzaf@gmail.com >>> > >> > >> > > > > >: >>> > >> > >> > > > > > >> > >>> > >> > >> > > > > > >> >> Dmitry, Ilya, >>> > >> > >> > > > > > >> >> >>> > >> > >> > > > > > >> >> Yes, I've looked through those changes [1] as >>> they >>> > >> can >>> > >> > >> affect >>> > >> > >> > > my >>> > >> > >> > > > > > local >>> > >> > >> > > > > > >> >> PR. Basically, changes look good to me. >>> > >> > >> > > > > > >> >> >>> > >> > >> > > > > > >> >> I'm not an expert with CommunicationSpi >>> component, >>> > so >>> > >> > can >>> > >> > >> > miss >>> > >> > >> > > > some >>> > >> > >> > > > > > >> >> details and I haven't tested these changes >>> under >>> > Java >>> > >> > 11. >>> > >> > >> One >>> > >> > >> > > > more >>> > >> > >> > > > > > >> >> thing I'd like to say, I would add additional >>> tests >>> > >> to >>> > >> > PR >>> > >> > >> > that >>> > >> > >> > > > will >>> > >> > >> > > > > > >> >> explicitly highlight the problem being solved= . >>> > >> > >> > > > > > >> >> >>> > >> > >> > > > > > >> >> >>> > >> > >> > > > > > >> >> [1] >>> > >> https://issues.apache.org/jira/browse/IGNITE-11299 >>> > >> > >> > > > > > >> >> >>> > >> > >> > > > > > >> >> On Thu, 21 Mar 2019 at 22:57, Dmitriy Pavlov = < >>> > >> > >> > > > dpavlov@apache.org >>> > >> > >> > > > > > >>> > >> > >> > > > > > >> wrote: >>> > >> > >> > > > > > >> >> > >>> > >> > >> > > > > > >> >> > Hi Igniters, >>> > >> > >> > > > > > >> >> > >>> > >> > >> > > > > > >> >> > fix >>> > >> > https://issues.apache.org/jira/browse/IGNITE-11299 >>> > >> > >> > > Avoid >>> > >> > >> > > > > busy >>> > >> > >> > > > > > >> wait >>> > >> > >> > > > > > >> >> on >>> > >> > >> > > > > > >> >> > processWrite during SSL handshake. >>> > >> > >> > > > > > >> >> > seems to be blocker cause it is related to >>> Java >>> > 11 >>> > >> > >> > > > > > >> >> > >>> > >> > >> > > > > > >> >> > I see Maxim M left some comments. Ilya K., >>> Maxim >>> > >> > M.were >>> > >> > >> > these >>> > >> > >> > > > > > >> comments >>> > >> > >> > > > > > >> >> > addressed? >>> > >> > >> > > > > > >> >> > >>> > >> > >> > > > > > >> >> > The ticket is in Patch Available. Reviewer >>> > needed. >>> > >> > >> Changes >>> > >> > >> > > > > located >>> > >> > >> > > > > > >> in >>> > >> > >> > > > > > >> >> > GridNioServer. >>> > >> > >> > > > > > >> >> > >>> > >> > >> > > > > > >> >> > Sincerely, >>> > >> > >> > > > > > >> >> > Dmitriy Pavlov >>> > >> > >> > > > > > >> >> > >>> > >> > >> > > > > > >> >> > P.S. a quite obvious ticket came to sope, a= s >>> > well: >>> > >> > >> > > > > > >> >> > >>> > >> https://issues.apache.org/jira/browse/IGNITE-11600 >>> > >> > >> > > > > > >> >> > >>> > >> > >> > > > > > >> >> > >>> > >> > >> > > > > > >> >> > =D1=87=D1=82, 21 =D0=BC=D0=B0=D1=80. 2019 = =D0=B3. =D0=B2 16:55, Petr Ivanov < >>> > >> > >> > > mr.weider@gmail.com >>> > >> > >> > > > > >: >>> > >> > >> > > > > > >> >> > >>> > >> > >> > > > > > >> >> > > Huge +1 >>> > >> > >> > > > > > >> >> > > >>> > >> > >> > > > > > >> >> > > Will try to add new JDK in nearest time t= o >>> our >>> > >> > >> Teamcity. >>> > >> > >> > > > > > >> >> > > >>> > >> > >> > > > > > >> >> > > >>> > >> > >> > > > > > >> >> > > > On 21 Mar 2019, at 16:27, Dmitriy Pavlo= v >>> < >>> > >> > >> > > > > dpavlov@apache.org >>> > >> > >> > > > > > > >>> > >> > >> > > > > > >> >> wrote: >>> > >> > >> > > > > > >> >> > > > >>> > >> > >> > > > > > >> >> > > > Hi Igniters, >>> > >> > >> > > > > > >> >> > > > >>> > >> > >> > > > > > >> >> > > > Meanwhile, Java 12 GA is available. I >>> suggest >>> > >> at >>> > >> > >> least >>> > >> > >> > > test >>> > >> > >> > > > > our >>> > >> > >> > > > > > >> new >>> > >> > >> > > > > > >> >> tests >>> > >> > >> > > > > > >> >> > > > scripts with a couple of Java builds. >>> WDYT? >>> > >> > >> > > > > > >> >> > > > >>> > >> > >> > > > > > >> >> > > > Sincerely, >>> > >> > >> > > > > > >> >> > > > Dmitriy Pavlov >>> > >> > >> > > > > > >> >> > > > >>> > >> > >> > > > > > >> >> > > > =D1=81=D1=80, 20 =D0=BC=D0=B0=D1=80. 20= 19 =D0=B3. =D0=B2 19:21, Dmitriy >>> Pavlov >>> > >> > >> > > > > > >> < dpavlov@apache.org >: >>> > >> > >> > > > > > >> >> > > > >>> > >> > >> > > > > > >> >> > > >> Hi Ignite Developers, >>> > >> > >> > > > > > >> >> > > >> >>> > >> > >> > > > > > >> >> > > >> In a separate discussion, I've shared = a >>> log >>> > >> with >>> > >> > >> all >>> > >> > >> > > > > commits. >>> > >> > >> > > > > > >> >> > > >> >>> > >> > >> > > > > > >> >> > > >> As far as I can see, nobody removed >>> commits >>> > >> from >>> > >> > >> this >>> > >> > >> > > > sheet, >>> > >> > >> > > > > > so >>> > >> > >> > > > > > >> the >>> > >> > >> > > > > > >> >> > > scope >>> > >> > >> > > > > > >> >> > > >> of release will be discussed in anothe= r >>> way: >>> > >> only >>> > >> > >> > > > explicitly >>> > >> > >> > > > > > >> >> declared >>> > >> > >> > > > > > >> >> > > >> commits will be cherry-picked. >>> > >> > >> > > > > > >> >> > > >> >>> > >> > >> > > > > > >> >> > > >> Sincerely, >>> > >> > >> > > > > > >> >> > > >> Dmitriy Pavlov >>> > >> > >> > > > > > >> >> > > >> >>> > >> > >> > > > > > >> >> > > >>> > >> > >> > > > > > >> >> > > >>> > >> > >> > > > > > >> >> >>> > >> > >> > > > > > >> > >>> > >> > >> > > > > > >>> > >> > >> > > > > > >>> > >> > >> > > > > > -- >>> > >> > >> > > > > > Zhenya Stanilovsky >>> > >> > >> > > > > > >>> > >> > >> > > > >>> > >> > >> > > >>> > >> > >> > >>> > >> > >> >>> > >> > > >>> > >> > >>> > >> >>> > > >>> > >>> >> --00000000000042a26a0586937510--