From dev-return-30442-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Sat Jan 27 01:32:18 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 2485D180657 for ; Sat, 27 Jan 2018 01:32:18 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 14875160C50; Sat, 27 Jan 2018 00:32:18 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 368AF160C2E for ; Sat, 27 Jan 2018 01:32:17 +0100 (CET) Received: (qmail 80543 invoked by uid 500); 27 Jan 2018 00:32:16 -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 80532 invoked by uid 99); 27 Jan 2018 00:32:16 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 27 Jan 2018 00:32:16 +0000 Received: from [192.168.75.177] (c-67-160-238-197.hsd1.ca.comcast.net [67.160.238.197]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 5E86E1A0195 for ; Sat, 27 Jan 2018 00:32:14 +0000 (UTC) From: Denis Magda Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: Apache Ignite 2.4 release Date: Fri, 26 Jan 2018 16:32:04 -0800 References: <005304E0-5D2A-4BE2-BB0B-BBBB627E7730@apache.org> To: dev@ignite.apache.org In-Reply-To: Message-Id: <234065A7-F935-4AAA-977E-20C2D410BCC3@apache.org> X-Mailer: Apple Mail (2.3445.5.20) Hi Vyacheslav, According to the previous review notes the impact of the changes might = be significant, thus, I would recommend us to move the changes to the = next release. BTW, don=E2=80=99t hesitate to ping reviewers more frequently if there = is a pending/abandon review. We are all the people who are tend to = forget or miss notifications ;) > On Jan 26, 2018, at 2:04 AM, Vyacheslav Daradur = wrote: >=20 > Hi, Vladimir, it's good news. I'm looking forward to new Ignite = release! >=20 > Could you please share a release schedule for 'varint' optimizations? >=20 > The task [1] is waiting for review for 5 months. >=20 > [1] https://issues.apache.org/jira/browse/IGNITE-5097 >=20 >=20 > On Fri, Jan 26, 2018 at 12:51 PM, Vladimir Ozerov = wrote: >> Hi Igniters, >>=20 >> As far as I can see all required tasks and fixes were merged. I = propose to >> take several days of silence to test what we've done and start vote = at the >> beginning of the next week. >>=20 >> Makes sense? >>=20 >> On Mon, Jan 22, 2018 at 8:39 PM, Denis Magda = wrote: >>=20 >>> Ok, let=E2=80=99s target Wednesday as a code freeze date. >>>=20 >>> Community members who are involved in 2.4 release please merge you = fixes >>> and optimizations by that time. >>>=20 >>> =E2=80=94 >>> Denis >>>=20 >>>> On Jan 22, 2018, at 8:24 AM, Anton Vinogradov = wrote: >>>>=20 >>>> Issues >>>> https://issues.apache.org/jira/browse/IGNITE-6711 >>>> https://issues.apache.org/jira/browse/IGNITE-6902 >>>>=20 >>>> are in master and ignite-2.4 >>>>=20 >>>> On Mon, Jan 22, 2018 at 6:43 PM, Denis Magda = wrote: >>>>=20 >>>>> Igniters, >>>>>=20 >>>>> What=E2=80=99s left and what prevents us from passing 2.4 through = the QA phase? >>>>>=20 >>>>> Petr, Anton, Vladimir, Alex G., others please chime in. >>>>>=20 >>>>> =E2=80=94 >>>>> Denis >>>>>=20 >>>>>> On Jan 17, 2018, at 7:05 PM, Dmitriy Setrakyan = >>>>> wrote: >>>>>>=20 >>>>>> Great news, indeed! Looking forward to 2.4 release. >>>>>>=20 >>>>>> On Wed, Jan 17, 2018 at 2:55 AM, Vladimir Ozerov = >>>=20 >>>>>> wrote: >>>>>>=20 >>>>>>> Igniters, >>>>>>>=20 >>>>>>> Great news - two very important tickets - baseline topology and = Java 8 >>>>>>> support - were merged to master. At this point it makes sense to >>> create >>>>> a >>>>>>> branch to stabilize the release and finalize outstanding = tickets. I >>>>> created >>>>>>> the branch *ignite-2.4*. Please follow the rules below when = merging >>> new >>>>>>> commits to master: >>>>>>> 1) If ticket is targeted for 2.4 release, please merge to = master, then >>>>>>> cherry-pick to ignite-2.4 >>>>>>> 2) Otherwise just merge to master. >>>>>>>=20 >>>>>>> Vladimir. >>>>>>>=20 >>>>>>> On Tue, Jan 16, 2018 at 12:32 PM, Anton Vinogradov < >>>>>>> avinogradov@gridgain.com >>>>>>>> wrote: >>>>>>>=20 >>>>>>>> Denis, >>>>>>>>=20 >>>>>>>> I'll review https://issues.apache.org/jira/browse/IGNITE-6902 >>>>>>>>=20 >>>>>>>> On Fri, Jan 12, 2018 at 11:45 PM, Denis Magda = >>>>> wrote: >>>>>>>>=20 >>>>>>>>> Here is the page create before: >>>>>>>>> https://cwiki.apache.org/confluence/display/IGNITE/ >>> Apache+Ignite+2.4 >>>>> < >>>>>>>>> https://cwiki.apache.org/confluence/display/IGNITE/ >>> Apache+Ignite+2.4> >>>>>>>>>=20 >>>>>>>>> This is good news. It will be perfect if we also release as = many >>>>>>>> "required >>>>>>>>> tickets" as we can: >>>>>>>>> https://cwiki.apache.org/confluence/display/IGNITE/ >>> Apache+Ignite+2.4 >>>>> < >>>>>>>>> https://cwiki.apache.org/confluence/display/IGNITE/ >>> Apache+Ignite+2.4> >>>>>>>>>=20 >>>>>>>>> My favorite is memory metrics in bytes: = https://issues.apache.org/ >>>>>>>>> jira/browse/IGNITE-6902 >>>>>>> jira/browse/IGNITE-6902 >>>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> The discussion lists are flooded with the demands for this = essential >>>>>>>>> capability. Who is going to review it? >>>>>>>>>=20 >>>>>>>>> - >>>>>>>>> Denis >>>>>>>>>=20 >>>>>>>>>> On Jan 12, 2018, at 11:22 AM, Dmitriy Setrakyan < >>>>>>> dsetrakyan@apache.org >>>>>>>>>=20 >>>>>>>>> wrote: >>>>>>>>>>=20 >>>>>>>>>> +1 >>>>>>>>>>=20 >>>>>>>>>> Do we have a list of features for 2.4 documented anywhere? >>>>>>>>>>=20 >>>>>>>>>> D. >>>>>>>>>>=20 >>>>>>>>>> On Fri, Jan 12, 2018 at 7:43 AM, Pavel Tupitsyn < >>>>>>> ptupitsyn@apache.org> >>>>>>>>>> wrote: >>>>>>>>>>=20 >>>>>>>>>>> +1 >>>>>>>>>>>=20 >>>>>>>>>>> But some stuff is not yet in master (like baseline = topology), so >>> it >>>>>>> is >>>>>>>>> too >>>>>>>>>>> soon to create a branch, I think. >>>>>>>>>>>=20 >>>>>>>>>>> Pavel >>>>>>>>>>>=20 >>>>>>>>>>> On Fri, Jan 12, 2018 at 5:31 PM, Vladimir Ozerov < >>>>>>>> vozerov@gridgain.com> >>>>>>>>>>> wrote: >>>>>>>>>>>=20 >>>>>>>>>>>> Igniters, >>>>>>>>>>>>=20 >>>>>>>>>>>> A number of major improvements have been made (or being = finalized >>>>>>> at >>>>>>>>> the >>>>>>>>>>>> moment) to Ignite since recent 2.3 release. This includes >>> baseline >>>>>>>>>>>> topology, new DDL commands, migration to Java 8 and Java 9 >>> support, >>>>>>>>>>>> critical performance improvements to WAL, etc.. >>>>>>>>>>>>=20 >>>>>>>>>>>> I think it makes sense to make a new release. What do you = think >>> if >>>>>>> we >>>>>>>>>>>> release AI 2.4 with all this great stuff by the end of Jan? >>>>>>>>>>>>=20 >>>>>>>>>>>> If there are no objections, I'll create a branch to start >>>>>>>> stabilization >>>>>>>>>>>> process. >>>>>>>>>>>>=20 >>>>>>>>>>>> Vladimir. >>>>>>>>>>>>=20 >>>>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>=20 >>>>>>>=20 >>>>>=20 >>>>>=20 >>>=20 >>>=20 >=20 >=20 >=20 > --=20 > Best Regards, Vyacheslav D.