From dev-return-60392-archive-asf-public=cust-asf.ponee.io@storm.apache.org Wed Aug 7 15:43:28 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 6D428180643 for ; Wed, 7 Aug 2019 17:43:28 +0200 (CEST) Received: (qmail 28721 invoked by uid 500); 7 Aug 2019 15:43:27 -0000 Mailing-List: contact dev-help@storm.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@storm.apache.org Delivered-To: mailing list dev@storm.apache.org Received: (qmail 28704 invoked by uid 99); 7 Aug 2019 15:43:27 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Aug 2019 15:43:27 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 87CDB180EC2 for ; Wed, 7 Aug 2019 15:43:26 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.234 X-Spam-Level: X-Spam-Status: No, score=0.234 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NO_RDNS_DOTCOM_HELO=0.433, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-he-de.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id QBK_T6KlGlzD for ; Wed, 7 Aug 2019 15:43:22 +0000 (UTC) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=2607:f8b0:4864:20::334; helo=mail-ot1-x334.google.com; envelope-from=ethanopensource@gmail.com; receiver= Received: from mail-ot1-x334.google.com (mail-ot1-x334.google.com [IPv6:2607:f8b0:4864:20::334]) by mx1-he-de.apache.org (ASF Mail Server at mx1-he-de.apache.org) with ESMTPS id 11B2C7D3FB for ; Wed, 7 Aug 2019 15:43:22 +0000 (UTC) Received: by mail-ot1-x334.google.com with SMTP id s20so40576869otp.4 for ; Wed, 07 Aug 2019 08:43:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:mime-version:subject:date:references :to:in-reply-to:message-id; bh=VklkWQi46HxV8b/zueZCppOHlvzU4hTTpTRGt4O/qK0=; b=U59hlsyq460g9ZePEdR9deabqMFWsCkTpA0/h9CGqruQX7c5630NmGXwo9mCTTLqgE tUtOuANMUqC51gbNvZwA3sLYKKAtyOIjn0C97l5K+fRQhm8CxTEh/vHZ6KPNui15V2Gr 7KtS0xGhSQlaIwGhqgOKT1QzR2mTAf2Z9FffNRPMHClMzbPfpWZZPAZblX7CYodBe4Pv uT9NZamsJe7udgHdZqlozPENOq3O2O+7RXswsCWM+62ci3ilnh+sBRxJJJkfoMJF4Y01 VzUtAdYiw8+aTQhhywkdV55R4HpuEXRBi2srxPY41LPSQle57G/kAGsXh7Bi67ev9g+t dqMw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:references:to:in-reply-to:message-id; bh=VklkWQi46HxV8b/zueZCppOHlvzU4hTTpTRGt4O/qK0=; b=hujyFvZOAKmpUYRUURcNBSw5M8fkRwaDWGmCuDUm+/80rj1+Qi9EeawfEEHtd15alV vtkT3e2uvWszvL4L9ob/PXop2awbmTvUb+h5IxRAaSJuhSwiAM0TyHNVggkM7/ZzVZq+ XwWMo2Nm4/8U3+d4VldGbl+C+EwLRJi13nN/pJjstjEbH/6u0bnTOvtc68Mt8heKiRWo 6TiyfFoxeqTHk7+etIoBsO9xgwm+peaCH4oYqeCxKMQjQ7L4k1Mo/W0jCnhliEA4hzlQ IcGIfglHuc6hOZq0W15gClMPW+qB37BKc1yG/aCq4fLH7pyaXv7CAzYqOHvSZw+UFjGt hnJA== X-Gm-Message-State: APjAAAUHdkVHtTZpI+jMBn/Bn+kRFDjha2S+tRI6D/Fl4mqrPQpa5UGU +mGoZw2qy38md0RGm/WhBiiH8o6BMco= X-Google-Smtp-Source: APXvYqwOny4enTtsi8rI5aVFCdKrQ2IF95EV8L/BwY1qJEGlhsEqdC7ZZnyuArhJJoGs/a2TgleJGg== X-Received: by 2002:a02:3b62:: with SMTP id i34mr10963412jaf.91.1565192595065; Wed, 07 Aug 2019 08:43:15 -0700 (PDT) Received: from minutehall-lm.y.corp.yahoo.com ([2001:4998:efeb:7805::100e]) by smtp.gmail.com with ESMTPSA id r5sm75986752iom.42.2019.08.07.08.43.14 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 07 Aug 2019 08:43:14 -0700 (PDT) From: Ethan Li Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: [DISCUSS] Next 2.x release Date: Wed, 7 Aug 2019 10:43:11 -0500 References: <7F45AEA5-83D6-4648-B24A-93CF133E95B1@gmail.com> <962D9490-F754-4C89-A655-24E77FC9193A@gmail.com> <9B2BFB67-6E55-440F-84BE-8F02ED6ECEF3@gmail.com> To: dev@storm.apache.org In-Reply-To: Message-Id: X-Mailer: Apple Mail (2.3445.104.11) Yes thanks.=20 > On Aug 7, 2019, at 10:39 AM, Stig Rohde D=C3=B8ssing = wrote: >=20 > Sounds great. Remember to add your key to > https://dist.apache.org/repos/dist/release/storm/KEYS, you should be = able > to update it with an SVN client. See also > https://www.apache.org/dev/openpgp.html#update. >=20 > Den ons. 7. aug. 2019 kl. 15.05 skrev Ethan Li = : >=20 >> I got my pgp key signed by Bryan W. Call > bcall@apache.org>> (Thanks to him). >>=20 >> My pgp key: >> = http://pgp.surfnet.nl/pks/lookup?op=3Dvindex&fingerprint=3Don&search=3D0xA= 4A672F11B5050C8 >> < >> = http://pgp.surfnet.nl/pks/lookup?op=3Dvindex&fingerprint=3Don&search=3D0xA= 4A672F11B5050C8 >>>=20 >>=20 >> My understanding is that I am good to do release with this key now. >>=20 >>=20 >> Here is a list of PRs that we might want to include in the new = release: >>=20 >> https://github.com/apache/storm/pull/3098 < >> https://github.com/apache/storm/pull/3098> >> https://github.com/apache/storm/pull/3096 < >> https://github.com/apache/storm/pull/3096> >> https://github.com/apache/storm/pull/2878 < >> https://github.com/apache/storm/pull/2878> >>=20 >>=20 >> Please review if you get a chance. Thanks >>=20 >>=20 >> Ethan >>=20 >>=20 >>=20 >>> On Aug 1, 2019, at 4:19 AM, Stig Rohde D=C3=B8ssing = >> wrote: >>>=20 >>> Thanks Ethan, yes 2.1.0 makes sense. >>>=20 >>> Den man. 29. jul. 2019 kl. 23.43 skrev Ethan Li < >> ethanopensource@gmail.com>: >>>=20 >>>> It=E2=80=99s a good point. I will start a discussion thread for it. >>>>=20 >>>>=20 >>>> For the new release, I went through the list: >>>>=20 >> = https://issues.apache.org/jira/issues/?jql=3Dproject%20%3D%20STORM%20AND%2= 0fixVersion%20%3D%202.0.1 >>>> < >>>>=20 >> = https://issues.apache.org/jira/issues/?jql=3Dproject%20=3D%20STORM%20AND%2= 0fixVersion%20=3D%202.0.1 >>>>>=20 >>>>=20 >>>> We introduced some new functionalities, including >>>> https://issues.apache.org/jira/browse/STORM-2720 < >>>> https://issues.apache.org/jira/browse/STORM-2720> >>>> https://issues.apache.org/jira/browse/STORM-3412 < >>>> https://issues.apache.org/jira/browse/STORM-3412> >>>> https://issues.apache.org/jira/browse/STORM-3411 < >>>> https://issues.apache.org/jira/browse/STORM-3411> >>>> https://issues.apache.org/jira/browse/STORM-3442 < >>>> https://issues.apache.org/jira/browse/STORM-3442> >>>> https://issues.apache.org/jira/browse/STORM-3396 < >>>> https://issues.apache.org/jira/browse/STORM-3396> >>>> https://issues.apache.org/jira/browse/STORM-3392 < >>>> https://issues.apache.org/jira/browse/STORM-3392> >>>> https://issues.apache.org/jira/browse/STORM-3395 < >>>> https://issues.apache.org/jira/browse/STORM-3395> >>>>=20 >>>> So I think we should release 2.1.0 rather than 2.0.1. >>>>=20 >>>> There are a few pull requests we may want to review before the next >>>> release: >>>>=20 >>>> https://github.com/apache/storm/pull/3094 < >>>> https://github.com/apache/storm/pull/3094> >>>> https://github.com/apache/storm/pull/2990 < >>>> https://github.com/apache/storm/pull/2990> >>>> https://github.com/apache/storm/pull/2878 < >>>> https://github.com/apache/storm/pull/2878> >>>>=20 >>>>=20 >>>> Thanks >>>> Ethan >>>>=20 >>>>=20 >>>>> On Jul 29, 2019, at 10:11 AM, Hugo Louro = wrote: >>>>>=20 >>>>> +1 >>>>>=20 >>>>> I think it would facilitate more frequent releases to summarize in = a >> page >>>>> the testing that all contributors/committers do in anticipation of = the >>>>> release, plus any "new" testing that may become relevant for the = newer >>>>> releases. Doing so would make it easy to create a check form or or >> email >>>>> template that what we feel should be done to guarantee a stable >> release. >>>>>=20 >>>>> Thanks, >>>>> Hugo >>>>>=20 >>>>> On Mon, Jul 29, 2019 at 7:15 AM Ethan Li = >>>> wrote: >>>>>=20 >>>>>> Thanks Stig. I will look into it. >>>>>>=20 >>>>>>> On Jul 26, 2019, at 3:06 PM, Stig Rohde D=C3=B8ssing < >>>> stigdoessing@gmail.com> >>>>>> wrote: >>>>>>>=20 >>>>>>> I think ideally we've been trying for semver, but it's been = pretty >>>> loose, >>>>>>> e.g. there were breaking changes in one of the 1.2.x releases = for >>>>>>> storm-kafka-client. I don't know what rules we've actually been >> using, >>>> if >>>>>>> any. >>>>>>>=20 >>>>>>> Semver for binary compatibility would probably be a good rule of >> thumb. >>>>>>>=20 >>>>>>> Den fre. 26. jul. 2019 kl. 20.01 skrev Ethan Li < >>>>>> ethanopensource@gmail.com>: >>>>>>>=20 >>>>>>>>=20 >>>>>>>> Stig, >>>>>>>>=20 >>>>>>>> Do you know what=E2=80=99s the versioning standard we have been = following >> (to >>>>>>>> determine a 2.0.1 release or 2.1.0 release) ? >>>>>>>>=20 >>>>>>>>=20 >>>>>>>>> On Jul 26, 2019, at 12:26 PM, Stig Rohde D=C3=B8ssing < >>>>>> stigdoessing@gmail.com> >>>>>>>> wrote: >>>>>>>>>=20 >>>>>>>>> Sounds great, thanks Ethan. >>>>>>>>>=20 >>>>>>>>> Den fre. 26. jul. 2019 kl. 19.16 skrev Ethan Li < >>>>>>>> ethanopensource@gmail.com>: >>>>>>>>>=20 >>>>>>>>>> It=E2=80=99s good idea to do more frequent release. I can run = the next >>>>>> release. >>>>>>>>>>=20 >>>>>>>>>> I will take a look at both PRs. Other than that, I think we = should >>>>>> also >>>>>>>>>> get https://github.com/apache/storm/pull/3093 < >>>>>>>>>> https://github.com/apache/storm/pull/3093> in the new = release. >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>>> On Jul 26, 2019, at 11:58 AM, Stig Rohde D=C3=B8ssing < >>>>>>>> stigdoessing@gmail.com> >>>>>>>>>> wrote: >>>>>>>>>>>=20 >>>>>>>>>>> Hi, >>>>>>>>>>>=20 >>>>>>>>>>> I think we've talked about more frequent releases before. >> Releasing >>>>>> new >>>>>>>>>>> versions every few months means people don't have to wait = long >> for >>>>>>>> fixes >>>>>>>>>> to >>>>>>>>>>> get out, and smaller releases are probably also easier for = users >> to >>>>>> get >>>>>>>>>> to >>>>>>>>>>> grips with (the fix list for 2.0.0 is enormous). >>>>>>>>>>>=20 >>>>>>>>>>> With that in mind, I think we should start looking at the = next >> 2.x >>>>>>>>>> release >>>>>>>>>>> (2.0.1 or 2.1.0?), since it's been a couple of months since = 2.0.0 >>>>>>>>>> released. >>>>>>>>>>> The fix list would be >>>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>=20 >>>>>>=20 >>>>=20 >> = https://issues.apache.org/jira/issues/?jql=3Dproject%20%3D%20STORM%20AND%2= 0fixVersion%20%3D%202.0.1 >>>>>>>>>>> . >>>>>>>>>>>=20 >>>>>>>>>>> Govind and Ethan have offered to run the next release, and = help >>>>>>>> validate >>>>>>>>>>> our release process guidelines. Would one of you have time = to >> work >>>>>> on a >>>>>>>>>>> release in the near future? >>>>>>>>>>>=20 >>>>>>>>>>> It would be good to take a look at currently open PRs and = decide >>>>>> which >>>>>>>> we >>>>>>>>>>> feel need to get merged before the next release. >>>>>>>>>>>=20 >>>>>>>>>>> I would like to see at least >>>>>> https://github.com/apache/storm/pull/2990 >>>>>>>>>>> merged >>>>>>>>>>>=20 >>>>>>>>>>> https://github.com/apache/storm/pull/2878 seems like it's = close >> to >>>>>> be >>>>>>>>>>> mergeable too? >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>=20 >>>>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>=20 >>>>=20 >>=20 >>=20