From dev-return-60581-archive-asf-public=cust-asf.ponee.io@storm.apache.org Wed Aug 21 15:37:52 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 D31B5180607 for ; Wed, 21 Aug 2019 17:37:51 +0200 (CEST) Received: (qmail 30908 invoked by uid 500); 21 Aug 2019 15:37:51 -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 30896 invoked by uid 99); 21 Aug 2019 15:37:50 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Aug 2019 15:37:50 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 6E8B4C0874 for ; Wed, 21 Aug 2019 15:37:49 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.051 X-Spam-Level: ** X-Spam-Status: No, score=2.051 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, KAM_LOTSOFHASH=0.25, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd1-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 (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id iPMhOnCjSrEj for ; Wed, 21 Aug 2019 15:37:40 +0000 (UTC) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=2607:f8b0:4864:20::334; helo=mail-ot1-x334.google.com; envelope-from=generalbas.srd@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 597FE7DD51 for ; Wed, 21 Aug 2019 15:37:39 +0000 (UTC) Received: by mail-ot1-x334.google.com with SMTP id w4so2438886ote.11 for ; Wed, 21 Aug 2019 08:37:39 -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=LSD0lLPCX53Zm+YaCBgfTMBMdwGqnoBqVY7hdEWOoi4=; b=rY/b8oAr4CLqYvnocWlEUmXND+PawVGeMMjBIb2QF7PW8ukeB9j+rWRv/eh28GLgWS YF/ZRAGT6gTlUy4j6yOvX0t8YFv8Ozm/uyqE9MWG6PRPZmaL3mK3S8kEO6taJK4R+pz8 hMbrbAB0gTjkbvvQ9ToZ2WGYFRBFGbJffb+bTgEq3prMmow/+LyoNzr9six5UePwe/mZ dLTOopfSTywUCnI+lywOQZYiXk0FdFz25tzxYhpXOabGxMiD9PIvvVsxsaOaGnFNWPd6 mTcZzjdXP8eT2yxsLI9nlM+IT2atp7gyI1D3fFNpdyVnQzklXfnD0C5JbuVpB3idYdv0 f0Cg== 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=LSD0lLPCX53Zm+YaCBgfTMBMdwGqnoBqVY7hdEWOoi4=; b=pva43737BmZICsmN02SiqSvoPSmaMUdazV/mh5kKpg3o3bFHH9esW+im+vAdtNlL/G H4bd+Ba9i0JDJay1izctplilWT3E4e7HVGixNP49QDyF47nXrN2SBpImfAhDfEE3Vyx2 42uj5HEI+unu57nrYVrL+Wxk4yCFfEQuDCReS+Cm9T9vfAgTQy/t8Z5gMyOLssLOYcfO jd6JNhtzZkui/ON49ji9VUHj5JuqI3pmlj14sgGQac8KcVu3cI0PKDu6x2xMLSPyPlWu ShbxRLmXsUPbMrDiKgkJHdpXZZ4IG27dE2XmP5IMYrgaGdpY76o4D6T0ZCfSxLx5zUOu xLKA== X-Gm-Message-State: APjAAAUSWQQa9ECgYlz3VvAppepiRztinUihBkyxtNp7AwkeSTW8SYnZ rUphDw6wvj5Rt3/RoA61UpeuN8Ho4kNExhi8QPNRPQ== X-Google-Smtp-Source: APXvYqxmafhNWfEUByUalX+sbm310CknATzaDsogSeaKo/gS03M3FdTSSeBTy0C9ELnxWDtUdLrYn5KKHag8Qi50JoE= X-Received: by 2002:a9d:7c87:: with SMTP id q7mr27756778otn.241.1566401857328; Wed, 21 Aug 2019 08:37:37 -0700 (PDT) MIME-Version: 1.0 References: <2tzY1nYzSo3UgEI0_byRUZ42bpbNKRNYmFTWTvLbbM8mcIIjv1Wv4T4ZAS0acF0Isp6uUdXG19o9G1iMrez8BQ==@protonmail.internalid> <86643B96-B8B7-4354-98AD-AF0260C45A3F@gmail.com> <20190808221518.GC26391@dagit.name> <20190809135332.GA30551@dagit.name> <20190809195353.GA31067@dagit.name> <26C0598C-C737-4AC5-9194-0CE8F63B6126@gmail.com> <9C6A4375-BAF2-4801-93C1-49C80B6F6146@gmail.com> <95E0E4A1-BD29-433A-873D-EC44C237F1C7@gmail.com> <7249561A-F225-4C3E-A5CD-3F0F6D14F1F7@gmail.com> <69BB2732-D9C8-463F-9C35-7558D0F8CE8A@gmail.com> <4BA37104-3E51-4AE6-BD6C-B510988C689C@gmail.com> <12816261-1B8D-4196-9C3E-337ECFE6EB24@gmail.com> <2055B111-7BFF-47E8-A92E-F5C6781DDBB6@gmail.com> <1274C115-8A2B-40E3-8548-5944CA065D6F@gmail.com> <0C7C1ED5-0044-408B-945E-EDA9688242A8@gmail.com> <89FDD8CE-2211-4997-84D3-2D08992A11E9@gmail.com> <2E4F6278-9E4A-401F-BCB6-8774BD793B3F@gmail.com> <40571B6D-FD0E-479D-8B3D-62A46A9F12E1@gmail.com> In-Reply-To: <40571B6D-FD0E-479D-8B3D-62A46A9F12E1@gmail.com> From: =?UTF-8?Q?Stig_Rohde_D=C3=B8ssing?= Date: Wed, 21 Aug 2019 17:37:25 +0200 Message-ID: Subject: Re: [DISCUSS] Next 2.x release To: dev@storm.apache.org Content-Type: multipart/alternative; boundary="00000000000048187a0590a25ae0" --00000000000048187a0590a25ae0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sounds good Den ons. 21. aug. 2019 kl. 17.27 skrev Ethan Li = : > As we agreed to create a 2.1.x-branch and any later critical bug fixes fo= r > 2.1.x will go into that branch, I think there is not point for master > branch to freeze. > > There are many pull requests I=E2=80=99d like to merge and it potentially= blocks > some of our developments (for up to 20 days now). So I am proposing to fr= ee > master branch and start merging pull requests. And if it=E2=80=99s a crit= ical bug > fix, we should merge it to 2.1.x-branch too. > > > On Aug 19, 2019, at 3:01 PM, Ethan Li wrote= : > > > > Yes we can revert the two commits before merging in a new commit if we > decide to include this new commit to current version. > > > > > >> On Aug 19, 2019, at 2:57 PM, Stig Rohde D=C3=B8ssing > wrote: > >> > >>> Now if we need to merge something in (2.1.0 is not released yet), we > >> merge it to 2.1.x-branch. But the current pom version is > 2.1.1-SNAPSHOT, > >> which should really be 2.1.0-SNAPSHOT, because this commit goes into > 2.1.0 > >> version. To fix this, we need to revert last two commits before we > merge > >> the new commit. > >> > >> Sure, but if we're merging anything to 2.1.x-branch during the release > >> process, we're either expecting it to go in 2.1.1 so 2.1.1-SNAPSHOT is > the > >> right version, or we're cancelling the 2.1.0 vote in order to include > it, > >> and in that case we're reverting those two commits anyway, right? I > don't > >> think there's a problem with merging something in, and then reverting > the > >> version bump in a later commit? > >> > >> Den man. 19. aug. 2019 kl. 20.38 skrev Ethan Li < > ethanopensource@gmail.com >: > >> > >>> You are right. But I was talking about the pom version. > >>> > >>> So if we have 2.1.x-branch and the pom version is 2.1.0-SNAPSHOT. If = we > >>> start release process here, i.e. run =E2=80=9Cmvn release:prepare=E2= =80=9D, it will > create > >>> and push two commits automatically. > >>> > >>> First commit: change pom version to 2.1.0; and create a v2.1.0 git ta= g. > >>> Second commit: change pom version to 2.1.1-SNAPSHOT. > >>> > >>> So now in 2.1.x-branch, the pom version is 2.1.1-SNAPSHOT. > >>> > >>> Now if we need to merge something in (2.1.0 is not released yet), we > merge > >>> it to 2.1.x-branch. But the current pom version is 2.1.1-SNAPSHOT, > which > >>> should really be 2.1.0-SNAPSHOT, because this commit goes into 2.1.0 > >>> version. To fix this, we need to revert last two commits before we > merge > >>> the new commit. > >>> > >>> If we use 2.1-SNAPSHOT, we don=E2=80=99t need to revert. > >>> > >>> With that being said, I am fine with reverting if needed. It=E2=80= =99s > probably > >>> safe to not change the convention. > >>> > >>> > >>> > >>>> On Aug 19, 2019, at 1:24 PM, Stig Rohde D=C3=B8ssing < > stigdoessing@gmail.com > > >>> wrote: > >>>> > >>>> Ok, that makes sense. I still don't understand the need for > 2.1-SNAPSHOT? > >>>> > >>>> If we branch off 2.1.x-branch and then roll master to 2.2.0-SNAPSHOT > >>>> immediately, we can merge any commits into master and mark them in > Jira > >>>> with fix version 2.2.0. If we then get a bugfix that needs to go in > e.g. > >>>> 2.1.1, we can merge it to master and cherry pick the commit back to > >>>> 2.1.x-branch, and update the fix version to both 2.2.0 and 2.1.1. > This is > >>>> basically similar to how it worked for the 1.x-branch branches. > >>>> > >>>> Why do we need 2.1-SNAPSHOT? > >>>> > >>>> Den man. 19. aug. 2019 kl. 20.03 skrev Ethan Li < > >>> ethanopensource@gmail.com ethanopensource@gmail.com >>: > >>>> > >>>>> We don=E2=80=99t create 2.1.0 branch. > >>>>> > >>>>> I was thinking (and have been doing) about creating a 2.1.x-branch > >>> before > >>>>> doing any thing release related. Then we use 2.1.x-branch to relea= se > >>>>> 2.1.0, and 2.1.1, etc. > >>>>> > >>>>> When we create a 2.1.x-branch, we move master to 2.2.x-branch. It= =E2=80=99s > a > >>>>> little different than what we did in the past. But it makes more > sense > >>> as > >>>>> it follows semantic versioning more strictly. > >>>>> > >>>>> > >>>>> > >>>>>> On Aug 19, 2019, at 12:53 PM, Stig Rohde D=C3=B8ssing < > >>> stigdoessing@gmail.com > > >>>>> wrote: > >>>>>> > >>>>>> I would be fine with just freezing (non-critical) merges during th= e > >>>>>> release process. These mails are public, so it's easy for anyone t= o > see > >>>>>> whether a release is in progress. > >>>>>> > >>>>>> If we want to do merges while releases are going on, I think your > >>>>> proposal > >>>>>> of using a release branch is fine. I'm not sure I understand why w= e > >>> need > >>>>>> the 2.1-SNAPSHOT version though? > >>>>>> > >>>>>> Let's say we create release branch 2.1.0-branch from master. We ro= ll > >>> the > >>>>>> master version to 2.1.1-SNAPSHOT (for example) after the 2.1.0 > branch > >>> is > >>>>>> created. We then get a bug fix that should go in 2.1.0. In this > case we > >>>>>> should merge it to 2.1.0-branch, then merge 2.1.0-branch to master= . > In > >>>>> Jira > >>>>>> we mark it as going in 2.1.0. > >>>>>> > >>>>>> We then get a PR that shouldn't be included in 2.1.0. We just merg= e > it > >>> to > >>>>>> master, and mark it as 2.1.1 in Jira. > >>>>>> > >>>>>> Finally once 2.1.0 is released, we merge 2.1.0-branch into master > and > >>>>>> delete 2.1.0-branch. > >>>>>> > >>>>>> Why is there a need to 2.1-SNAPSHOT? > >>>>>> > >>>>>> Den man. 19. aug. 2019 kl. 18.15 skrev Ethan Li < > >>>>> ethanopensource@gmail.com > > > >>> ethanopensource@gmail.com ethanopensource@gmail.com >>>: > >>>>>> > >>>>>>> Many issues came up while I was preparing for 2.1.0 release. > Freezing > >>>>>>> merge until the release is done is not practical. So I am > proposing: > >>>>>>> > >>>>>>> 1. Once we decide to make a release, we create a new branch based > on > >>>>>>> master and start release process. > >>>>>>> 2. During the new process, master is still open for backwards > >>>>>>> compatibility commits, including new features, bu g fixes, etc. > >>>>>>> 3. Only bug fixes will be merged to the new branch and we need to > >>>>> restart > >>>>>>> the release process to include the bug fixes. > >>>>>>> 4. To avoid too much confusion on pom versions when we merge new > >>> commits > >>>>>>> during the release process, we should use less concrete version. > For > >>>>>>> example, in 2.1.x-branch, the pom version should be 2.1-SNAPSHOT, > >>>>> instead > >>>>>>> of 2.1.0-SNAPSHOT. > >>>>>>> > >>>>>>> For example, > >>>>>>> > >>>>>>> Let=E2=80=99s say we have a new branch 2.1.x-branch, the pom vers= ion is > >>>>>>> 2.1.0-SNAPSHOT. We start the release process and after running th= e > mvn > >>>>>>> release:prepare -Pxxx command, the pom version changes to > >>>>> 2.1.1-SNAPSHOT, > >>>>>>> and before that a git tag v2.1.0 is created. Now if there is a b= ug > >>> fix > >>>>> we > >>>>>>> have to merge in, so we merge in and it=E2=80=99s actually merged= in to > >>>>>>> 2.1.1-SNAPSHOT at this point if we don=E2=80=99t manually revert = the pom > >>>>> version, > >>>>>>> which can be confusing. We can avoid this problem by just using > >>>>>>> 2.1-SNAPSHOT as the pom version. So it doesn=E2=80=99t have to ch= ange. > >>>>>>> > >>>>>>> Please let me know if there is any potential risk for doing this. > >>>>>>> > >>>>>>> Thanks > >>>>>>> Ethan > >>>>>>> > >>>>>>>> On Aug 19, 2019, at 10:25 AM, Ethan Li > >>> >= > > >>>>>>> wrote: > >>>>>>>> > >>>>>>>> The pull request for the fix is > >>>>>>> https://github.com/apache/storm/pull/3106 < > https://github.com/apache/storm/pull/3106> < > >>> https://github.com/apache/storm/pull/3106 < > https://github.com/apache/storm/pull/3106>> < > >>>>>>> https://github.com/apache/storm/pull/3106 < > https://github.com/apache/storm/pull/3106> < > >>> https://github.com/apache/storm/pull/3106 < > https://github.com/apache/storm/pull/3106>> < > >>>>> https://github.com/apache/storm/pull/3106 < > https://github.com/apache/storm/pull/3106> < > >>> https://github.com/apache/storm/pull/3106 < > https://github.com/apache/storm/pull/3106>>>> > >>>>>>>> > >>>>>>>>> On Aug 19, 2019, at 10:15 AM, Ethan Li < > ethanopensource@gmail.com > >>> > > >>>>> > >> > >>>>>>> ethanopensource@gmail.com> ethanopensource@gmail.com>> > >>> > >>>> > >>>>> wrote: > >>>>>>>>> > >>>>>>>>> So I was preparing for a new release candidate i.e. rc3. I can > build > >>>>> it > >>>>>>> from source without any problem. Then I set up a standalone clust= er > >>> and > >>>>>>> submitted a WordCountTopology. The workers kept restarting becaus= e > of > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> 2019-08-19 15:09:49.635 o.a.s.t.ShellBolt Thread-30 [ERROR] > Halting > >>>>>>> process: ShellBolt died. Command: [python, splitsentence.py], > >>>>> ProcessInfo > >>>>>>> pid:3756, name:split exitCode:-1, errorString: > >>>>>>>>> java.lang.IllegalArgumentException: command sync is not support= ed > >>>>>>>>> at > >>>>>>> > >>>>> > >>> > org.apache.storm.task.ShellBolt$BoltReaderRunnable.run(ShellBolt.java:366= ) > >>>>>>> [storm-client-2.1.0.jar:2.1.0] > >>>>>>>>> at java.lang.Thread.run(Thread.java:748) [?:1.8.0_181] > >>>>>>>>> 2019-08-19 15:09:49.635 o.a.s.e.e.ReportError Thread-30 [ERROR] > >>> Error > >>>>>>>>> java.lang.IllegalArgumentException: command sync is not support= ed > >>>>>>>>> at > >>>>>>> > >>>>> > >>> > org.apache.storm.task.ShellBolt$BoltReaderRunnable.run(ShellBolt.java:366= ) > >>>>>>> [storm-client-2.1.0.jar:2.1.0] > >>>>>>>>> at java.lang.Thread.run(Thread.java:748) [?:1.8.0_181] > >>>>>>>>> 2019-08-19 15:09:49.636 o.a.s.t.ShellBolt Thread-28 [ERROR] > Halting > >>>>>>> process: ShellBolt died. Command: [python, splitsentence.py], > >>>>> ProcessInfo > >>>>>>> pid:3755, name:split exitCode:-1, errorString: > >>>>>>>>> java.lang.IllegalArgumentException: command sync is not support= ed > >>>>>>>>> at > >>>>>>> > >>>>> > >>> > org.apache.storm.task.ShellBolt$BoltReaderRunnable.run(ShellBolt.java:366= ) > >>>>>>> [storm-client-2.1.0.jar:2.1.0] > >>>>>>>>> at java.lang.Thread.run(Thread.java:748) [?:1.8.0_181] > >>>>>>>>> 2019-08-19 15:09:49.637 o.a.s.e.e.ReportError Thread-28 [ERROR] > >>> Error > >>>>>>>>> java.lang.IllegalArgumentException: command sync is not support= ed > >>>>>>>>> at > >>>>>>> > >>>>> > >>> > org.apache.storm.task.ShellBolt$BoltReaderRunnable.run(ShellBolt.java:366= ) > >>>>>>> [storm-client-2.1.0.jar:2.1.0] > >>>>>>>>> at java.lang.Thread.run(Thread.java:748) [?:1.8.0_181] > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>> > >>>>> > >>> > https://github.com/apache/storm/blob/master/storm-client/src/jvm/org/apac= he/storm/task/ShellBolt.java#L365-L367 > < > https://github.com/apache/storm/blob/master/storm-client/src/jvm/org/apac= he/storm/task/ShellBolt.java#L365-L367 > > > >>> < > >>> > https://github.com/apache/storm/blob/master/storm-client/src/jvm/org/apac= he/storm/task/ShellBolt.java#L365-L367 > < > https://github.com/apache/storm/blob/master/storm-client/src/jvm/org/apac= he/storm/task/ShellBolt.java#L365-L367 > > > >>>> > >>>>> < > >>>>> > >>> > https://github.com/apache/storm/blob/master/storm-client/src/jvm/org/apac= he/storm/task/ShellBolt.java#L365-L367 > < > https://github.com/apache/storm/blob/master/storm-client/src/jvm/org/apac= he/storm/task/ShellBolt.java#L365-L367 > > > >>> < > >>> > https://github.com/apache/storm/blob/master/storm-client/src/jvm/org/apac= he/storm/task/ShellBolt.java#L365-L367 > < > https://github.com/apache/storm/blob/master/storm-client/src/jvm/org/apac= he/storm/task/ShellBolt.java#L365-L367 > > > >>>> > >>>>>> > >>>>>>> < > >>>>>>> > >>>>> > >>> > https://github.com/apache/storm/blob/master/storm-client/src/jvm/org/apac= he/storm/task/ShellBolt.java#L365-L367 > < > https://github.com/apache/storm/blob/master/storm-client/src/jvm/org/apac= he/storm/task/ShellBolt.java#L365-L367 > > > >>> < > >>> > https://github.com/apache/storm/blob/master/storm-client/src/jvm/org/apac= he/storm/task/ShellBolt.java#L365-L367 > < > https://github.com/apache/storm/blob/master/storm-client/src/jvm/org/apac= he/storm/task/ShellBolt.java#L365-L367 > > > >>>> > >>>>> < > >>>>> > >>> > https://github.com/apache/storm/blob/master/storm-client/src/jvm/org/apac= he/storm/task/ShellBolt.java#L365-L367 > < > https://github.com/apache/storm/blob/master/storm-client/src/jvm/org/apac= he/storm/task/ShellBolt.java#L365-L367 > > > >>> < > >>> > https://github.com/apache/storm/blob/master/storm-client/src/jvm/org/apac= he/storm/task/ShellBolt.java#L365-L367 > < > https://github.com/apache/storm/blob/master/storm-client/src/jvm/org/apac= he/storm/task/ShellBolt.java#L365-L367 > > > >>>> > >>>>>>> > >>>>>>> I believe we shouldn=E2=80=99t throw exceptions here. > >>>>>>>>> > >>>>>>>>> Will make a pull request to fix it. > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>>> On Aug 14, 2019, at 11:11 PM, Ethan Li < > ethanopensource@gmail.com > >>> > > >>>>> > >> > >>>>>>> ethanopensource@gmail.com> ethanopensource@gmail.com>> > >>> > >>>> > >>>>> wrote: > >>>>>>>>>> > >>>>>>>>>> Hi Taylor, > >>>>>>>>>> > >>>>>>>>>> Mostly I was able to follow the doc > >>>>>>> > >>>>> > >>> > https://github.com/apache/storm/blob/master/RELEASING.md#setting-up-a-vot= e > < > https://github.com/apache/storm/blob/master/RELEASING.md#setting-up-a-vot= e > > > >>> < > >>> > https://github.com/apache/storm/blob/master/RELEASING.md#setting-up-a-vot= e > < > https://github.com/apache/storm/blob/master/RELEASING.md#setting-up-a-vot= e > > > >>>> > >>>>> < > >>>>> > >>> > https://github.com/apache/storm/blob/master/RELEASING.md#setting-up-a-vot= e > < > https://github.com/apache/storm/blob/master/RELEASING.md#setting-up-a-vot= e > > > >>> < > >>> > https://github.com/apache/storm/blob/master/RELEASING.md#setting-up-a-vot= e > < > https://github.com/apache/storm/blob/master/RELEASING.md#setting-up-a-vot= e > > > >>>> > >>>>>> > >>>>>>> < > >>>>>>> > >>>>> > >>> > https://github.com/apache/storm/blob/master/RELEASING.md#setting-up-a-vot= e > < > https://github.com/apache/storm/blob/master/RELEASING.md#setting-up-a-vot= e > > > >>> < > >>> > https://github.com/apache/storm/blob/master/RELEASING.md#setting-up-a-vot= e > < > https://github.com/apache/storm/blob/master/RELEASING.md#setting-up-a-vot= e > > > >>>> > >>>>> < > >>>>> > >>> > https://github.com/apache/storm/blob/master/RELEASING.md#setting-up-a-vot= e > < > https://github.com/apache/storm/blob/master/RELEASING.md#setting-up-a-vot= e > > > >>> < > >>> > https://github.com/apache/storm/blob/master/RELEASING.md#setting-up-a-vot= e > < > https://github.com/apache/storm/blob/master/RELEASING.md#setting-up-a-vot= e > > > >>>> > >>>>>>> , > >>>>>>> except: > >>>>>>>>>> > >>>>>>>>>> For Step 1, I used the following command as suggested. > >>>>>>>>>> mvn release:prepare -P dist,rat,externals,examples > >>>>>>>>>> mvn release:perform -P dist,rat,externals,examples > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> For Step3, I had to run "git checkout tags/v2.1.0 -b v2.1.0= =E2=80=9D so > >>> that > >>>>>>> I can run =E2=80=9Cmvn package=E2=80=9D for storm-dist/binary and= storm-dist/source > >>>>> based > >>>>>>> on v2.1.0. Otherwise if I run =E2=80=9Cmvn package=E2=80=9D on 2.= 1.x-branch, it > will > >>>>> fail > >>>>>>> because the pom version is =E2=80=9C2.1.x-SNAPSHOT=E2=80=9D. > >>>>>>>>>> > >>>>>>>>>> Then I find packages in storm-dist/binary/final-package/target > and > >>>>>>> storm-dist/source/target, sign them, generate checksum and copy > them > >>> to > >>>>> svn. > >>>>>>>>>> > >>>>>>>>>> I think there are something I should do. But please let me kno= w > if > >>> I > >>>>>>> was doing something wrong. I will also update the doc after the > >>>>> release > >>>>>>> is complete. Thank you very much! > >>>>>>>>>> > >>>>>>>>>> Ethan > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>>> On Aug 14, 2019, at 12:24 PM, Ethan Li < > ethanopensource@gmail.com > >>> > > >>>>> > >> > >>>>>>> ethanopensource@gmail.com> ethanopensource@gmail.com>> > >>> > >>>> > >>>>> wrote: > >>>>>>>>>>> > >>>>>>>>>>> I am continuing for another release candidate since the pr is > >>>>> merged. > >>>>>>>>>>> > >>>>>>>>>>>> On Aug 13, 2019, at 11:58 AM, Stig Rohde D=C3=B8ssing < > >>>>>>> stigdoessing@gmail.com stigdoessing@gmail.com > >>> stigdoessing@gmail.com stigdoessing@gmail.com >> >>>>> stigdoessing@gmail.com stigdoessing@gmail.com > >>> stigdoessing@gmail.com stigdoessing@gmail.com >>>> wrote: > >>>>>>>>>>>> > >>>>>>>>>>>> Updated https://github.com/apache/storm/pull/3053 < > https://github.com/apache/storm/pull/3053> < > >>> https://github.com/apache/storm/pull/3053 < > https://github.com/apache/storm/pull/3053>> < > >>>>> https://github.com/apache/storm/pull/3053 < > https://github.com/apache/storm/pull/3053> < > >>> https://github.com/apache/storm/pull/3053 < > https://github.com/apache/storm/pull/3053>>> < > >>>>>>> https://github.com/apache/storm/pull/3053 < > https://github.com/apache/storm/pull/3053> < > >>> https://github.com/apache/storm/pull/3053 < > https://github.com/apache/storm/pull/3053>> < > >>>>> https://github.com/apache/storm/pull/3053 < > https://github.com/apache/storm/pull/3053> < > >>> https://github.com/apache/storm/pull/3053 < > https://github.com/apache/storm/pull/3053>>>> so we don't have > >>>>>>>>>>>> org.apache.storm artifacts in the DEPENDENCY-LICENSES file. > It's > >>>>>>> ready for > >>>>>>>>>>>> review if someone wants to look at it. > >>>>>>>>>>>> > >>>>>>>>>>>> Den tir. 13. aug. 2019 kl. 18.21 skrev Ethan Li < > >>>>>>> ethanopensource@gmail.com > > > >>> ethanopensource@gmail.com ethanopensource@gmail.com >> >>>>> ethanopensource@gmail.com > > > >>> ethanopensource@gmail.com ethanopensource@gmail.com >>>>: > >>>>>>>>>>>> > >>>>>>>>>>>>> Thank you, Taylor. Will delete them. > >>>>>>>>>>>>> > >>>>>>>>>>>>>> On Aug 13, 2019, at 11:19 AM, P. Taylor Goetz < > >>> ptgoetz@gmail.com > > >>>>> ptgoetz@gmail.com >> > >>>>>>> ptgoetz@gmail.com > >>> ptgoetz@gmail.com >>>> wrote: > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> Those can be safely deleted. > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> -Taylor > >>>>>>>>>>>>>> > >>>>>>>>>>>>>>> On Aug 13, 2019, at 12:15 PM, Ethan Li < > >>>>> ethanopensource@gmail.com > > > >>> ethanopensource@gmail.com ethanopensource@gmail.com >> > >>>>>>> ethanopensource@gmail.com> ethanopensource@gmail.com>> > >>> > >>>> > >>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> Do we need/want to clean up the release candidate from > >>>>>>>>>>>>> https://dist.apache.org/repos/dist/dev/storm < > https://dist.apache.org/repos/dist/dev/storm> < > >>> https://dist.apache.org/repos/dist/dev/storm < > https://dist.apache.org/repos/dist/dev/storm>> < > >>>>> https://dist.apache.org/repos/dist/dev/storm < > https://dist.apache.org/repos/dist/dev/storm> < > >>> https://dist.apache.org/repos/dist/dev/storm < > https://dist.apache.org/repos/dist/dev/storm>>> < > >>>>>>> https://dist.apache.org/repos/dist/dev/storm < > https://dist.apache.org/repos/dist/dev/storm> < > >>> https://dist.apache.org/repos/dist/dev/storm < > https://dist.apache.org/repos/dist/dev/storm>> < > >>>>> https://dist.apache.org/repos/dist/dev/storm < > https://dist.apache.org/repos/dist/dev/storm> < > >>> https://dist.apache.org/repos/dist/dev/storm < > https://dist.apache.org/repos/dist/dev/storm>>>> < > >>>>>>>>>>>>> https://dist.apache.org/repos/dist/dev/storm < > https://dist.apache.org/repos/dist/dev/storm> < > >>> https://dist.apache.org/repos/dist/dev/storm < > https://dist.apache.org/repos/dist/dev/storm>> < > >>>>> https://dist.apache.org/repos/dist/dev/storm < > https://dist.apache.org/repos/dist/dev/storm> < > >>> https://dist.apache.org/repos/dist/dev/storm < > https://dist.apache.org/repos/dist/dev/storm>>> < > >>>>>>> https://dist.apache.org/repos/dist/dev/storm < > https://dist.apache.org/repos/dist/dev/storm> < > >>> https://dist.apache.org/repos/dist/dev/storm < > https://dist.apache.org/repos/dist/dev/storm>> < > >>>>> https://dist.apache.org/repos/dist/dev/storm < > https://dist.apache.org/repos/dist/dev/storm> < > >>> https://dist.apache.org/repos/dist/dev/storm < > https://dist.apache.org/repos/dist/dev/storm>>>>> ? > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>> > >>>>> > >>> > https://github.com/apache/storm/blob/master/RELEASING.md#cleaning-up-if-t= he-vote-fails > < > https://github.com/apache/storm/blob/master/RELEASING.md#cleaning-up-if-t= he-vote-fails > > > >>> < > >>> > https://github.com/apache/storm/blob/master/RELEASING.md#cleaning-up-if-t= he-vote-fails > < > https://github.com/apache/storm/blob/master/RELEASING.md#cleaning-up-if-t= he-vote-fails > > > >>>> > >>>>> < > >>>>> > >>> > https://github.com/apache/storm/blob/master/RELEASING.md#cleaning-up-if-t= he-vote-fails > < > https://github.com/apache/storm/blob/master/RELEASING.md#cleaning-up-if-t= he-vote-fails > > > >>> < > >>> > https://github.com/apache/storm/blob/master/RELEASING.md#cleaning-up-if-t= he-vote-fails > < > https://github.com/apache/storm/blob/master/RELEASING.md#cleaning-up-if-t= he-vote-fails > > > >>>> > >>>>>> > >>>>>>> < > >>>>>>> > >>>>> > >>> > https://github.com/apache/storm/blob/master/RELEASING.md#cleaning-up-if-t= he-vote-fails > < > https://github.com/apache/storm/blob/master/RELEASING.md#cleaning-up-if-t= he-vote-fails > > > >>> < > >>> > https://github.com/apache/storm/blob/master/RELEASING.md#cleaning-up-if-t= he-vote-fails > < > https://github.com/apache/storm/blob/master/RELEASING.md#cleaning-up-if-t= he-vote-fails > > > >>>> > >>>>> < > >>>>> > >>> > https://github.com/apache/storm/blob/master/RELEASING.md#cleaning-up-if-t= he-vote-fails > < > https://github.com/apache/storm/blob/master/RELEASING.md#cleaning-up-if-t= he-vote-fails > > > >>> < > >>> > https://github.com/apache/storm/blob/master/RELEASING.md#cleaning-up-if-t= he-vote-fails > < > https://github.com/apache/storm/blob/master/RELEASING.md#cleaning-up-if-t= he-vote-fails > > > >>>> > >>>>>> > >>>>>>>> > >>>>>>>>>>>>> < > >>>>>>>>>>>>> > >>>>>>> > >>>>> > >>> > https://github.com/apache/storm/blob/master/RELEASING.md#cleaning-up-if-t= he-vote-fails > < > https://github.com/apache/storm/blob/master/RELEASING.md#cleaning-up-if-t= he-vote-fails > > > >>> < > >>> > https://github.com/apache/storm/blob/master/RELEASING.md#cleaning-up-if-t= he-vote-fails > < > https://github.com/apache/storm/blob/master/RELEASING.md#cleaning-up-if-t= he-vote-fails > > > >>>> > >>>>> < > >>>>> > >>> > https://github.com/apache/storm/blob/master/RELEASING.md#cleaning-up-if-t= he-vote-fails > < > https://github.com/apache/storm/blob/master/RELEASING.md#cleaning-up-if-t= he-vote-fails > > > >>> < > >>> > https://github.com/apache/storm/blob/master/RELEASING.md#cleaning-up-if-t= he-vote-fails > < > https://github.com/apache/storm/blob/master/RELEASING.md#cleaning-up-if-t= he-vote-fails > > > >>>> > >>>>>> > >>>>>>> < > >>>>>>> > >>>>> > >>> > https://github.com/apache/storm/blob/master/RELEASING.md#cleaning-up-if-t= he-vote-fails > < > https://github.com/apache/storm/blob/master/RELEASING.md#cleaning-up-if-t= he-vote-fails > > > >>> < > >>> > https://github.com/apache/storm/blob/master/RELEASING.md#cleaning-up-if-t= he-vote-fails > < > https://github.com/apache/storm/blob/master/RELEASING.md#cleaning-up-if-t= he-vote-fails > > > >>>> > >>>>> < > >>>>> > >>> > https://github.com/apache/storm/blob/master/RELEASING.md#cleaning-up-if-t= he-vote-fails > < > https://github.com/apache/storm/blob/master/RELEASING.md#cleaning-up-if-t= he-vote-fails > > > >>> < > >>> > https://github.com/apache/storm/blob/master/RELEASING.md#cleaning-up-if-t= he-vote-fails > < > https://github.com/apache/storm/blob/master/RELEASING.md#cleaning-up-if-t= he-vote-fails > > > >>>> > >>>>>> > >>>>>>>>> > >>>>>>>>>>>>> says we do. But we have a lot of rc in > >>>>>>>>>>>>> https://dist.apache.org/repos/dist/dev/storm/ < > https://dist.apache.org/repos/dist/dev/storm/> < > >>> https://dist.apache.org/repos/dist/dev/storm/ < > https://dist.apache.org/repos/dist/dev/storm/>> < > >>>>> https://dist.apache.org/repos/dist/dev/storm/ < > https://dist.apache.org/repos/dist/dev/storm/> < > >>> https://dist.apache.org/repos/dist/dev/storm/ < > https://dist.apache.org/repos/dist/dev/storm/>>> < > >>>>>>> https://dist.apache.org/repos/dist/dev/storm/ < > https://dist.apache.org/repos/dist/dev/storm/> < > >>> https://dist.apache.org/repos/dist/dev/storm/ < > https://dist.apache.org/repos/dist/dev/storm/>> < > >>>>> https://dist.apache.org/repos/dist/dev/storm/ < > https://dist.apache.org/repos/dist/dev/storm/> < > >>> https://dist.apache.org/repos/dist/dev/storm/ < > https://dist.apache.org/repos/dist/dev/storm/>>>> < > >>>>>>>>>>>>> https://dist.apache.org/repos/dist/dev/storm/ < > https://dist.apache.org/repos/dist/dev/storm/> < > >>> https://dist.apache.org/repos/dist/dev/storm/ < > https://dist.apache.org/repos/dist/dev/storm/>> < > >>>>> https://dist.apache.org/repos/dist/dev/storm/ < > https://dist.apache.org/repos/dist/dev/storm/> < > >>> https://dist.apache.org/repos/dist/dev/storm/ < > https://dist.apache.org/repos/dist/dev/storm/>>> < > >>>>>>> https://dist.apache.org/repos/dist/dev/storm/ < > https://dist.apache.org/repos/dist/dev/storm/> < > >>> https://dist.apache.org/repos/dist/dev/storm/ < > https://dist.apache.org/repos/dist/dev/storm/>> < > >>>>> https://dist.apache.org/repos/dist/dev/storm/ < > https://dist.apache.org/repos/dist/dev/storm/> < > >>> https://dist.apache.org/repos/dist/dev/storm/ < > https://dist.apache.org/repos/dist/dev/storm/>>>>> > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> Just want to be absolutely sure about this. Thanks. > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> On Aug 13, 2019, at 10:56 AM, Ethan Li < > >>>>>>> ethanopensource@gmail.com > > > >>> ethanopensource@gmail.com ethanopensource@gmail.com >> >>>>> ethanopensource@gmail.com > > > >>> ethanopensource@gmail.com ethanopensource@gmail.com >>>> > >>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> That sounds better. It will be easier for release. Thank > you > >>>>> for > >>>>>>>>>>>>> looking into this. > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> On Aug 13, 2019, at 10:54 AM, Stig Rohde D=C3=B8ssing < > >>>>>>>>>>>>> stigdoessing@gmail.com > > >>> stigdoessing@gmail.com stigdoessing@gmail.com >> >>>>> stigdoessing@gmail.com stigdoessing@gmail.com > >>> stigdoessing@gmail.com stigdoessing@gmail.com >>>> wrote: > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> Makes sense. I'll take a look at it. Ideally I'd want t= he > >>>>>>> license > >>>>>>>>>>>>> files to > >>>>>>>>>>>>>>>>> just not include org.apache.storm artifacts. I don't > think > >>> we > >>>>>>> need to > >>>>>>>>>>>>> tell > >>>>>>>>>>>>>>>>> people that the project depends on itself. > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> If we can exclude these artifacts from the lists, I don= 't > >>>>> think > >>>>>>> the > >>>>>>>>>>>>> release > >>>>>>>>>>>>>>>>> plugin needs to update these files. > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> Den tir. 13. aug. 2019 kl. 17.36 skrev Ethan Li < > >>>>>>>>>>>>> ethanopensource@gmail.com > > > >>> > >> > >>>>> > > > >>> > >>>>: > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> Thanks Stig. > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> In this case, we probably should abort release process > and > >>>>> get > >>>>>>> this > >>>>>>>>>>>>> merged > >>>>>>>>>>>>>>>>>> into master first. Also we need to make sure it works > with > >>>>> =E2=80=9Cmvn > >>>>>>>>>>>>>>>>>> release:prepare=E2=80=9D since =E2=80=9C mvn release:p= repare=E2=80=9D will > >>>>>>> automatically > >>>>>>>>>>>>> push two > >>>>>>>>>>>>>>>>>> commits. For example, > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> (1) [maven-release-plugin] prepare release v2.1.0: th= is > >>>>> commit > >>>>>>>>>>>>> changes > >>>>>>>>>>>>>>>>>> the pom version to 2.1.0, push the commit, and then > create > >>> a > >>>>>>> git tag > >>>>>>>>>>>>> v2.1.0. > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> (2) [maven-release-plugin] prepare for next developme= nt > >>>>>>> iteration: > >>>>>>>>>>>>> this > >>>>>>>>>>>>>>>>>> commit changes the pom version to 2.1.1-SNAPSHOT. > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> We need DEPENDENCY-LICENSES to be updated on every ste= p. > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>> On Aug 13, 2019, at 10:24 AM, Stig Rohde D=C3=B8ssing= < > >>>>>>>>>>>>> stigdoessing@gmail.com > > >>> stigdoessing@gmail.com stigdoessing@gmail.com >> >>>>> stigdoessing@gmail.com stigdoessing@gmail.com > >>> stigdoessing@gmail.com stigdoessing@gmail.com >>>> > >>>>>>>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>> Oops, sorry that's not right. The license plugin setu= p > was > >>>>>>> disabled > >>>>>>>>>>>>> in > >>>>>>>>>>>>>>>>>>> https://github.com/apache/storm/pull/3031 < > https://github.com/apache/storm/pull/3031> < > >>> https://github.com/apache/storm/pull/3031 < > https://github.com/apache/storm/pull/3031>> < > >>>>> https://github.com/apache/storm/pull/3031 < > https://github.com/apache/storm/pull/3031> < > >>> https://github.com/apache/storm/pull/3031 < > https://github.com/apache/storm/pull/3031>>> < > >>>>>>> https://github.com/apache/storm/pull/3031 < > https://github.com/apache/storm/pull/3031> < > >>> https://github.com/apache/storm/pull/3031 < > https://github.com/apache/storm/pull/3031>> < > >>>>> https://github.com/apache/storm/pull/3031 < > https://github.com/apache/storm/pull/3031> < > >>> https://github.com/apache/storm/pull/3031 < > https://github.com/apache/storm/pull/3031>>>> due to a bug in the > >>>>>>>>>>>>> license > >>>>>>>>>>>>>>>>>>> plugin. It is added back in > >>>>>>>>>>>>> https://github.com/apache/storm/pull/3053 < > https://github.com/apache/storm/pull/3053> < > >>> https://github.com/apache/storm/pull/3053 < > https://github.com/apache/storm/pull/3053>> < > >>>>> https://github.com/apache/storm/pull/3053 < > https://github.com/apache/storm/pull/3053> < > >>> https://github.com/apache/storm/pull/3053 < > https://github.com/apache/storm/pull/3053>>> < > >>>>>>> https://github.com/apache/storm/pull/3053 < > https://github.com/apache/storm/pull/3053> < > >>> https://github.com/apache/storm/pull/3053 < > https://github.com/apache/storm/pull/3053>> < > >>>>> https://github.com/apache/storm/pull/3053 < > https://github.com/apache/storm/pull/3053> < > >>> https://github.com/apache/storm/pull/3053 < > https://github.com/apache/storm/pull/3053>>>>, > >>>>>>>>>>>>>>>>>>> where we've upgraded the plugin. Until that PR goes > in, we > >>>>>>> can't > >>>>>>>>>>>>> easily > >>>>>>>>>>>>>>>>>>> regenerate DEPENDENCY-LICENSES. > >>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>> Den tir. 13. aug. 2019 kl. 17.15 skrev Stig Rohde > D=C3=B8ssing > >>> < > >>>>>>>>>>>>>>>>>>> stigdoessing@gmail.com > > > >>> > >> > >>>>> > > >>> stigdoessing@gmail.com stigdoessing@gmail.com >>>>: > >>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>> There's a script that can help you do it in > >>>>>>>>>>>>>>>>>>>> https://github.com/apache/storm/pull/3053 < > https://github.com/apache/storm/pull/3053> < > >>> https://github.com/apache/storm/pull/3053 < > https://github.com/apache/storm/pull/3053>> < > >>>>> https://github.com/apache/storm/pull/3053 < > https://github.com/apache/storm/pull/3053> < > >>> https://github.com/apache/storm/pull/3053 < > https://github.com/apache/storm/pull/3053>>> < > >>>>>>> https://github.com/apache/storm/pull/3053 < > https://github.com/apache/storm/pull/3053> < > >>> https://github.com/apache/storm/pull/3053 < > https://github.com/apache/storm/pull/3053>> < > >>>>> https://github.com/apache/storm/pull/3053 < > https://github.com/apache/storm/pull/3053> < > >>> https://github.com/apache/storm/pull/3053 < > https://github.com/apache/storm/pull/3053>>>>. It checks the > >>>>>>>>>>>>>>>>>>>> DEPENDENCY-LICENSES and LICENSE-binary contain the > right > >>>>>>>>>>>>> dependencies, > >>>>>>>>>>>>>>>>>> and > >>>>>>>>>>>>>>>>>>>> prints which licenses are redundant or should be > added. > >>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>> For DEPENDENCY-LICENSES specifically you can run "mv= n > >>>>>>>>>>>>>>>>>>>> > >>>>> license:aggregate-add-third-party@generate-and-check-licenses > >>>>>>>>>>>>>>>>>>>> -Dlicense.skipAggregateAddThirdParty=3Dfalse -B" in = the > >>>>> project > >>>>>>>>>>>>> root. It > >>>>>>>>>>>>>>>>>>>> should update the file for you. > >>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>> Den tir. 13. aug. 2019 kl. 17.06 skrev Ethan Li < > >>>>>>>>>>>>>>>>>> ethanopensource@gmail.com ethanopensource@gmail.com> >>> ethanopensource@gmail.com > ethanopensource@gmail.com >>> ethanopensource@gmail.com >> > >>>>> > > > >>> > >>> > >>>>>>>>>>>>>>>>>>>>> : > >>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>> Hi Stig, > >>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>> How do we update > >>>>>>>>>>>>>>>>>>>>> > >>>>>>> https://github.com/apache/storm/blob/v2.1.0/DEPENDENCY-LICENSES? = < > https://github.com/apache/storm/blob/v2.1.0/DEPENDENCY-LICENSES?> < > >>> https://github.com/apache/storm/blob/v2.1.0/DEPENDENCY-LICENSES? < > https://github.com/apache/storm/blob/v2.1.0/DEPENDENCY-LICENSES?>> < > >>>>> https://github.com/apache/storm/blob/v2.1.0/DEPENDENCY-LICENSES? < > https://github.com/apache/storm/blob/v2.1.0/DEPENDENCY-LICENSES?> < > >>> https://github.com/apache/storm/blob/v2.1.0/DEPENDENCY-LICENSES? < > https://github.com/apache/storm/blob/v2.1.0/DEPENDENCY-LICENSES?>>> < > >>>>>>> https://github.com/apache/storm/blob/v2.1.0/DEPENDENCY-LICENSES? = < > https://github.com/apache/storm/blob/v2.1.0/DEPENDENCY-LICENSES?> < > >>> https://github.com/apache/storm/blob/v2.1.0/DEPENDENCY-LICENSES? < > https://github.com/apache/storm/blob/v2.1.0/DEPENDENCY-LICENSES?>> < > >>>>> https://github.com/apache/storm/blob/v2.1.0/DEPENDENCY-LICENSES? < > https://github.com/apache/storm/blob/v2.1.0/DEPENDENCY-LICENSES?> < > >>> https://github.com/apache/storm/blob/v2.1.0/DEPENDENCY-LICENSES? < > https://github.com/apache/storm/blob/v2.1.0/DEPENDENCY-LICENSES?>>>> > >>>>>>>>>>>>> < > >>>>>>>>>>>>>>>>>>>>> > >>>>>>> https://github.com/apache/storm/blob/v2.1.0/DEPENDENCY-LICENSES? = < > https://github.com/apache/storm/blob/v2.1.0/DEPENDENCY-LICENSES?> < > >>> https://github.com/apache/storm/blob/v2.1.0/DEPENDENCY-LICENSES? < > https://github.com/apache/storm/blob/v2.1.0/DEPENDENCY-LICENSES?>> < > >>>>> https://github.com/apache/storm/blob/v2.1.0/DEPENDENCY-LICENSES? < > https://github.com/apache/storm/blob/v2.1.0/DEPENDENCY-LICENSES?> < > >>> https://github.com/apache/storm/blob/v2.1.0/DEPENDENCY-LICENSES? < > https://github.com/apache/storm/blob/v2.1.0/DEPENDENCY-LICENSES?>>> < > >>>>>>> https://github.com/apache/storm/blob/v2.1.0/DEPENDENCY-LICENSES? = < > https://github.com/apache/storm/blob/v2.1.0/DEPENDENCY-LICENSES?> < > >>> https://github.com/apache/storm/blob/v2.1.0/DEPENDENCY-LICENSES? < > https://github.com/apache/storm/blob/v2.1.0/DEPENDENCY-LICENSES?>> < > >>>>> https://github.com/apache/storm/blob/v2.1.0/DEPENDENCY-LICENSES? < > https://github.com/apache/storm/blob/v2.1.0/DEPENDENCY-LICENSES?> < > >>> https://github.com/apache/storm/blob/v2.1.0/DEPENDENCY-LICENSES? < > https://github.com/apache/storm/blob/v2.1.0/DEPENDENCY-LICENSES?>>>>> > >>>>>>>>>>>>> Is > >>>>>>>>>>>>>>>>>>>>> there a command I can use? Or I just replace string= s > >>>>>>> manually? > >>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>> Thanks > >>>>>>>>>>>>>>>>>>>>> Ethan > >>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>> On Aug 12, 2019, at 3:54 PM, Ethan Li < > >>>>>>> ethanopensource@gmail.com > > > >>> ethanopensource@gmail.com ethanopensource@gmail.com >> >>>>> ethanopensource@gmail.com > > > >>> ethanopensource@gmail.com ethanopensource@gmail.com >>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>> Yes my public keys in that file. Thanks! Ready to > set > >>> up > >>>>> a > >>>>>>> vote. > >>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>> On Aug 12, 2019, at 3:52 PM, P. Taylor Goetz < > >>>>>>> ptgoetz@gmail.com ptgoetz@gmail.com > >>> ptgoetz@gmail.com >> ptgoetz@gmail.com> > >>> > > >>>>> ptgoetz@gmail.com >>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>> Yes. Is you public key in that file? If not you > should > >>>>>>> add it. > >>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>> -Taylor > >>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>> On Aug 12, 2019, at 4:15 PM, Ethan Li < > >>>>>>>>>>>>> ethanopensource@gmail.com > > > >>> > >> > >>>>> > > > >>> > >>>> > >>>>>>>>>>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>> I have one more question before I can start a > vote. > >>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>> In previous [VOTE] thread, Taylor always has thi= s: > >>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>> The release artifacts are signed with the > following > >>>>> key: > >>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>> > >>>>> > >>> > https://git-wip-us.apache.org/repos/asf?p=3Dstorm.git;a=3Dblob_plain;f=3D= KEYS;hb=3D22b832708295fa2c15c4f3c70ac0d2bc6fded4bd > < > https://git-wip-us.apache.org/repos/asf?p=3Dstorm.git;a=3Dblob_plain;f=3D= KEYS;hb=3D22b832708295fa2c15c4f3c70ac0d2bc6fded4bd > > > >>> < > >>> > https://git-wip-us.apache.org/repos/asf?p=3Dstorm.git;a=3Dblob_plain;f=3D= KEYS;hb=3D22b832708295fa2c15c4f3c70ac0d2bc6fded4bd > < > https://git-wip-us.apache.org/repos/asf?p=3Dstorm.git;a=3Dblob_plain;f=3D= KEYS;hb=3D22b832708295fa2c15c4f3c70ac0d2bc6fded4bd > > > >>>> > >>>>> < > >>>>> > >>> > https://git-wip-us.apache.org/repos/asf?p=3Dstorm.git;a=3Dblob_plain;f=3D= KEYS;hb=3D22b832708295fa2c15c4f3c70ac0d2bc6fded4bd > < > https://git-wip-us.apache.org/repos/asf?p=3Dstorm.git;a=3Dblob_plain;f=3D= KEYS;hb=3D22b832708295fa2c15c4f3c70ac0d2bc6fded4bd > > > >>> < > >>> > https://git-wip-us.apache.org/repos/asf?p=3Dstorm.git;a=3Dblob_plain;f=3D= KEYS;hb=3D22b832708295fa2c15c4f3c70ac0d2bc6fded4bd > >>>> > >>>>>> > >>>>>>> < > >>>>>>> > >>>>> > >>> > https://git-wip-us.apache.org/repos/asf?p=3Dstorm.git;a=3Dblob_plain;f=3D= KEYS;hb=3D22b832708295fa2c15c4f3c70ac0d2bc6fded4bd > >>>>> < > >>>>> > >>> > https://git-wip-us.apache.org/repos/asf?p=3Dstorm.git;a=3Dblob_plain;f=3D= KEYS;hb=3D22b832708295fa2c15c4f3c70ac0d2bc6fded4bd > >>>>>> > >>>>>>>> > >>>>>>>>>>>>>>>>>>>>> < > >>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>> > >>>>> > >>> > https://git-wip-us.apache.org/repos/asf?p=3Dstorm.git;a=3Dblob_plain;f=3D= KEYS;hb=3D22b832708295fa2c15c4f3c70ac0d2bc6fded4bd > >>>>>>> < > >>>>>>> > >>>>> > >>> > https://git-wip-us.apache.org/repos/asf?p=3Dstorm.git;a=3Dblob_plain;f=3D= KEYS;hb=3D22b832708295fa2c15c4f3c70ac0d2bc6fded4bd > >>>>>>>> > >>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>> Does anyone know where to find the updated KEYs > file? > >>>>>>> Should I > >>>>>>>>>>>>> just > >>>>>>>>>>>>>>>>>>>>> use https://www.apache.org/dist/storm/KEYS < > >>>>>>>>>>>>>>>>>>>>> https://www.apache.org/dist/storm/KEYS> ? > >>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>> Thanks very much > >>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>> On Aug 12, 2019, at 9:44 AM, Ethan Li < > >>>>>>>>>>>>> ethanopensource@gmail.com> > >>>>>>>>>>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>> Thanks Stig and Taylor! It worked. I will > continue > >>> the > >>>>>>>>>>>>> process now > >>>>>>>>>>>>>>>>>>>>> and update the documentation later. > >>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>> On Aug 12, 2019, at 9:40 AM, P. Taylor Goetz < > >>>>>>>>>>>>> ptgoetz@gmail.com> > >>>>>>>>>>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>> For the 2.x version lines, there are a bunch o= f > >>>>>>> profiles you > >>>>>>>>>>>>> need > >>>>>>>>>>>>>>>>>>>>> to enable. This is what I use when preparing a > release: > >>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>> -P > dist,include-shaded-deps,rat,externals,examples > >>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>> -Taylor > >>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>> On Aug 12, 2019, at 9:27 AM, Stig Rohde > D=C3=B8ssing < > >>>>>>>>>>>>>>>>>>>>> stigdoessing@gmail.com> wrote: > >>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>> Try enabling the "dist" profile by adding "-P > >>>>>>>>>>>>>>>>>>>>> dist,externals,examples" to > >>>>>>>>>>>>>>>>>>>>>>>>>>> the command you're running. See > >>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>> https://github.com/apache/storm/blob/master/pom.xml#L518. > >>>>>>>>>>>>> Unless > >>>>>>>>>>>>>>>>>>>>> you enable > >>>>>>>>>>>>>>>>>>>>>>>>>>> that profile, the storm-dist modules aren't i= n > the > >>>>>>> reactor. > >>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>> Den man. 12. aug. 2019 kl. 15.15 skrev Ethan > Li < > >>>>>>>>>>>>>>>>>>>>> ethanopensource@gmail.com>: > >>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>> Just in case if anyone happens to know the > >>> answer: > >>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>> I created a branch > >>>>>>>>>>>>>>>>>>>>> https://github.com/apache/storm/tree/2.1.x-branch < > >>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>> https://github.com/apache/storm/tree/2.1.x-branch> > >>>>>>> and ran > >>>>>>>>>>>>>>>>>>>>> =E2=80=9Cmvn:prepare=E2=80=9D > >>>>>>>>>>>>>>>>>>>>>>>>>>>> and =E2=80=9Cmvn:perform=E2=80=9D. It create= d two commits and > >>>>>>> created a > >>>>>>>>>>>>> v2.1.0 > >>>>>>>>>>>>>>>>>>>>> git tag. But > >>>>>>>>>>>>>>>>>>>>>>>>>>>> I realized that the pom version under > storm-dist > >>>>> was > >>>>>>> not > >>>>>>>>>>>>> updated > >>>>>>>>>>>>>>>>>>>>> and it=E2=80=99s > >>>>>>>>>>>>>>>>>>>>>>>>>>>> still 2.0.1-SNAPSHOT. I checked the commits = in > >>>>> other > >>>>>>> tags > >>>>>>>>>>>>> like > >>>>>>>>>>>>>>>>>>>>>>>>>>>> > https://github.com/apache/storm/commits/v2.0.0 < > >>>>>>>>>>>>>>>>>>>>>>>>>>>> > https://github.com/apache/storm/commits/v2.0.0> > >>>>> and > >>>>>>> it > >>>>>>>>>>>>> looks > >>>>>>>>>>>>>>>>>> like > >>>>>>>>>>>>>>>>>>>>>>>>>>>> storm-dist got updated within the > =E2=80=9Cmvn:prepare=E2=80=9D > >>>>>>> step. How > >>>>>>>>>>>>> do I > >>>>>>>>>>>>>>>>>>>>> get > >>>>>>>>>>>>>>>>>>>>>>>>>>>> storm-dist pom version updated with > =E2=80=9Cmv:prepare=E2=80=9D? > >>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>> I am currently blocked on this. Any help wil= l > be > >>>>>>>>>>>>> appreciated. > >>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks, > >>>>>>>>>>>>>>>>>>>>>>>>>>>> Ethan > >>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Aug 12, 2019, at 2:38 AM, Stig Rohde > D=C3=B8ssing > >>> < > >>>>>>>>>>>>>>>>>>>>> stigdoessing@gmail.com> > >>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>> Sounds good Ethan. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>> Derek, I also think being clear about how > long > >>> we > >>>>>>> expect > >>>>>>>>>>>>> to > >>>>>>>>>>>>>>>>>>>>> support a > >>>>>>>>>>>>>>>>>>>>>>>>>>>>> release line is a good idea. Maybe we shoul= d > do > >>> a > >>>>>>> separate > >>>>>>>>>>>>>>>>>>>>> discuss thread > >>>>>>>>>>>>>>>>>>>>>>>>>>>>> on this, or if you already have a good idea > for > >>>>>>> what the > >>>>>>>>>>>>> policy > >>>>>>>>>>>>>>>>>>>>> should > >>>>>>>>>>>>>>>>>>>>>>>>>>>> look > >>>>>>>>>>>>>>>>>>>>>>>>>>>>> like you could put it up as a PR for either > the > >>>>>>> Downloads > >>>>>>>>>>>>> page > >>>>>>>>>>>>>>>>>>>>> or a new > >>>>>>>>>>>>>>>>>>>>>>>>>>>>> page on the Storm site? > >>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>> Den s=C3=B8n. 11. aug. 2019 kl. 08.37 skrev= Ethan > Li > >>> < > >>>>>>>>>>>>>>>>>>>>>>>>>>>> ethanopensource@gmail.com>: > >>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> I am doing the release following > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>> https://github.com/apache/storm/blob/master/RELEASING.md > >>>>>>>>>>>>> < > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>> https://github.com/apache/storm/blob/master/RELEASING.md> > >>>>>>>>>>>>> . I > >>>>>>>>>>>>>>>>>>>>> made some > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> progress but I have some questions so I ju= st > >>> sent > >>>>>>> an > >>>>>>>>>>>>> email to > >>>>>>>>>>>>>>>>>>>>> Taylor. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Please don=E2=80=99t merge anything to mas= ter or > >>>>>>> 2.1.x-branch > >>>>>>>>>>>>> for now. > >>>>>>>>>>>>>>>>>>>>> Thanks > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Best, > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Ethan > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Aug 9, 2019, at 4:45 PM, Ethan Li < > >>>>>>>>>>>>>>>>>>>>> ethanopensource@gmail.com> > >>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Currently we have two outstanding PRs tha= t > we > >>>>>>> wanted to > >>>>>>>>>>>>>>>>>>>>> include in the > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> new release: > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> https://github.com/apache/storm/pull/3096 > < > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> https://github.com/apache/storm/pull/3096> > >>>>>>> (Travis has > >>>>>>>>>>>>> some > >>>>>>>>>>>>>>>>>>>>> issues > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> connecting to repository.apache.org < > >>>>>>>>>>>>>>>>>>>>> http://repository.apache.org/> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> recently. Travis build fails consistently) > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> https://github.com/apache/storm/pull/2878 > < > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> https://github.com/apache/storm/pull/2878> > >>> (Some > >>>>>>>>>>>>> comments are > >>>>>>>>>>>>>>>>>>>>> to be > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> addressed but Author hasn=E2=80=99t respon= ded yet.) > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> It=E2=80=99s not absolutely necessary to = include > them > >>> in > >>>>>>> this > >>>>>>>>>>>>> new > >>>>>>>>>>>>>>>>>>>>> release so I > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> think I should move forward with the relea= se > >>>>>>> process. > >>>>>>>>>>>>> These > >>>>>>>>>>>>>>>>>> two > >>>>>>>>>>>>>>>>>>>>> and > >>>>>>>>>>>>>>>>>>>>>>>>>>>> other > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> PRs can be included in the next release. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> For the release, I will create a new bran= ch > >>>>>>> 2.1.x-branch > >>>>>>>>>>>>>>>>>> based > >>>>>>>>>>>>>>>>>>>>> on > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> current master branch, and release 2.1.0 > from > >>>>>>> there. I > >>>>>>>>>>>>> will > >>>>>>>>>>>>>>>>>>>>> then move > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> master to 2.2.0-SNAPSHOT. Please let me > know > >>> if > >>>>>>> there > >>>>>>>>>>>>> is any > >>>>>>>>>>>>>>>>>>>>>>>>>>>> objections. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks, > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Ethan > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Aug 9, 2019, at 2:53 PM, Derek Dagit = < > >>>>>>>>>>>>> dagit@apache.org > >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> dagit@apache.org>> wrote: > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> We might not able to say how long we > want to > >>>>>>> support a > >>>>>>>>>>>>>>>>>>>>> specific > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> release line but I would love to see a > clear > >>>>>>> release > >>>>>>>>>>>>> policy > >>>>>>>>>>>>>>>>>>>>> being > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> made. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> That makes sense. It seems better for us > not > >>> to > >>>>>>> choose > >>>>>>>>>>>>> a > >>>>>>>>>>>>>>>>>>>>> specific > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> calendar date or duration of time. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> - We do not want too many release lines > >>>>> supported > >>>>>>>>>>>>>>>>>>>>> concurrently. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> - We want devs and users to know what to > >>>>> expect. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> -- > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Derek > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Fri, Aug 09, 2019 at 10:32:59AM -0500= , > >>> Ethan > >>>>>>> Li > >>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Derek, > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> I think it=E2=80=99s a good idea to be = more > clear on > >>>>> the > >>>>>>>>>>>>> versioning > >>>>>>>>>>>>>>>>>>>>> and > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> release process so users and developers kn= ow > >>> what > >>>>>>> to > >>>>>>>>>>>>> expect. > >>>>>>>>>>>>>>>>>> We > >>>>>>>>>>>>>>>>>>>>> might > >>>>>>>>>>>>>>>>>>>>>>>>>>>> not > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> able to say how long we want to support a > >>>>> specific > >>>>>>>>>>>>> release > >>>>>>>>>>>>>>>>>> line > >>>>>>>>>>>>>>>>>>>>> but I > >>>>>>>>>>>>>>>>>>>>>>>>>>>> would > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> love to see a clear release policy being > made. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks, > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Ethan > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Aug 9, 2019, at 8:53 AM, Derek Dagi= t > < > >>>>>>>>>>>>> dagit@apache.org > >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> dagit@apache.org>> wrote: > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Fri, Aug 09, 2019 at 02:35:57PM > +0200, > >>>>> Stig > >>>>>>> Rohde > >>>>>>>>>>>>>>>>>>>>> D=C3=B8ssing wrote: > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Where on the Traffic Server page do > they > >>>>> list > >>>>>>> how > >>>>>>>>>>>>> long > >>>>>>>>>>>>>>>>>>>>> their > >>>>>>>>>>>>>>>>>>>>>>>>>>>> release > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> trains survive? I only see dates of > >>> release, > >>>>>>> not > >>>>>>>>>>>>> how long > >>>>>>>>>>>>>>>>>>>>> e.g. 7.x > >>>>>>>>>>>>>>>>>>>>>>>>>>>> is > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> supposed to receive support. Derek, > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> This is a better link: > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>> > >>>>>>> https://cwiki.apache.org/confluence/display/TS/Release+Management > >>>>>>>>>>>>> < > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>> > >>>>>>> https://cwiki.apache.org/confluence/display/TS/Release+Management > >>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> This example, where "RM" means "Releas= e > >>>>>>> Manager": > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 1. We promise to make 1 major release= / > >>>>> year, > >>>>>>> but > >>>>>>>>>>>>> the RM > >>>>>>>>>>>>>>>>>>>>> and > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> community > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> can of course make more as necessary > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 2. We only make releases off the LTS > >>>>> branches, > >>>>>>>>>>>>> which are > >>>>>>>>>>>>>>>>>>>>> cut once a > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> year off master > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 3. Master is always open, for any typ= e > of > >>>>>>> change > >>>>>>>>>>>>>>>>>> (including > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> incompatible changes). But don't brea= k > >>>>>>>>>>>>> compatibility just > >>>>>>>>>>>>>>>>>>>>> for fun! > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 4. Master is always stable, i.e. > commits > >>>>>>> should be > >>>>>>>>>>>>>>>>>>>>> properly tested > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> and > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> reviewed before committed to master. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 5. All releases are stable releases, > >>>>> following > >>>>>>>>>>>>> strict > >>>>>>>>>>>>>>>>>>>>> Semantic > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Versioning. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 6. Minor releases are made at the > >>> discretion > >>>>>>> at the > >>>>>>>>>>>>>>>>>>>>> discretion of > >>>>>>>>>>>>>>>>>>>>>>>>>>>> the > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> community and the RM. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 7. Minor releases can include new > (small / > >>>>>>> safe) > >>>>>>>>>>>>>>>>>> features, > >>>>>>>>>>>>>>>>>>>>> but must > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> be > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> compatible within the LTS major > version. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 8. The LTS cycle, 2 years + 6 months > >>> Sunset, > >>>>>>> does > >>>>>>>>>>>>> not > >>>>>>>>>>>>>>>>>>>>> reset when we > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> make a minor release. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Now, I am not proposing we do exactly > this. > >>>>>>> The goal > >>>>>>>>>>>>> would > >>>>>>>>>>>>>>>>>>>>> be to set > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> expectations among developers and the > >>>>>>> community, and > >>>>>>>>>>>>> here > >>>>>>>>>>>>>>>>>>>>> is one > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> concrete example of how it could be > done. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> If we're going to promise that a > release > >>>>> line > >>>>>>>>>>>>> survives > >>>>>>>>>>>>>>>>>> for > >>>>>>>>>>>>>>>>>>>>> a given > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> amount of time, I think we should do > it at > >>>>>>> the major > >>>>>>>>>>>>>>>>>>>>> version level > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> only > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Yeah, that sounds reasonable to me. If > we > >>>>>>> choose to > >>>>>>>>>>>>> commit > >>>>>>>>>>>>>>>>>>>>> to > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> something > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> like the above, we should base the > decision > >>>>> in > >>>>>>> part > >>>>>>>>>>>>> on > >>>>>>>>>>>>>>>>>> what > >>>>>>>>>>>>>>>>>>>>> kind of > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> resources we have so that we do not > >>>>>>> over-commit. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Den fre. 9. aug. 2019 kl. 00.15 skrev > >>> Derek > >>>>>>> Dagit < > >>>>>>>>>>>>>>>>>>>>>>>>>>>> dagit@apache.org > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >: > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> What do we think about defining > Long-Term > >>>>>>> Support > >>>>>>>>>>>>>>>>>>>>> branches with a > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> fixed > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> period of support? > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> For example, we could say 2.0.x is a= n > LTS > >>>>>>> release > >>>>>>>>>>>>> line > >>>>>>>>>>>>>>>>>>>>> with > >>>>>>>>>>>>>>>>>>>>>>>>>>>> support > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ending no earlier than a certain > calendar > >>>>>>> date. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> The date could be extended, and it > might > >>>>>>>>>>>>> ultimately be > >>>>>>>>>>>>>>>>>>>>> governed by > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> the > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> timing of the subsequent release > (e.g., > >>>>>>> 2.1.x or > >>>>>>>>>>>>> 3.0.x). > >>>>>>>>>>>>>>>>>>>>> Keeping > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> things > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> clear would imply semantic versionin= g > as > >>>>>>> mentioned > >>>>>>>>>>>>>>>>>> earlier > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> (https://semver.org/ < > >>> https://semver.org/ > >>>>>> ). > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Apache Traffic Server does something > like > >>>>>>> this, to > >>>>>>>>>>>>> name > >>>>>>>>>>>>>>>>>>>>> one > >>>>>>>>>>>>>>>>>>>>>>>>>>>> project: > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>> https://trafficserver.apache.org/downloads > >>>>> < > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> https://trafficserver.apache.org/downloads= > > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Having a regular cadence of releases > >>> might > >>>>>>> also > >>>>>>>>>>>>> help > >>>>>>>>>>>>>>>>>> make > >>>>>>>>>>>>>>>>>>>>> the > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> process > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> easier and help set expectations for > >>> users > >>>>>>> and > >>>>>>>>>>>>> devs. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> -- > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Derek > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Thu, Aug 08, 2019 at 02:50:07PM > -0500, > >>>>>>> Ethan Li > >>>>>>>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Currently we don=E2=80=99t have a > 2.0.x-branch > >>> and > >>>>>>> master > >>>>>>>>>>>>> is > >>>>>>>>>>>>>>>>>>>>> actually > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> =E2=80=9C2.0.1-SNAPSHOT=E2=80=9D. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> So if we do a 2.1.0 release, we > will > >>>>>>> create a > >>>>>>>>>>>>>>>>>>>>> 2.1.x-branch > >>>>>>>>>>>>>>>>>>>>>>>>>>>> based > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> on > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> current master, release from there. > And > >>> we > >>>>>>> change > >>>>>>>>>>>>> master > >>>>>>>>>>>>>>>>>>>>> to > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> =E2=80=9C2.2.0-SNAPSHOT=E2=80=9D. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> But we will have one problem: we wi= ll > >>> lose > >>>>>>> 2.0.x > >>>>>>>>>>>>>>>>>> release > >>>>>>>>>>>>>>>>>>>>> line. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> There are two things I can do: > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 1) create a 2.0.x-branch based on > v2.0.0 > >>>>>>> tag. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 2) ignore it. If there is an issue > with > >>>>>>> 2.0.x > >>>>>>>>>>>>> release, > >>>>>>>>>>>>>>>>>>>>> ask users > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> to > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> upgrade to 2.1.0. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> I prefer 1) but not sure if it=E2= =80=99s the > >>> right > >>>>>>> way to > >>>>>>>>>>>>> make > >>>>>>>>>>>>>>>>>>>>> things > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> right. Or > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> please let me know if I misunderstoo= d > >>>>>>> something > >>>>>>>>>>>>> and it=E2=80=99s > >>>>>>>>>>>>>>>>>>>>> not an > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> issue. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Btw, I am seeing the same issue wit= h > >>>>>>> 1.x-branch. > >>>>>>>>>>>>> We > >>>>>>>>>>>>>>>>>>>>> shouldn=E2=80=99t > >>>>>>>>>>>>>>>>>>>>>>>>>>>> have > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 1.x-branch. Instead, we should have > >>>>>>> 1.2.x-branch. > >>>>>>>>>>>>> But > >>>>>>>>>>>>>>>>>>>>> this is not > >>>>>>>>>>>>>>>>>>>>>>>>>>>> a > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> problem > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> since we will not release 1.3.x. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks, > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Ethan > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Aug 7, 2019, at 10:43 AM, Ethan > Li < > >>>>>>>>>>>>>>>>>>>>>>>>>>>> ethanopensource@gmail.com> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Yes thanks. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Aug 7, 2019, at 10:39 AM, Stig > >>> Rohde > >>>>>>> D=C3=B8ssing > >>>>>>>>>>>>> < > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> stigdoessing@gmail.com> wrote: > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Sounds great. Remember to add you= r > 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 < > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ethanopensource@gmail.com>: > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> I got my pgp key signed by Bryan > W. > >>>>> Call > >>>>>>> < > >>>>>>>>>>>>>>>>>>>>> bcall@apache.org > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 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 chanc= e. > >>>>>>> Thanks > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Ethan > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Aug 1, 2019, at 4:19 AM, Sti= g > >>> Rohde > >>>>>>>>>>>>> D=C3=B8ssing < > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> stigdoessing@gmail.com> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks Ethan, yes 2.1.0 makes > sense. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Den man. 29. jul. 2019 kl. 23.4= 3 > >>> skrev > >>>>>>> Ethan > >>>>>>>>>>>>> Li < > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ethanopensource@gmail.com>: > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> It=E2=80=99s a good point. I w= ill 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 < > >>>>>>>>>>>>>>>>>>>>>>>>>>>> hmclouro@gmail.com > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 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 the > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> release, plus any "new" testi= ng > >>> 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. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks, > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Hugo > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Mon, Jul 29, 2019 at 7:15 = AM > >>>>> Ethan > >>>>>>> Li < > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ethanopensource@gmail.com> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks Stig. I will look int= o > 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 > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> following > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> (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 Etha= n. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Den fre. 26. jul. 2019 kl= . > >>> 19.16 > >>>>>>> skrev > >>>>>>>>>>>>> Ethan > >>>>>>>>>>>>>>>>>>>>> Li < > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ethanopensource@gmail.com>= : > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> It=E2=80=99s good idea t= o do more > >>>>>>> frequent > >>>>>>>>>>>>> release. > >>>>>>>>>>>>>>>>>> I > >>>>>>>>>>>>>>>>>>>>> can run > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> the > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> next > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> release. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> I will take a look at bo= th > >>> 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. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 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 mont= hs > >>>>> 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 lis= t > 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?), sinc= e > >>> 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 tak= e > a > >>>>> look > >>>>>>> at > >>>>>>>>>>>>>>>>>> currently > >>>>>>>>>>>>>>>>>>>>> open PRs > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> and > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> decide > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 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? > > > > --00000000000048187a0590a25ae0--