From dev-return-34031-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Sat Apr 28 17:08:41 2018 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 [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id A2515180649 for ; Sat, 28 Apr 2018 17:08:40 +0200 (CEST) Received: (qmail 33725 invoked by uid 500); 28 Apr 2018 15:08:39 -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 33713 invoked by uid 99); 28 Apr 2018 15:08:38 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 28 Apr 2018 15:08:38 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 8B05AC0040 for ; Sat, 28 Apr 2018 15:08:38 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.898 X-Spam-Level: * X-Spam-Status: No, score=1.898 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id dchRKZ4pL4-p for ; Sat, 28 Apr 2018 15:08:34 +0000 (UTC) Received: from mail-io0-f181.google.com (mail-io0-f181.google.com [209.85.223.181]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 6D9175F3CE for ; Sat, 28 Apr 2018 15:08:34 +0000 (UTC) Received: by mail-io0-f181.google.com with SMTP id e78-v6so5770769iod.0 for ; Sat, 28 Apr 2018 08:08:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=RoPLT4bqwBR+apJ+EGoTvJYDmWapFajA5APIDlg963A=; b=U40AUFiGl8gwEU5R1SyOlrZCDxUOy0ze6dd9k31SYWtwOkZ9HFXz8xC7I4M1DOpvoc 5cN2NeYJH0xsyiOypasqZPRrV5mNYk1ci4t+lHqk4NPigq6Lfjb9EwUNVPWP1YAgEhrO ZLk7I1t7AIL6OA5FcVLZ2/37yWg4TDXl/VaDJEWY6XU5PGT/AmoVO48zEKZkBmch1bbb roS2HapBj7UWHvl0J3niEvYKN4Y+QES1vT0pWn75a6mCvclS0IRoITcWhW38Rgeyopo9 rstz/Fug62I2l0hQ519YXP8IIq9XAY3u93DcjJ41Ba8JQaHG9CDaL2KhOaltvyuoUNAD 3Stw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=RoPLT4bqwBR+apJ+EGoTvJYDmWapFajA5APIDlg963A=; b=PglDOpe0Ibbeyewc2RSkMdieHzrM4z5OttwUuJcML4j4TF/hM2kSMNlmUTdYhCV9z7 8wqXm9ueBlCC2GyOMplKRcvEIx5PyZK2RdA+W/W1RoSl8LZl+oT5k/nWGQegAvioigof bB4SWfIz89b8RxFgKNg9KnTNHXtlwTXZzh/jP8TjAOlDZeq6WPLN5qbXjE7fesJ/j+Vb 7h2gU2gGtSm9tms86GcFvUFalzI83xRD8/I5lEzenzFluCsfO3V11akQMtiI9zEHJEC4 ZxCRY+LRdK4NS7vwgJOOR0Br96wU47yCt82AXc+XNXUEyAZ4K5u06G6YE1tHJMPBc91H 7AFw== X-Gm-Message-State: ALQs6tDv3IrH1A9bTrIkYVh4dkEi85vyb6VygDx/Wh39tUZkCIPJyxxw afQt8T284GiZPEqOx4Zmaz3vYvka1QFr9JBjnAY= X-Google-Smtp-Source: AB8JxZpscOSAhttFEXEhjRDvQ+bmRdMDSyfJCCFtxltZJ94ckTm1JEc6bd8h59mMkcUQlt6mL9Jn4xuWxhHCsigbSQc= X-Received: by 2002:a6b:e80f:: with SMTP id f15-v6mr6402396ioh.146.1524928113746; Sat, 28 Apr 2018 08:08:33 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Dmitry Pavlov Date: Sat, 28 Apr 2018 15:08:23 +0000 Message-ID: Subject: Re: Postpone Apache Ignite 2.5 release to fix baseline topology To: dev@ignite.apache.org Content-Type: multipart/alternative; boundary="000000000000872a6b056ae9feee" --000000000000872a6b056ae9feee Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I like AI 2.5 now, but then release AI 2.6 with (BL)AT fix. Probably we will find some more changes to be delivered to users. =D1=81=D0=B1, 28 =D0=B0=D0=BF=D1=80. 2018 =D0=B3. =D0=B2 17:56, Vladimir Oz= erov : > Yakov, > > Messages would help users understand what is wrong earlier, but will not > protect them from additional maintenance which is required in AI 2.4 and = is > supposed to be removed in next AI releases. > Please note that in IEP-4 topic I proposed alternative solution - release > AI 2.5 now, but then release AI 2.6 as soon as BLT is fixed. I.e. it woul= d > be emergency release. > > Both approaches works for me, the main goal is to deliver original defaul= ts > ASAP. However, approach with a single release looks better to me because = it > will minimize number of migrations for users. > > Vladimir. > > > On Sat, Apr 28, 2018 at 5:47 PM, Yakov Zhdanov > wrote: > > > Guys, how about we release 2.5 in the nearest future after adding prope= r > > usability log messages that will explain user what to do and also outpu= t > > link to readme.io with the first BLT related message during node uptime= . > > This should not take much time and we can use the same messages when we > > have (BL)AT modes in 2.6. I think that adding messages makes sense and > > should be clear for users which is not the case for 2.4. > > > > --Yakov > > > --000000000000872a6b056ae9feee--