From dev-return-48923-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Fri Dec 27 20:59:38 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 EA748180658 for ; Fri, 27 Dec 2019 21:59:37 +0100 (CET) Received: (qmail 73612 invoked by uid 500); 27 Dec 2019 20:59:37 -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 73600 invoked by uid 99); 27 Dec 2019 20:59:37 -0000 Received: from Unknown (HELO mailrelay1-lw-us.apache.org) (10.10.3.159) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Dec 2019 20:59:37 +0000 Received: from mail-il1-f180.google.com (mail-il1-f180.google.com [209.85.166.180]) by mailrelay1-lw-us.apache.org (ASF Mail Server at mailrelay1-lw-us.apache.org) with ESMTPSA id D7EDA4FB3 for ; Fri, 27 Dec 2019 20:59:36 +0000 (UTC) Received: by mail-il1-f180.google.com with SMTP id v15so23299384iln.0 for ; Fri, 27 Dec 2019 12:59:36 -0800 (PST) X-Gm-Message-State: APjAAAX4gOZGKSWgBPummowYBXVLvq3aLBON86ykGp7qi+s2BVUYJQVL R7DFAHxpUS3LW9mWtOcBwRBBLcgY4IbHVf0rfoFMYg== X-Google-Smtp-Source: APXvYqyahr8ioMcIxcGUb17IWVZvUEXp7YGtRiqQIliAH545VTWmlK5MsIAVq0fqC3ACBrS5tPgGt/1+ufVnuPhdTfA= X-Received: by 2002:a92:da41:: with SMTP id p1mr43156792ilq.65.1577480376573; Fri, 27 Dec 2019 12:59:36 -0800 (PST) MIME-Version: 1.0 References: <1577182948.967805691@f380.i.mail.ru> In-Reply-To: From: Denis Magda Date: Fri, 27 Dec 2019 12:59:09 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Apache Ignite 2.8 RELEASE [Time, Scope, Manager] To: dev Content-Type: multipart/alternative; boundary="0000000000007c76a6059ab5c5cb" --0000000000007c76a6059ab5c5cb Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Ilya, no I see, thanks for the explanation. Agree with you, let's update the versions of the dependencies to the latest. - Denis On Thu, Dec 26, 2019 at 10:50 PM Ilya Kasnacheev wrote: > Hello! > > I have committed ignite-spring-data_2.2 to ignite-2.8. > > By bumping versisons I mean the following: > 1.7.*7* > 1.6.*4* > 1.1.7.*2* > 2.6.*5* > 2.3.*0* > 1.13.*14*.RELEASE > 4.3.*18*.RELEASE > 2.0.*9*.RELEASE > > 5.0.*8*.RELEASE > > All these libraries have maintenance release (such as our 2.7.*6*) and I > think it would be beneficial to upgrade these dependencies to the latest > maintenance version found in Maven Central. > For example, there is spring.data-2.0 2.0.*14*.RELEASE. > > Regards, > -- > Ilya Kasnacheev > > > =D1=87=D1=82, 26 =D0=B4=D0=B5=D0=BA. 2019 =D0=B3. =D0=B2 19:32, Denis Mag= da : > > > A huge +1 for adding Spring Data related fixes/improvements. Ilya is > right > > that Spring Data related questions sparked last time due to missing > support > > of 2.2 version. > > > > Ilya, could you elaborate on what you mean under "bumping the versions"= ? > Do > > you suggest performing a straightforward upgrade of "ignite-spring-data= " > to > > version 2.2 and introducing "ignite-spring-data-{old-version"} for the > > previous versions? If it's so, I fully agree with the proposal. > > > > - > > Denis > > > > > > On Thu, Dec 26, 2019 at 4:52 AM Ilya Kasnacheev < > ilya.kasnacheev@gmail.com > > > > > wrote: > > > > > Hello! > > > > > > I propose to add the following ticket to the scope: > > > https://issues.apache.org/jira/browse/IGNITE-12259 (3 commits, be > > careful > > > with release version) > > > > > > Adding tickets to scope surely seems crazy now, but I will provide th= e > > > following considerations: > > > * This is Spring Data 2.2 integration, which we currently do not have= , > > > leading to lots of confused questions on stack overflow and mailing > list. > > > Spring Data is important to our public image since many people may > learn > > > about out project by starting with Spring Data. > > > > > > * It has zero code impact outside of its own module (just 2 POM file > > > touched and that's all). > > > > > > * The core was ready since early November but, due to gmail quirk, we > did > > > not react to it in time. > > > > > > WDYT? > > > > > > Another semi-related question. *Should we bump our dependencies' > versions > > > before releasing 2.8?* I talk mainly about spring and hibernate > > > dependencies. We could switch them to their latest maintenance versio= ns > > to > > > avoid shipping default links to outdated packages. > > > > > > I think this is one of things that are very hard to do between > releases, > > so > > > I think this dependencies bumping should be a part of a formal > > > release/testing cycle, and then be backported to master. > > > > > > I could volunteer to do that myself, if we agree to merge these versi= on > > > upgrades to ignite-2.8 and then re-test. > > > > > > Regards, > > > -- > > > Ilya Kasnacheev > > > > > > > > > =D0=B2=D1=82, 24 =D0=B4=D0=B5=D0=BA. 2019 =D0=B3. =D0=B2 13:22, Zheny= a Stanilovsky > > > > >: > > > > > > > > > > > Igniters, i`l try to compare 2.8 release candidate vs 2.7.6, > > > > last sha 2.8 was build from : 9d114f3137f92aebc2562a > > > > i use yardstick benchmarks, 4 bare machine with: 2x Xeon X5570 96G= b > > > 512GB > > > > SSD 2048GB HDD 10GB/s > > > > 1 for client (driver) and 3 for servers. > > > > this mappings for graphs and real yardstick tests: > > > > > > > > atomic-put: IgnitePutBenchmark > > > > sql-merge-query: IgniteSqlMergeQueryBenchmark > > > > atomic-get: IgniteGetBenchmark > > > > tx-get: IgniteGetTxBenchmark > > > > tx-put: IgnitePutTxBenchmark > > > > atomic-put-all-bs-10: IgnitePutAllBenchmark > > > > tx-put-all-bs-10: IgnitePutAllTxBenchmark > > > > > > > > cacheMode =E2=80=94 partitioned > > > > CacheWriteSynchronizationMode.FULL_SYNC > > > > 1 backup > > > > > > > > 1. wal =3D log_only 2. wal =3D none 3. persistence disabled. > > > > Thanks Maxim for wiki page [1] > > > > > > > > > > > > [1] > > > > > > > > > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#Apac= heIgnite2.8-Benchmarks > > > > > > > > do we need some bisect or other work here ? > > > > > > > > > > > > > > > > > > >------- Forwarded message ------- > > > > >From: "Maxim Muzafarov" < mmuzaf@apache.org > > > > > >To: dev@ignite.apache.org > > > > >Cc: > > > > >Subject: Apache Ignite 2.8 RELEASE [Time, Scope, Manager] > > > > >Date: Fri, 20 Sep 2019 14:44:31 +0300 > > > > > > > > > >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? > > > > > > > > > > > > > > > > > > > > > > --0000000000007c76a6059ab5c5cb--