From dev-return-60391-archive-asf-public=cust-asf.ponee.io@storm.apache.org Wed Aug 7 15:40:12 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 62F11180643 for ; Wed, 7 Aug 2019 17:40:12 +0200 (CEST) Received: (qmail 21667 invoked by uid 500); 7 Aug 2019 15:40:11 -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 21655 invoked by uid 99); 7 Aug 2019 15:40:11 -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; Wed, 07 Aug 2019 15:40:11 +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 7F7DEC1BB4 for ; Wed, 7 Aug 2019 15:40:10 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.801 X-Spam-Level: * X-Spam-Status: No, score=1.801 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, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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-ec2-va.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id hQWbRl0Y3fEh for ; Wed, 7 Aug 2019 15:40:06 +0000 (UTC) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=209.85.210.44; helo=mail-ot1-f44.google.com; envelope-from=generalbas.srd@gmail.com; receiver= Received: from mail-ot1-f44.google.com (mail-ot1-f44.google.com [209.85.210.44]) by mx1-ec2-va.apache.org (ASF Mail Server at mx1-ec2-va.apache.org) with ESMTPS id 25E71BC7AD for ; Wed, 7 Aug 2019 15:40:06 +0000 (UTC) Received: by mail-ot1-f44.google.com with SMTP id q20so105934328otl.0 for ; Wed, 07 Aug 2019 08:40:06 -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=Jj4KrMcc50jy6py3xnalLfzTcjfI9L1p6s+7EJVYDPI=; b=iHQClN2/WAfMF6LL7HqcRazVS4SYVezX1oB6uOzNfcvuoz26tD6eFwR5jzWPbiJoWt DD9fa3xPi4w55/bQEwdIs6DnaBEz6dLU9YlBZZ3WsiFLORyeQDBgG3ZJHR9lUOCT7p3B yRP3Spts4JyZntVghBvTcXQ4cbJP5BJEBQKgxeQc0vLXH2nJePjA/Q2bcGkmGY4Jr4Gk TtimA1xYP4t50B3veYd5B/FlFaFlrLKanLm3IwGHs5TDdqIVmwXja89iH0ekdgJCjayo eahuIOeAJyKV0P7O+KALO9pEO/GTEBgCBvL4A+OufsJArYgGLUIWFz+J3F8Nb4mXhVOX VjHA== 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=Jj4KrMcc50jy6py3xnalLfzTcjfI9L1p6s+7EJVYDPI=; b=jzq2WKsDmCHvvgSQtMCDF3+G/80JGTKlLz/70y7ZxPcZBTDDx9lZwQE1k3kLWHMb/p SOYuIuU0nzAmVmo3AiMtQN5bziHyUdMf4eqRUemnFxgjwt5/+Eil3s9PYJ1yVJt6+7of ssaRtbcyGTmJqDR0/8QKmiPFhBCrGgDJH3LhgnyDLdztEFe9XaFR6frKTXsmv8scb6xY Htyhfvde9bZcVP6ZM4ZNGQ4eNcsSTDqFKtf6FYJN+HE+tj/OETioHmzcqqnA3gHqW22G Qeyd+auP7FphsdTrgt8aQbnIwbAuOR4V7rlJvlEn8lflmr+20hnD5yyxtEXHsk502cTH uKWA== X-Gm-Message-State: APjAAAXXFKYruNApCukDkWqPLHdXaLu9ypw71uoFTEoSSZajXi0pWghE VjDzg1HLOTNptebRjpRt7+ASYLeK0vpG4pedOu8Xcwyn X-Google-Smtp-Source: APXvYqzsO89vhvZ+Jp8n3sD/tLFoGRfKbOEQ9KCceC+hDTkOSjPpZVXu1RMgS0DB2HPWtAv8Ij/KqB9PYNYRxA2p2UQ= X-Received: by 2002:a9d:4c8b:: with SMTP id m11mr8728556otf.293.1565192405322; Wed, 07 Aug 2019 08:40:05 -0700 (PDT) MIME-Version: 1.0 References: <7F45AEA5-83D6-4648-B24A-93CF133E95B1@gmail.com> <962D9490-F754-4C89-A655-24E77FC9193A@gmail.com> <9B2BFB67-6E55-440F-84BE-8F02ED6ECEF3@gmail.com> In-Reply-To: <9B2BFB67-6E55-440F-84BE-8F02ED6ECEF3@gmail.com> From: =?UTF-8?Q?Stig_Rohde_D=C3=B8ssing?= Date: Wed, 7 Aug 2019 17:39:54 +0200 Message-ID: Subject: Re: [DISCUSS] Next 2.x release To: dev@storm.apache.org Content-Type: multipart/alternative; boundary="000000000000530f0b058f88c1e0" --000000000000530f0b058f88c1e0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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. Den ons. 7. aug. 2019 kl. 15.05 skrev Ethan Li : > I got my pgp key signed by Bryan W. Call bcall@apache.org>> (Thanks to him). > > My pgp key: > http://pgp.surfnet.nl/pks/lookup?op=3Dvindex&fingerprint=3Don&search=3D0x= A4A672F11B5050C8 > < > http://pgp.surfnet.nl/pks/lookup?op=3Dvindex&fingerprint=3Don&search=3D0x= A4A672F11B5050C8 > > > > My understanding is that I am good to do release with this key now. > > > Here is a list of PRs that we might want to include in the new release: > > 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> > > > Please review if you get a chance. Thanks > > > Ethan > > > > > On Aug 1, 2019, at 4:19 AM, Stig Rohde D=C3=B8ssing > wrote: > > > > Thanks Ethan, yes 2.1.0 makes sense. > > > > Den man. 29. jul. 2019 kl. 23.43 skrev Ethan Li < > ethanopensource@gmail.com>: > > > >> It=E2=80=99s a good point. I will start a discussion thread for it. > >> > >> > >> For the new release, I went through the list: > >> > https://issues.apache.org/jira/issues/?jql=3Dproject%20%3D%20STORM%20AND%= 20fixVersion%20%3D%202.0.1 > >> < > >> > https://issues.apache.org/jira/issues/?jql=3Dproject%20=3D%20STORM%20AND%= 20fixVersion%20=3D%202.0.1 > >>> > >> > >> 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> > >> > >> So I think we should release 2.1.0 rather than 2.0.1. > >> > >> There are a few pull requests we may want to review before the next > >> release: > >> > >> 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> > >> > >> > >> Thanks > >> Ethan > >> > >> > >>> On Jul 29, 2019, at 10:11 AM, Hugo Louro wrote: > >>> > >>> +1 > >>> > >>> I think it would facilitate more frequent releases to summarize in a > page > >>> the testing that all contributors/committers do in anticipation of th= e > >>> release, plus any "new" testing that may become relevant for the newe= r > >>> 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. > >>> > >>> Thanks, > >>> Hugo > >>> > >>> On Mon, Jul 29, 2019 at 7:15 AM Ethan Li > >> wrote: > >>> > >>>> Thanks Stig. I will look into it. > >>>> > >>>>> On Jul 26, 2019, at 3:06 PM, Stig Rohde D=C3=B8ssing < > >> stigdoessing@gmail.com> > >>>> wrote: > >>>>> > >>>>> 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. > >>>>> > >>>>> Semver for binary compatibility would probably be a good rule of > thumb. > >>>>> > >>>>> Den fre. 26. jul. 2019 kl. 20.01 skrev Ethan Li < > >>>> ethanopensource@gmail.com>: > >>>>> > >>>>>> > >>>>>> Stig, > >>>>>> > >>>>>> Do you know what=E2=80=99s the versioning standard we have been fo= llowing > (to > >>>>>> determine a 2.0.1 release or 2.1.0 release) ? > >>>>>> > >>>>>> > >>>>>>> On Jul 26, 2019, at 12:26 PM, Stig Rohde D=C3=B8ssing < > >>>> stigdoessing@gmail.com> > >>>>>> wrote: > >>>>>>> > >>>>>>> Sounds great, thanks Ethan. > >>>>>>> > >>>>>>> Den fre. 26. jul. 2019 kl. 19.16 skrev Ethan Li < > >>>>>> ethanopensource@gmail.com>: > >>>>>>> > >>>>>>>> It=E2=80=99s good idea to do more frequent release. I can run th= e next > >>>> release. > >>>>>>>> > >>>>>>>> I will take a look at both PRs. Other than that, I think we shou= ld > >>>> also > >>>>>>>> get https://github.com/apache/storm/pull/3093 < > >>>>>>>> https://github.com/apache/storm/pull/3093> in the new release. > >>>>>>>> > >>>>>>>> > >>>>>>>>> On Jul 26, 2019, at 11:58 AM, Stig Rohde D=C3=B8ssing < > >>>>>> stigdoessing@gmail.com> > >>>>>>>> wrote: > >>>>>>>>> > >>>>>>>>> Hi, > >>>>>>>>> > >>>>>>>>> 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 user= s > to > >>>> get > >>>>>>>> to > >>>>>>>>> grips with (the fix list for 2.0.0 is enormous). > >>>>>>>>> > >>>>>>>>> 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 > >>>>>>>>> > >>>>>>>> > >>>>>> > >>>> > >> > https://issues.apache.org/jira/issues/?jql=3Dproject%20%3D%20STORM%20AND%= 20fixVersion%20%3D%202.0.1 > >>>>>>>>> . > >>>>>>>>> > >>>>>>>>> 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? > >>>>>>>>> > >>>>>>>>> It would be good to take a look at currently open PRs and decid= e > >>>> which > >>>>>> we > >>>>>>>>> feel need to get merged before the next release. > >>>>>>>>> > >>>>>>>>> I would like to see at least > >>>> https://github.com/apache/storm/pull/2990 > >>>>>>>>> merged > >>>>>>>>> > >>>>>>>>> https://github.com/apache/storm/pull/2878 seems like it's close > to > >>>> be > >>>>>>>>> mergeable too? > >>>>>>>> > >>>>>>>> > >>>>>> > >>>>>> > >>>> > >>>> > >> > >> > > --000000000000530f0b058f88c1e0--