Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id E9332200BFB for ; Wed, 11 Jan 2017 11:25:10 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id E7E20160B4E; Wed, 11 Jan 2017 10:25:10 +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 384EA160B2E for ; Wed, 11 Jan 2017 11:25:10 +0100 (CET) Received: (qmail 69991 invoked by uid 500); 11 Jan 2017 10:25:04 -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 69979 invoked by uid 99); 11 Jan 2017 10:25:04 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Jan 2017 10:25:04 +0000 Received: from mail-yw0-f179.google.com (mail-yw0-f179.google.com [209.85.161.179]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id D21601A0595 for ; Wed, 11 Jan 2017 10:25:03 +0000 (UTC) Received: by mail-yw0-f179.google.com with SMTP id l19so21891540ywc.2 for ; Wed, 11 Jan 2017 02:25:03 -0800 (PST) X-Gm-Message-State: AIkVDXLvgsNFt6l9Numky+9ABdkoActiwPsBr2AzXvBNoS96/WNfsv29QX3ajwrHyC9RugW3b07FbUHeDlhVYQ== X-Received: by 10.129.182.78 with SMTP id h14mr7502604ywk.314.1484130303145; Wed, 11 Jan 2017 02:25:03 -0800 (PST) MIME-Version: 1.0 Received: by 10.37.230.215 with HTTP; Wed, 11 Jan 2017 02:25:02 -0800 (PST) In-Reply-To: <1058947889.2826021.1483996569911@mail.yahoo.com> References: <5D6A7AA1-3A55-4404-A7F6-2003FAAFEC39@apache.org> <0F30F88C-2B8F-4D8A-861A-EA506A34A443@apache.org> <1888387481.4288566.1482887303051@mail.yahoo.com> <74DED292-E636-4F8B-9329-DB0CED2E21E5@apache.org> <456694194.5028183.1482958619170@mail.yahoo.com> <14B3BFD1-E5C5-4943-96E3-C160A717B3A2@apache.org> <440344432.5025532.1482962439788@mail.yahoo.com> <31E190DF-17C9-42BD-AA2D-CBA9C2C81D38@apache.org> <1425405216.5148338.1482967541448@mail.yahoo.com> <7154C0ED-1FF2-414C-B0E8-EE477093553B@apache.org> <148686060.5919308.1483051111028@mail.yahoo.com> <3F61287C-81CE-433E-ACB6-E20335DD6216@apache.org> <1847251368.6001650.1483052881123@mail.yahoo.com> <443841484.3687741.1483099771708@mail.yahoo.com> <436304839.892267.1483954980904@mail.yahoo.com> <1058947889.2826021.1483996569911@mail.yahoo.com> From: Andrey Gura Date: Wed, 11 Jan 2017 13:25:02 +0300 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [ANNOUNCE] Apache Ignite 1.8.0 Released To: dev@ignite.apache.org, "sk@apache.org" Cc: Denis Magda , Roman Shtykh , Prachi Garg Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable archived-at: Wed, 11 Jan 2017 10:25:11 -0000 Hi all I have a comment about release notes. Transactions deadlock detection was implemented in Apache Ignite 1.7. But this implementation is limited by pessimistic transactions only and doesn't support transactions on near caches. In Apache Ignite 1.8 release implemented deadlock detection that supports optimistic transactions and transactions on near caches. It is useful feature and could be important for transactions users. On Tue, Jan 10, 2017 at 12:16 AM, Sally Khudairi wrote: > Thanks, Denis. I'm working on a draft and will send it over for review in= the next couple of days. > Kind regards,Sally > > > [From the mobile; please excuse top-posting, spelling/spacing errors, and= brevity] > > > > > On Mon, Jan 9, 2017 at 13:33, Denis Magda wrote: R= oman, perfect! Well done! > *Prachi*, please add Roman=E2=80=99s blog to Apache Ignite=E2=80=99s blog= s list:https://ignite.apache.org/blogs.html > *Sally*, considering that all the information is already at place is it a= good time to wrap it up in an Apache official announcement? > =E2=80=94Denis > > On Jan 9, 2017, at 1:43 AM, Roman Shtykh wrote: > Denis, I published a short article on https://dzone.com/articles/handling= -apache-ignite-cluster-data-via-redis-prot -Roman > > On Saturday, December 31, 2016 12:50 AM, Denis Magda wrote: > > > Roman, amazing thanks! > You can use any blogging engine you like. After the blog post is ready no= tify the community and Prachi will send your material to dzone.com and when= it=E2=80=99s accepted there we will public it on Ignite=E2=80=99s blogging= page (https://ignite.apache.org/blogs.html). > As for the format, I would suggest making a quick walk-through guidance i= ncluding code snippets and showing how to connect to the cluster from Pytho= n or Ruby (whatever you like most) and work with it. You can do something l= ike I did for PHPhttps://dzone.com/articles/apache-ignite-enables-full-fled= ged-sql-support-for > =E2=80=94Denis > > On Dec 30, 2016, at 4:09 AM, Roman Shtykh wro= te: > Sure, Denis, I can write about Redis protocol support. Can you please ins= truct me about the format and how/where to submit? > Roman > > > On Friday, December 30, 2016 8:11 AM, Sally Khudairi = wrote: > > > Boop! Sorry about that...indeed, I wrote Roman's name in my notes next t= o "1.8 release manager?" and clearly combined the two. > Apologies for alarming you. > But that is a good hint, Denis > Cheers,Sally > > > [From the mobile; please excuse top-posting, spelling/spacing errors, and= brevity] > > > > > On Thu, Dec 29, 2016 at 17:58, Denis Magda wrote: S= ally, looks like you got confused with this > > On Dec 29, 2016, at 2:38 PM, Sally Khudairi wrote: > And thanks in advance, Roman Shtykh, for acting as project spokesperson i= n your role as release manager. Participation from the community at-large i= s greatly appreciated! > > Roman have never been a release manager yet. However, this is just a matt= er of time and his interest/intention ;) > =E2=80=94Denis > > > > > > > >