Re: [DISCUSS] Call for PMC Members and Contributors

[P. Taylor Goetz]

Thanks for the reminder Richard,

In response, I’ve bumped the PMC-private discussion around adding new members 
interested in contributing.

- Taylor

> On May 11, 2023, at 8:39 AM, Richard Zowalla  wrote:
> 
> Hello,
> 
> I know we are all busy with our day jobs, but is there any news?
> 
> We had some activity after a move to the attic was proposed. In the process, 
> a few people volunteered to help with the project.
> 
> A few weeks later, IMHO we are back to where we were before the proposal. 
> Mails are going nowhere and I've heard of a few people planning to just fork 
> Storm to get an updated version into production. 
> 
> If we want to prevent that and Storm should really be put into maintenance 
> mode, then we should urgently take care of expanding the PMC/Committers 
> circle, so that we are able to put out timely releases again and the work 
> regarding maintenance is distributed on more than just 2 shoulders.
> 
> Don't take it as a rant, it's just my opinion as someone who runs a Storm 
> Cluster in production and would love to help the project to sustain.
> 
> Gruß
> Richard
> 
> On 2023/05/02 12:58:00 Richard Zowalla wrote:
>> Any updates? :-)
>> 
>> Think Storm would benefit from a new release soon...
>> 
>> Am Mittwoch, dem 22.02.2023 um 18:02 -0500 schrieb P. Taylor Goetz:
>>> Quick update:
>>> 
>>> The ASF Board voted to accept both our report and the resolution to
>>> change PMC Chair. Board feedback on our report was positive.
>>> 
>>> The next step is to expand the the PMC/Committers group. Official
>>> votes will necessarily be private, but I see no reason nominations
>>> can’t be public.
>>> 
>>> So lets open a thread to talk about adding new contributors to the
>>> PMC. Feel free to:
>>> 
>>> 1. Volunteer to support the project as a PMC Member/Committer..
>>> 2. Nominate someone become PMC/Committer
>>> 
>>> I have a few candidates in mind, and will follow up accordingly.
>>> Votes for new members will be private, but successful votes for new
>>> members will be announced on the public lists.
>>> 
>>> One important way to contribute is to volunteer as a release manager
>>> for any given release, even if we release infrequently (e.g. only in
>>> response to a serious bug or security issue. I don’t have the
>>> bandwidth to act in that role, though I will commit to support voting
>>> on releases, etc. Ideally we would want at least two folks ready to
>>> step into that role, but we can get by with one if necessary.
>>> 
>>> Thanks again to everyone who’s expressed interest in contributing to
>>> the project.
>>> 
>>> - Taylor
>> 
>> 

[DISCUSS] Call for PMC Members and Contributors

[P. Taylor Goetz]

Quick update:

The ASF Board voted to accept both our report and the resolution to change PMC 
Chair. Board feedback on our report was positive.

The next step is to expand the the PMC/Committers group. Official votes will 
necessarily be private, but I see no reason nominations can’t be public.

So lets open a thread to talk about adding new contributors to the PMC. Feel 
free to:

1. Volunteer to support the project as a PMC Member/Committer..
2. Nominate someone become PMC/Committer

I have a few candidates in mind, and will follow up accordingly. Votes for new 
members will be private, but successful votes for new members will be announced 
on the public lists.

One important way to contribute is to volunteer as a release manager for any 
given release, even if we release infrequently (e.g. only in response to a 
serious bug or security issue. I don’t have the bandwidth to act in that role, 
though I will commit to support voting on releases, etc. Ideally we would want 
at least two folks ready to step into that role, but we can get by with one if 
necessary.

Thanks again to everyone who’s expressed interest in contributing to the 
project.

- Taylor

Re: [DISCUSSION] Apache Storm and moving to the Attic

[P. Taylor Goetz]

An anecdote that might be applicable:

Look at version controls over the last few decades:

CVS —> Apache Subersion —> Git

Each transition was a major improvement.

That may lead you believe that Subversion is dead and long gone. And you would 
be wrong.

Subversion is still alive because it stil  has a user base, Talso has one of, 
if not the most, open-door policies to entry: Want committer access? Just ask 
and you’re in. If you eff up, someone will catch it and revert it.


We’ve had a few express interest in continuing the project. Why not elevate 
them to Committer/PMC? 

-Taylor


> On Feb 2, 2023, at 12:06 AM, P. Taylor Goetz  wrote:
> 
> IMO, there are tow scenarios:
> 
> 1. Storm is in dead. No one uses it anymore, and no one needs security 
> patches, etc.
> 2. Storm is in maintenance mode. While new features may not be added, there 
> are enough contributors left tp at least address any security concerns.
> 
> Wether we pursue the attic o projectr continuation is really up to the 
> community. Anyone who want to step up and help continue the project should be 
> considered a PMC candidate.
> 
> As I’ve said in other threads, I’m willing to act as PMC chair whatever the 
> PMC decides.
> 
> But for now we have ne official liaison to ther ASF board. PMC members need 
> to elect a chair, whether we choose to continue or head to the attic.
> 
> I would lean toward lowering the bar for PMC membership to anyone interested 
> in ongoing maintenance. 
> 
> I’m still willing to serve as the board liaison (PMC Chair) in either case of 
> retirement or continuation. I’d also support anyone else willing to take the 
> position.  The position needs to be filled either way.
> 
> This is a decision that affects both developers and users. Thank you Aaron 
> for bringing it to the attention of the  broader community.
> 
> -Taylor
> 
>> On Feb 1, 2023, at 9:26 PM, sunil yadav > <mailto:raosutn...@gmail.com>> wrote:
>> 
>> One side note looking to see what folks are migrating or moved to if not 
>> using Storm actively. Any cloud native DAG platform to recommend?
>> 
>> -Sunil
>> 
>> On Wed, Feb 1, 2023 at 6:12 PM Stephen Powis via user > <mailto:u...@storm.apache.org>> wrote:
>> Ah Yea, also not opposed to the move to the attic if it's determined to be 
>> most appropriate, but I had a similar experience as Richard where I 
>> submitted some PRs, asked for comments/thoughts/review, and even offered to 
>> take over ownership of one of the sub modules and got no responses.  Perhaps 
>> I just submitted under the wrong forum to get an answer, but definitely a 
>> bummer, and would love to see the project/community get revived.
>> 
>> - Stephen
>> 
>> On Wed, Feb 1, 2023 at 10:09 PM Richard Zowalla > <mailto:r...@apache.org>> wrote:
>> Hi Aaron,
>> 
>> I am CC the users@ list as they weren't contained in the initial
>> proposal. Perhaps, there are people or institutions in the wild, who
>> want to volunteer or give it a try (still at the ASF level). 
>> 
>> Of course it shouldn't prevent a VOTE for moving to the attic, but an
>> additional try to get some more attention (if needed).
>> 
>> Gruß
>> Richard
>> 
>> 
>> Am Dienstag, dem 31.01.2023 um 08:00 -0600 schrieb Aaron Niskode-
>> Dossett:
>> > Thank you to those who responded. Given that the low number of
>> > responses I
>> > am going to start a vote on moving to the attic tomorrow.
>> > 
>> > One other note: A vote to move to the attic would not mean the end of
>> > Storm, the project can be forked by anyone who wants to continue the
>> > work
>> > (just as it can be forked today), it would just be outside of the
>> > ASF.
>> > 
>> > On Thu, Jan 26, 2023 at 3:12 AM Richard Zowalla > > <mailto:r...@apache.org>>
>> > wrote:
>> > 
>> > > Hi all,
>> > > 
>> > > I also experienced, that dev@ activity is quite low. I did provide
>> > > some
>> > > PRs and asked questions a few months ago and didn't get any
>> > > feedback,
>> > > although the PRs got merged in the end. I think, that we need some
>> > > sort
>> > > of community rebuilding / revival, if we want to maintain Storm in
>> > > a
>> > > sustainable way (like it is done for TomEE or OpenNLP).
>> > > 
>> > > Nevertheless, as I am also a committer on StormCrawler, which
>> > > relies on
>> > > Storm (obviously) _and_ is used in our research work, I am also
&

Re: [DISCUSSION] Apache Storm and moving to the Attic

[P. Taylor Goetz]

IMO, there are tow scenarios:

1. Storm is in dead. No one uses it anymore, and no one needs security patches, 
etc.
2. Storm is in maintenance mode. While new features may not be added, there are 
enough contributors left tp at least address any security concerns.

Wether we pursue the attic o projectr continuation is really up to the 
community. Anyone who want to step up and help continue the project should be 
considered a PMC candidate.

As I’ve said in other threads, I’m willing to act as PMC chair whatever the PMC 
decides.

But for now we have ne official liaison to ther ASF board. PMC members need to 
elect a chair, whether we choose to continue or head to the attic.

I would lean toward lowering the bar for PMC membership to anyone interested in 
ongoing maintenance. 

I’m still willing to serve as the board liaison (PMC Chair) in either case of 
retirement or continuation. I’d also support anyone else willing to take the 
position.  The position needs to be filled either way.

This is a decision that affects both developers and users. Thank you Aaron for 
bringing it to the attention of the  broader community.

-Taylor

> On Feb 1, 2023, at 9:26 PM, sunil yadav  wrote:
> 
> One side note looking to see what folks are migrating or moved to if not 
> using Storm actively. Any cloud native DAG platform to recommend?
> 
> -Sunil
> 
> On Wed, Feb 1, 2023 at 6:12 PM Stephen Powis via user  > wrote:
> Ah Yea, also not opposed to the move to the attic if it's determined to be 
> most appropriate, but I had a similar experience as Richard where I submitted 
> some PRs, asked for comments/thoughts/review, and even offered to take over 
> ownership of one of the sub modules and got no responses.  Perhaps I just 
> submitted under the wrong forum to get an answer, but definitely a bummer, 
> and would love to see the project/community get revived.
> 
> - Stephen
> 
> On Wed, Feb 1, 2023 at 10:09 PM Richard Zowalla  > wrote:
> Hi Aaron,
> 
> I am CC the users@ list as they weren't contained in the initial
> proposal. Perhaps, there are people or institutions in the wild, who
> want to volunteer or give it a try (still at the ASF level). 
> 
> Of course it shouldn't prevent a VOTE for moving to the attic, but an
> additional try to get some more attention (if needed).
> 
> Gruß
> Richard
> 
> 
> Am Dienstag, dem 31.01.2023 um 08:00 -0600 schrieb Aaron Niskode-
> Dossett:
> > Thank you to those who responded. Given that the low number of
> > responses I
> > am going to start a vote on moving to the attic tomorrow.
> > 
> > One other note: A vote to move to the attic would not mean the end of
> > Storm, the project can be forked by anyone who wants to continue the
> > work
> > (just as it can be forked today), it would just be outside of the
> > ASF.
> > 
> > On Thu, Jan 26, 2023 at 3:12 AM Richard Zowalla  > >
> > wrote:
> > 
> > > Hi all,
> > > 
> > > I also experienced, that dev@ activity is quite low. I did provide
> > > some
> > > PRs and asked questions a few months ago and didn't get any
> > > feedback,
> > > although the PRs got merged in the end. I think, that we need some
> > > sort
> > > of community rebuilding / revival, if we want to maintain Storm in
> > > a
> > > sustainable way (like it is done for TomEE or OpenNLP).
> > > 
> > > Nevertheless, as I am also a committer on StormCrawler, which
> > > relies on
> > > Storm (obviously) _and_ is used in our research work, I am also
> > > happy
> > > to jump in as a volunteer, if some ppl are needed.
> > > 
> > > Gruß
> > > Richard
> > > 
> > > 
> > > Am Mittwoch, dem 25.01.2023 um 22:00 + schrieb Bipin Prasad:
> > > > I am volunteering to take on the role of PMC chairFor Storm. Not
> > > > quite sure about the process.
> > > > Thanks—Bipin Prasad
> > > > 
> > > > 
> > > > Sent from Yahoo Mail for iPhone
> > > > 
> > > > 
> > > > On Wednesday, January 25, 2023, 4:50 PM, Aaron Niskode-Dossett <
> > > > doss...@gmail.com > wrote:
> > > > 
> > > > Hello Storm developer community,
> > > > 
> > > > In the past year or so this project has slowed down and the
> > > > Project
> > > > Management Committee [PMC] has almost no active members.  The PMC
> > > > chair
> > > > resigned in 2022 with due notice and noone has since volunteered
> > > > to
> > > > assume
> > > > those duties.  I myself am an inactive PMC member.
> > > > 
> > > > This suggests to me that it's time to consider moving this
> > > > project to
> > > > the
> > > > Attic [1].  I would view this as the natural culmination of a
> > > > very
> > > > successful Apache project and not as a mark of failure.  There
> > > > are
> > > > many,
> > > > many successful and influential projects in the attic.
> > > > 
> > > > The alternative to moving to the attic would be to reconstitute
> > > > the
> > > > PMC
> > > > with *new members* of the development community willing to take
> > > > on
> > > > 

Re: [VOTE] Release Apache Storm 2.1.0 (rc2)

[P. Taylor Goetz]

Nice work Ethan!

I’ll try to take a look in the next few days.

-Taylor

> On Aug 14, 2019, at 2:13 PM, Ethan Li  wrote:
> 
> This is a call to vote on releasing Apache Storm 2.1.0 (rc2)
> 
> Full list of changes in this release:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.1.0-rc2/RELEASE_NOTES.html
> 
> The tag/commit to be voted upon is v2.1.0:
> 
> https://gitbox.apache.org/repos/asf?p=storm.git;a=tree;h=6c7adb8c7095cb718d5c49d07331034ae0e8434a;hb=f875619fc1017e401d65bd2900b195738f90e754
> 
> The source archive being voted upon can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.1.0-rc2/apache-storm-2.1.0-src.tar.gz
> 
> Other release files, signatures and digests can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.1.0-rc2
> 
> The release artifacts are signed with the following key:
> 
> https://www.apache.org/dist/storm/KEYS
> 
> The Nexus staging repository for this release is:
> 
> https://repository.apache.org/content/repositories/orgapachestorm-1085/
> 
> Please vote on releasing this package as Apache Storm 2.1.0.
> 
> When voting, please list the actions taken to verify the release.
> 
> This vote will be open for at least 72 hours.
> 
> [ ] +1 Release this package as Apache Storm 2.1.0
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
> 
> Thanks to everyone who contributed to this release.
> 
> Ethan

Re: [DISCUSS] Next 2.x release

[P. Taylor Goetz]

Those can be safely deleted.

-Taylor

> On Aug 13, 2019, at 12:15 PM, Ethan Li  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://github.com/apache/storm/blob/master/RELEASING.md#cleaning-up-if-the-vote-fails
>  
> <https://github.com/apache/storm/blob/master/RELEASING.md#cleaning-up-if-the-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/>
> 
> Just want to be absolutely sure about this. Thanks.
> 
>> On Aug 13, 2019, at 10:56 AM, Ethan Li  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øssing  
>>> wrote:
>>> 
>>> Makes sense. I'll take a look at it. Ideally I'd want the 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 :
>>> 
>>>> 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 “mvn
>>>> release:prepare” since “ mvn release:prepare” will automatically push two
>>>> commits. For example,
>>>> 
>>>> (1) [maven-release-plugin] prepare release v2.1.0:  this 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 development iteration:  this
>>>> commit changes the pom version to 2.1.1-SNAPSHOT.
>>>> 
>>>> 
>>>> We need DEPENDENCY-LICENSES to be updated on every step.
>>>> 
>>>> 
>>>> 
>>>>> On Aug 13, 2019, at 10:24 AM, Stig Rohde Døssing 
>>>> wrote:
>>>>> 
>>>>> Oops, sorry that's not right. The license plugin setup was disabled in
>>>>> 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,
>>>>> 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øssing <
>>>>> stigdoess...@gmail.com>:
>>>>> 
>>>>>> There's a script that can help you do it in
>>>>>> 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 "mvn
>>>>>> license:aggregate-add-third-party@generate-and-check-licenses
>>>>>> -Dlicense.skipAggregateAddThirdParty=false -B" in the project root. It
>>>>>> should update the file for you.
>>>>>> 
>>>>>> Den tir. 13. aug. 2019 kl. 17.06 skrev Ethan Li <
>>>> ethanopensou...@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?> Is
>>>>>>> there a command I can use? Or I just replace strings manually?
>>>>>>> 
>>>>>>> Thanks
>>>>>>> Ethan
>>>>>>> 
>>>>>>>> On Aug 12, 2019, at 3:54 PM, Ethan Li 
>>>>>>> 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 
>>>>>>> wrote:
>>>>>>>>> 
>>>>>>>>>

Re: [DISCUSS] Next 2.x release

[P. Taylor Goetz]

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  wrote:
> 
> I have one more question before I can start a vote. 
> 
> In previous [VOTE] thread, Taylor always has this:
> 
> The release artifacts are signed with the following key:
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
>  
> <https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd>
> 
> 
> 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  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  wrote:
>>> 
>>> For the 2.x version lines, there are a bunch of 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øssing  
>>>> 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 in the reactor.
>>>> 
>>>> Den man. 12. aug. 2019 kl. 15.15 skrev Ethan Li 
>>>> :
>>>> 
>>>>> 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 “mvn:prepare”
>>>>> and “mvn:perform”. It created 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’s
>>>>> 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 “mvn:prepare” step.  How do I get
>>>>> storm-dist pom version updated with “mv:prepare”?
>>>>> 
>>>>> I am currently blocked on this. Any help will be appreciated.
>>>>> 
>>>>> Thanks,
>>>>> Ethan
>>>>> 
>>>>> 
>>>>>> On Aug 12, 2019, at 2:38 AM, Stig Rohde Døssing 
>>>>> 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 should 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øn. 11. aug. 2019 kl. 08.37 skrev Ethan Li <
>>>>> ethanopensou...@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 just sent an email to Taylor.
>>>>>>> 
>>>>>>> Please don’t merge anything to master or 2.1.x-branch for now. Thanks
>>>>>>> 
>>>>>>> Best,
>>>>>>> Ethan
>>>>>>> 
>>>>>>> 
>>>>>>>> On Aug 9, 2019, at 4:45 PM, Ethan Li 
>>>>> wrote:
>>>>>>>> 
>>>>>>>> Currently we have two outstanding PRs that we wanted to include in the
>>>>>>> new release:
>>>>>>>> 
>>>>>>>> https://github.com/apache/storm/pull/3096 <
>>>>>>> https://github.com/apache/storm/p

Re: [DISCUSS] Next 2.x release

[P. Taylor Goetz]

For the 2.x version lines, there are a bunch of 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øssing  
> 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 in the reactor.
> 
> Den man. 12. aug. 2019 kl. 15.15 skrev Ethan Li :
> 
>> 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 “mvn:prepare”
>> and “mvn:perform”. It created 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’s
>> 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 “mvn:prepare” step.  How do I get
>> storm-dist pom version updated with “mv:prepare”?
>> 
>> I am currently blocked on this. Any help will be appreciated.
>> 
>> Thanks,
>> Ethan
>> 
>> 
>>> On Aug 12, 2019, at 2:38 AM, Stig Rohde Døssing 
>> 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 should 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øn. 11. aug. 2019 kl. 08.37 skrev Ethan Li <
>> ethanopensou...@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 just sent an email to Taylor.
 
 Please don’t merge anything to master or 2.1.x-branch for now. Thanks
 
 Best,
 Ethan
 
 
> On Aug 9, 2019, at 4:45 PM, Ethan Li 
>> wrote:
> 
> Currently we have two outstanding PRs that 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 
 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’t responded yet.)
> 
> It’s not absolutely necessary to include them in this new release so I
 think I should move forward with the release process. These two and
>> other
 PRs can be included in the next release.
> 
> For the release, I will create a new branch 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 >>> da...@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’s a good idea to be more clear on the versioning and
 release process so users and developers know 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 Dagit >>> da...@apache.org>> wrote:
 
 On Fri, Aug 09, 2019 at 02:35:57PM +0200, Stig Rohde Døssing 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 "Release Manager":
 
> 1. We promise to make 1 major release / year, but the 

Re: [VOTE] Release Apache Storm 1.2.3 (rc2)

[P. Taylor Goetz]

This vote is now closed and passes with 3 binding +1 votes and 1 non-binding +1 
vote.

I will release the artifacts and create a release announcement.

-Taylor

> On May 10, 2019, at 12:20 PM, P. Taylor Goetz  wrote:
> 
> This is a call to vote on releasing Apache Storm 1.2.3 (rc2)
> 
> Full list of changes in this release:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.3-rc2/RELEASE_NOTES.html
> 
> The tag/commit to be voted upon is v1.2.3:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=ac0e39d7cad48b3ec863c8a3b711d36511d4daf6;hb=4e162a47c8219546ab9639401363a8f1b5e51119
> 
> The source archive being voted upon can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.3-rc2/apache-storm-1.2.3-src.tar.gz
> 
> Other release files, signatures and digests can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.3-rc2/
> 
> The release artifacts are signed with the following key:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
> 
> The Nexus staging repository for this release is:
> 
> https://repository.apache.org/content/repositories/orgapachestorm-1081
> 
> Please vote on releasing this package as Apache Storm 1.2.3.
> 
> When voting, please list the actions taken to verify the release.
> 
> This vote will be open for at least 72 hours.
> 
> [ ] +1 Release this package as Apache Storm 1.2.3
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
> 
> Thanks to everyone who contributed to this release.
> 
> -Taylor

Re: Storm Windowing

[P. Taylor Goetz]

Hi Vibhatha,

What version of Storm are you using?

-Taylor

> On Jun 4, 2019, at 3:25 PM, Vibhatha Abeykoon  wrote:
> 
> Vibhatha

Re: Storm 2.0 Maven Artifacts

[P. Taylor Goetz]

My bad. I missed a button click in repository.a.o. Just released now, should be 
available in at most 24 hrs.

-TAylor

> On Jun 3, 2019, at 8:59 PM, Roshan Naik  wrote:
> 
> Does this mean that the artifacts were not been pushed to the mvn repo ? Or 
> do we just need to wait for the artifacts to show up there .. and if so how 
> long ? 
> -roshan
> 
> 
> 
> 
> 
> On Monday, June 3, 2019, 9:33:44 AM PDT, Stig Rohde Døssing 
>  wrote: 
> 
> 
> 
> No, I think you are right. It doesn't look like the 2.0.0 artifacts are
> present in Maven yet.
> 
> CC'ing to the dev list.
> 
> Den man. 3. jun. 2019 kl. 17.30 skrev Re'em Bensimhon :
> 
>> Hey everybody
>> 
>> I'm trying to test out the new Storm release (very exciting :-) but I'm
>> not managing to find the v2.0 artifacts for storm-client or storm-core in
>> any public maven repository.
>> 
>> https://repo.maven.apache.org/maven2/org/apache/storm/storm/
>> https://mvnrepository.com/artifact/org.apache.storm/storm
>> 
>> Am I missing something?
>> 
>> Re'em
>> 

Re: [Discuss] New release managers

[P. Taylor Goetz]

+1 It’s clear I’ve become a bottleneck in this regard and would love to see 
others pick up release management duties.

I have markdown document somewhere (likely on an old laptop backup somewhere) 
I’ll dig it up, update it and share it.

I imagine most committers know what the lead up to a release is like — 
essentially just gather consensus that it’s time to release and figure out what 
to include..

A high level view of the Storm-specific process of actually creating a release 
is:

1. Run `mvn release:prepare` followed `mvn release:perform` on the branch to be 
released. You will need to have an account on repository.apache.org 
 to do this. I believe all committers have 
access, but I would have to verify that. This will create all the artifacts 
that will eventually be available in maven central. This step may seem simple, 
but a lot can go wrong (mainly flaky tests).

2. Once you get a successful maven release, a “staging repository” will be 
created in the “open” state, meaning it is still writable. You will need to 
close it, making it read-only and the artifiacts now “staged”.

3. Run `mvn package` for `storm-dist/binary` and `storm-dist/source` to create 
the actual distributions.

4. Sign and generate checksums for the *.tar.gz and *.zip distribution files.

5. Create a directory in the dist svn repo for the release candidate: 
https://dist.apache.org/repos/dist/dev/storm/apache-storm-x.x.x-rcx 


6. Run `release_notes.py` for the release version, piping the output to 
RELEASE_NOTES.html. Move that file to the svn release directory, sign it, and 
generate checksums.

6. Move release files from Step 4 and 6 to the svn directory from Step 5. Add 
and commit the files. This makes them available in the apache staging repo.

— at this point the release candidate is created and staged —

7. Start the VOTE thread.

— Assuming successful VOTE —

8. `svn mv https://dist.apache.org/repos/dist/dev/storm/apache-storm-x.x.x-rcx 
 
https://dist.apache.org/repos/release/dev/storm/apache-storm-x.x.x` 
. This 
will make the release artifacts available on dist.apache.org 
 and the artifacts will start replicating to mirrors.

9. Wait at least 24 hrs. for the mirrors to catch up.

10. Compose blog post announcement. Generate documentation, generate site, and 
`git push` to publish the site.

11. Announce to dev@storm.a.o , user@storm.a.o 
, and announce@a.o . You will need 
to use your @apache.org email to do this.

12. Tweet, promote, celebrate. ;)

I know I’ve glossed over a lot of details.

I would suggest someone volunteer to be a RM “guinea pig” and try to do a mock 
release. We can debug and document the details. Obviously RCs can be cancelled 
and rolled back, so it would be a harmless exercise.

-Taylor

> On May 30, 2019, at 5:18 PM, Stig Rohde Døssing  
> wrote:
> 
> Hi everyone,
> 
> I think we should have more people willing to act as release managers.
> Taylor has expressed a desire to step back from the role (or at least to
> not be the only RM), and it would be good if we could have a few people
> ready to step up and wear the RM hat. If you're interested in this role,
> this thread would be a good place to say so.
> 
> There's some general information about releasing under Apache at
> http://www.apache.org/dev/release-publishing.html.
> 
> As I understand it, a new RM will need to at least generate and publish
> their signature before they can act as RM. More info at
> http://www.apache.org/dev/release-signing.html. I'm not sure whether
> linking with the Apache web of trust is also mandatory.
> 
> Taylor, it would be helpful if you could explain any additional steps
> beyond what is in the Apache guide to what a release manager needs to do to
> release Storm.

[ANNOUNCE] Apache Storm 2.0.0 Released

[P. Taylor Goetz]

The Apache Storm community is pleased to announce the release of Apache Storm 
version 2.0.0.

Storm is a distributed, fault-tolerant, and high-performance realtime 
computation system that provides strong guarantees on the processing of data. 
You can read more about Storm on the project website:

http://storm.apache.org

Downloads of source and binary distributions are listed in our download
section:

http://storm.apache.org/downloads.html

You can read more about this release in the following blog post:

http://storm.apache.org/2019/05/30/storm200-released.html

Distribution artifacts are available in Maven Central at the following 
coordinates:

groupId: org.apache.storm
artifactId: storm-core
version: 2.0.0

The full list of changes is available here[1]. Please let us know [2] if you 
encounter any problems.

Regards,

The Apache Storm Team

[1]: http://www.us.apache.org/dist/storm/apache-storm-2.0.0/RELEASE_NOTES.html
[2]: https://issues.apache.org/jira/browse/STORM

Re: Storm 2.0 blogs ?

[P. Taylor Goetz]

I’m going to distill everything mentioned so far into a release announcement 
that I hope to get out later today, or more likely, Monday.

Then we can add follow up blog posts that go into greater detail.

For reference, I’m reposting the list of topics Roshan came up with:

1- Re-architecture - [Roshan]
2- Windowing enhancements
3- SQL enhancements
4- Metrics
5- Kafka related changes 
6- Security (nimbus admin groups, delegation tokens, optional impersonation)
7- PMML (Machine Learning) support.
8- Streams API
9- Module restructuring & dependency mitigation 
10- Java porting
11- DRPC cmd line
12- Lambda support
13- New spouts: Kinesis & Druid ?
14- Changes to deployment and cli submission 
15- RAS changes
16- Trident enhancements
17- New Admin cmds to debug cluster state
18 ... others ?

-Taylor




> On Jan 29, 2019, at 6:16 PM, Arun M  wrote:
> 
> Heres a short blurb for Streams API & windowing enhancements.
> 
> 1. Streams API
> 
> A typed API for expressing streaming computations more easily using
> functional style operations.
> It builds on top of the Storm's core spouts and bolt APIs and automatically
> fuses multiple operations together to optimize the pipeline.
> For more details and examples see -
> https://github.com/apache/storm/blob/master/docs/Stream-API.md
> 
> 2. Windowing enhancements
> 
> Storm can save/restore the window state to the configured state backend so
> that larger continuous windows can be supported.
> The window boundaries can now be accessed via the APIs.
> For more details see -
> https://github.com/apache/storm/blob/master/docs/Windowing.md#stateful-windowing
> 
> Thanks,
> Arun

[VOTE] Release Apache Storm 1.2.3 (rc2)

[P. Taylor Goetz]

This is a call to vote on releasing Apache Storm 1.2.3 (rc2)

Full list of changes in this release:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.3-rc2/RELEASE_NOTES.html

The tag/commit to be voted upon is v1.2.3:

https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=ac0e39d7cad48b3ec863c8a3b711d36511d4daf6;hb=4e162a47c8219546ab9639401363a8f1b5e51119

The source archive being voted upon can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.3-rc2/apache-storm-1.2.3-src.tar.gz

Other release files, signatures and digests can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.3-rc2/

The release artifacts are signed with the following key:

https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd

The Nexus staging repository for this release is:

https://repository.apache.org/content/repositories/orgapachestorm-1081

Please vote on releasing this package as Apache Storm 1.2.3.

When voting, please list the actions taken to verify the release.

This vote will be open for at least 72 hours.

[ ] +1 Release this package as Apache Storm 1.2.3
[ ]  0 No opinion
[ ] -1 Do not release this package because...

Thanks to everyone who contributed to this release.

-Taylor

[CANCELED] [VOTE] Release Apache Storm 1.2.3 (rc1)

[P. Taylor Goetz]

Good catch. Off-by-one error on my part.

The release candidate is still valid. I just need to do an `svn mv`.

Canceling vote to do an svn rename.

-Taylor

> On May 9, 2019, at 3:48 AM, Alexandre Vermeerbergen 
>  wrote:
> 
> Hello,
> 
> I am confused : there was a mail calling for voting for 1.2.3-RC1 on
> 8th of January this year.
> Is this new call for vote related to exactly the same "code freeze",
> or is that a newer code freeze, in which case shouldn't be called
> "1.2.3-rc2" ?
> 
> Kind regards,
> Alexandre Vermeerbergen
> 
> Le mer. 8 mai 2019 à 21:30, P. Taylor Goetz  a écrit :
>> 
>> This is a call to vote on releasing Apache Storm 1.2.3 (rc1)
>> 
>> Full list of changes in this release:
>> 
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.3-rc1/RELEASE_NOTES.html
>> 
>> The tag/commit to be voted upon is v1.2.3:
>> 
>> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=ac0e39d7cad48b3ec863c8a3b711d36511d4daf6;hb=4e162a47c8219546ab9639401363a8f1b5e51119
>> 
>> The source archive being voted upon can be found here:
>> 
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.3-rc1/apache-storm-1.2.3-src.tar.gz
>> 
>> Other release files, signatures and digests can be found here:
>> 
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.3-rc1/
>> 
>> The release artifacts are signed with the following key:
>> 
>> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
>> 
>> The Nexus staging repository for this release is:
>> 
>> https://repository.apache.org/content/repositories/orgapachestorm-1081
>> 
>> Please vote on releasing this package as Apache Storm 1.2.3.
>> 
>> When voting, please list the actions taken to verify the release.
>> 
>> This vote will be open for at least 72 hours.
>> 
>> [ ] +1 Release this package as Apache Storm 1.2.3
>> [ ]  0 No opinion
>> [ ] -1 Do not release this package because...
>> 
>> Thanks to everyone who contributed to this release.
>> 
>> -Taylor

[VOTE] Release Apache Storm 1.2.3 (rc1)

[P. Taylor Goetz]

This is a call to vote on releasing Apache Storm 1.2.3 (rc1)

Full list of changes in this release:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.3-rc1/RELEASE_NOTES.html

The tag/commit to be voted upon is v1.2.3:

https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=ac0e39d7cad48b3ec863c8a3b711d36511d4daf6;hb=4e162a47c8219546ab9639401363a8f1b5e51119

The source archive being voted upon can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.3-rc1/apache-storm-1.2.3-src.tar.gz

Other release files, signatures and digests can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.3-rc1/

The release artifacts are signed with the following key:

https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd

The Nexus staging repository for this release is:

https://repository.apache.org/content/repositories/orgapachestorm-1081

Please vote on releasing this package as Apache Storm 1.2.3.

When voting, please list the actions taken to verify the release.

This vote will be open for at least 72 hours.

[ ] +1 Release this package as Apache Storm 1.2.3
[ ]  0 No opinion
[ ] -1 Do not release this package because...

Thanks to everyone who contributed to this release.

-Taylor

[RESULT] [VOTE] Release Apache Storm 2.0.0 RC7

[P. Taylor Goetz]

Wow. This is a special occasion…

The 2.0 release has been a very long time in the making, I can’t begin to thank 
all those who helped shepherd this branch to release quality.

To me this is an Apache project at it’s finest. We’ve seen core contributors 
come and go. And when they go, we’ve seen new contributors step up and fill the 
gap created. A big thank you to all contributors, past, present and future! 
This is a true community achievement.

This vote is now closed and passes with 6 binding +1 votes,  and no 0 or -1 
votes.

Vote tally (* indicates a binding vote):

+1: 
Derek Dagit*
Stig Rohde Døssing*
Kishorkumar Patil*
Jungtaek Lim*
Arun Mahadevan*
Ethan Li*

0:

-1:

I will release the staged artifacts and prepare a release announcement.

Congratulations again to all who contributed to this release.

-Taylor

> On Apr 29, 2019, at 6:49 PM, P. Taylor Goetz  wrote:
> 
> This is a call to vote on releasing Apache Storm 2.0.0 (rc7)
> 
> Full list of changes in this release:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc7/RELEASE_NOTES.html
> 
> The tag/commit to be voted upon is v2.0.0:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=007863edd95e838b3df414928c6fa3f28244ab49;hb=2ba95bbd1c911d4fc6363b1c4b9c4c6d86ac9aae
> 
> The source archive being voted upon can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc7/apache-storm-2.0.0-src.tar.gz
> 
> Other release files, signatures and digests can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc7/
> 
> The release artifacts are signed with the following key:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
> 
> The Nexus staging repository for this release is:
> 
> https://repository.apache.org/content/repositories/orgapachestorm-1079
> 
> Please vote on releasing this package as Apache Storm 2.0.0.
> 
> When voting, please list the actions taken to verify the release.
> 
> This vote will be open for at least 72 hours.
> 
> [ ] +1 Release this package as Apache Storm 2.0.0
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
> 
> Thanks to everyone who contributed to this release.
> 
> -Taylor

Re: [VOTE] Release Apache Storm 2.0.0 RC7

[P. Taylor Goetz]

Yeah, I had an expiration date on now of my keys. I’ve sorted it out, but need 
to wait for propagation of myyl keys.

This is currently blocking the 1.2.x. and 1.1.x releases. But it looks like we 
can move forward with the 2.0.0 release.

-Taylor

> On May 2, 2019, at 4:51 PM, Ethan Li  wrote:
> 
> +1
> 
> 
> 1. Checked *.asc, *.md5, *.sha512
> 2. Built from the source code and ran unit tests; created a storm 
> distribution based on it
> 3. set up a standalone cluster (based on apache-storm-2.0.0.zip, 
> apache-storm-2.0.0.tar.gz, the storm distribution created above, separately)
> 4. Launched WordCountTopology and ThroughputVslatency and checked logs, 
> output, UI
> 4. Tested jstack, heap dump, deactivate, activate, rebalance, change log 
> level and kll on UI.
> 
> 
> I noticed "Note: This key has expired!” when I used "gpg —verify" to verify 
> the signature. I am not sure if we care about that.
> 
> 
> Thanks
> 
> - Ethan
> 
>> On Apr 29, 2019, at 5:49 PM, P. Taylor Goetz  wrote:
>> 
>> This is a call to vote on releasing Apache Storm 2.0.0 (rc7)
>> 
>> Full list of changes in this release:
>> 
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc7/RELEASE_NOTES.html
>> 
>> The tag/commit to be voted upon is v2.0.0:
>> 
>> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=007863edd95e838b3df414928c6fa3f28244ab49;hb=2ba95bbd1c911d4fc6363b1c4b9c4c6d86ac9aae
>> 
>> The source archive being voted upon can be found here:
>> 
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc7/apache-storm-2.0.0-src.tar.gz
>> 
>> Other release files, signatures and digests can be found here:
>> 
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc7/
>> 
>> The release artifacts are signed with the following key:
>> 
>> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
>> 
>> The Nexus staging repository for this release is:
>> 
>> https://repository.apache.org/content/repositories/orgapachestorm-1079
>> 
>> Please vote on releasing this package as Apache Storm 2.0.0.
>> 
>> When voting, please list the actions taken to verify the release.
>> 
>> This vote will be open for at least 72 hours.
>> 
>> [ ] +1 Release this package as Apache Storm 2.0.0
>> [ ]  0 No opinion
>> [ ] -1 Do not release this package because...
>> 
>> Thanks to everyone who contributed to this release.
>> 
>> -Taylor
> 

[CANCELED] [VOTE] Release Apache Storm 1.2.4 (rc1)

[P. Taylor Goetz]

I accidentally skipped a version number. Will kick off a new RC tomorrow.

-Taylor

> On Apr 30, 2019, at 10:49 AM, P. Taylor Goetz  wrote:
> 
> This is a call to vote on releasing Apache Storm 1.2.4 (rc1)
> 
> Full list of changes in this release:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.4-rc1/RELEASE_NOTES.html
> 
> The tag/commit to be voted upon is v1.2.4:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=47cd68feb442a80abd40f0942baaed899c14ee66;hb=8143f448849a266a90ae4d4f5cc1c12c5f8e5188
> 
> The source archive being voted upon can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.4-rc1/apache-storm-1.2.4-src.tar.gz
> 
> Other release files, signatures and digests can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.4-rc1/
> 
> The release artifacts are signed with the following key:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
> 
> The Nexus staging repository for this release is:
> 
> https://repository.apache.org/content/repositories/orgapachestorm-1080
> 
> Please vote on releasing this package as Apache Storm 1.2.4.
> 
> When voting, please list the actions taken to verify the release.
> 
> This vote will be open for at least 72 hours.
> 
> [ ] +1 Release this package as Apache Storm 1.2.4
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
> 
> Thanks to everyone who contributed to this release.
> 
> -Taylor

[VOTE] Release Apache Storm 1.2.4 (rc1)

[P. Taylor Goetz]

This is a call to vote on releasing Apache Storm 1.2.4 (rc1)

Full list of changes in this release:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.4-rc1/RELEASE_NOTES.html

The tag/commit to be voted upon is v1.2.4:

https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=47cd68feb442a80abd40f0942baaed899c14ee66;hb=8143f448849a266a90ae4d4f5cc1c12c5f8e5188

The source archive being voted upon can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.4-rc1/apache-storm-1.2.4-src.tar.gz

Other release files, signatures and digests can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.4-rc1/

The release artifacts are signed with the following key:

https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd

The Nexus staging repository for this release is:

https://repository.apache.org/content/repositories/orgapachestorm-1080

Please vote on releasing this package as Apache Storm 1.2.4.

When voting, please list the actions taken to verify the release.

This vote will be open for at least 72 hours.

[ ] +1 Release this package as Apache Storm 1.2.4
[ ]  0 No opinion
[ ] -1 Do not release this package because...

Thanks to everyone who contributed to this release.

-Taylor

[VOTE] Release Apache Storm 2.0.0 RC7

[P. Taylor Goetz]

This is a call to vote on releasing Apache Storm 2.0.0 (rc7)

Full list of changes in this release:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc7/RELEASE_NOTES.html

The tag/commit to be voted upon is v2.0.0:

https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=007863edd95e838b3df414928c6fa3f28244ab49;hb=2ba95bbd1c911d4fc6363b1c4b9c4c6d86ac9aae

The source archive being voted upon can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc7/apache-storm-2.0.0-src.tar.gz

Other release files, signatures and digests can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc7/

The release artifacts are signed with the following key:

https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd

The Nexus staging repository for this release is:

https://repository.apache.org/content/repositories/orgapachestorm-1079

Please vote on releasing this package as Apache Storm 2.0.0.

When voting, please list the actions taken to verify the release.

This vote will be open for at least 72 hours.

[ ] +1 Release this package as Apache Storm 2.0.0
[ ]  0 No opinion
[ ] -1 Do not release this package because...

Thanks to everyone who contributed to this release.

-Taylor

[CANCELED] [VOTE] Release Apache Storm 2.0.0 (rc6)

[P. Taylor Goetz]

Canceling due to another license issue. Will issue a new RC shortly.

-Taylor

> On Apr 16, 2019, at 2:42 PM, P. Taylor Goetz  wrote:
> 
> This is a call to vote on releasing Apache Storm 2.0.0 (rc6)
> 
> Full list of changes in this release:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc6/RELEASE_NOTES.html
> 
> The tag/commit to be voted upon is v2.0.0:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=fb277b90c8488aec017eed066a9fd221a247e4f9;hb=ac046ee6170d982f98b66f3ed21a82f979707d68
> 
> The source archive being voted upon can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc6/apache-storm-2.0.0-src.tar.gz
> 
> Other release files, signatures and digests can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc6/
> 
> The release artifacts are signed with the following key:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
> 
> The Nexus staging repository for this release is:
> 
> https://repository.apache.org/content/repositories/orgapachestorm-1077
> 
> Please vote on releasing this package as Apache Storm 2.0.0.
> 
> When voting, please list the actions taken to verify the release.
> 
> This vote will be open for at least 72 hours.
> 
> [ ] +1 Release this package as Apache Storm 2.0.0
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
> 
> Thanks to everyone who contributed to this release.
> 
> -Taylor

[VOTE] Release Apache Storm 2.0.0 (rc6)

[P. Taylor Goetz]

This is a call to vote on releasing Apache Storm 2.0.0 (rc6)

Full list of changes in this release:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc6/RELEASE_NOTES.html

The tag/commit to be voted upon is v2.0.0:

https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=fb277b90c8488aec017eed066a9fd221a247e4f9;hb=ac046ee6170d982f98b66f3ed21a82f979707d68

The source archive being voted upon can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc6/apache-storm-2.0.0-src.tar.gz

Other release files, signatures and digests can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc6/

The release artifacts are signed with the following key:

https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd

The Nexus staging repository for this release is:

https://repository.apache.org/content/repositories/orgapachestorm-1077

Please vote on releasing this package as Apache Storm 2.0.0.

When voting, please list the actions taken to verify the release.

This vote will be open for at least 72 hours.

[ ] +1 Release this package as Apache Storm 2.0.0
[ ]  0 No opinion
[ ] -1 Do not release this package because...

Thanks to everyone who contributed to this release.

-Taylor

[CANCELED] [VOTE] Release Apache Storm 2.0.0 RC5

[P. Taylor Goetz]

Canceling due to some license issues in this RC.

-Taylor

> On Mar 22, 2019, at 4:23 PM, P. Taylor Goetz  wrote:
> 
> This is a call to vote on releasing Apache Storm 2.0.0 (rc5)
> 
> Full list of changes in this release:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc5/RELEASE_NOTES.html
>  
> <https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc5/RELEASE_NOTES.html>
> 
> The tag/commit to be voted upon is v2.0.0:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=7e0a711e4ed5315f04f9f726caff61e0f169e320;hb=b5823809bd4b438e789a36f163f318d4b161ad13
>  
> <https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=7e0a711e4ed5315f04f9f726caff61e0f169e320;hb=b5823809bd4b438e789a36f163f318d4b161ad13>
> 
> The source archive being voted upon can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc5/apache-storm-2.0.0-src.tar.gz
>  
> <https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc5/apache-storm-2.0.0-src.tar.gz>
> 
> Other release files, signatures and digests can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc5/ 
> <https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc5/>
> 
> The release artifacts are signed with the following key:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
>  
> <https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd>
> 
> The Nexus staging repository for this release is:
> 
> https://repository.apache.org/content/repositories/orgapachestorm-1076 
> <https://repository.apache.org/content/repositories/orgapachestorm-1076>
> 
> Please vote on releasing this package as Apache Storm 2.0.0.
> 
> When voting, please list the actions taken to verify the release.
> 
> This vote will be open for at least 72 hours.
> 
> [ ] +1 Release this package as Apache Storm 2.0.0
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
> 
> Thanks to everyone who contributed to this release.
> 
> -Taylor

Re: [VOTE] Release Apache Storm 2.0.0 RC5

[P. Taylor Goetz]

Cool. I’ll put one together tomorrow.

-Taylor

> On Apr 9, 2019, at 1:00 PM, Stig Rohde Døssing  wrote:
> 
> Merged the PR. I think we follow the ASF guidelines more closely now.
> 
> I probably won't backport it to 1.x, and I'm not sure it's necessary. After
> looking at a few other Apache projects, it looks like it's pretty variable
> how detailed the included license information is. If someone feels that it
> should be backported, they should be able to do so by following the README
> instructions added in the PR.
> 
> I think we can try another RC.
> 
> Den man. 8. apr. 2019 kl. 22.43 skrev Stig Rohde Døssing <
> stigdoess...@gmail.com>:
> 
>> See the first few responses in this thread, as well as this comment
>> https://github.com/apache/storm/pull/2980#issuecomment-480514979, I tried
>> to point to the relevant ASF guidelines there. We are missing a bit of text
>> in NOTICE, we aren't including enough in LICENSE for the binary releases,
>> and we aren't listing dependencies with category B licenses anywhere users
>> are likely to see it.
>> 
>> Den man. 8. apr. 2019 kl. 20.59 skrev Roshan Naik
>> :
>> 
>>> ?
>>>On Wednesday, March 27, 2019, 4:39:33 PM PDT, Roshan Naik
>>>  wrote:
>>> 
>>>  Will there be another RC or this one is good to continue with ?
>>> 
>>> 
>>> 
>>> Sent from Yahoo Mail for iPhone
>>> 
>>> 
>>> On Wednesday, March 27, 2019, 9:41 AM, Derek Dagit 
>>> wrote:
>>> 
>>> * Downloaded source ZIP, `mvn clean install`, all passed
>>> * Verified signatures and checksums
>>> * Packaged my build and ran a single-tenant (default) cluster
>>> * Ran org.apache.storm.starter.WordCountTopology
>>> * UI seemed OK, Visualization seemed OK, Logviewer seemed OK
>>> 
>>> +1
>>> 
>>> On Fri, Mar 22, 2019 at 3:23 PM P. Taylor Goetz 
>>> wrote:
>>> 
>>>> This is a call to vote on releasing Apache Storm 2.0.0 (rc5)
>>>> 
>>>> Full list of changes in this release:
>>>> 
>>>> 
>>>> 
>>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc5/RELEASE_NOTES.html
>>>> 
>>>> The tag/commit to be voted upon is v2.0.0:
>>>> 
>>>> 
>>>> 
>>> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=7e0a711e4ed5315f04f9f726caff61e0f169e320;hb=b5823809bd4b438e789a36f163f318d4b161ad13
>>>> 
>>>> The source archive being voted upon can be found here:
>>>> 
>>>> 
>>>> 
>>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc5/apache-storm-2.0.0-src.tar.gz
>>>> 
>>>> Other release files, signatures and digests can be found here:
>>>> 
>>>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc5/
>>>> 
>>>> The release artifacts are signed with the following key:
>>>> 
>>>> 
>>>> 
>>> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
>>>> 
>>>> The Nexus staging repository for this release is:
>>>> 
>>>> https://repository.apache.org/content/repositories/orgapachestorm-1076
>>>> 
>>>> Please vote on releasing this package as Apache Storm 2.0.0.
>>>> 
>>>> When voting, please list the actions taken to verify the release.
>>>> 
>>>> This vote will be open for at least 72 hours.
>>>> 
>>>> [ ] +1 Release this package as Apache Storm 2.0.0
>>>> [ ]  0 No opinion
>>>> [ ] -1 Do not release this package because...
>>>> 
>>>> Thanks to everyone who contributed to this release.
>>>> 
>>>> -Taylor
>>> 
>>> 
>>> 
>> 
>> 

Re: [VOTE] Release Apache Storm 2.0.0 RC5

[P. Taylor Goetz]

L & N files usually differ between source and binary distributions. Usually due 
to shading, contents of lib directory, etc. Source distributions are simpler, 
since they can’t contain any binaries. For a binary distribution, the L & N 
files need to reflect everything in the binary dependencies.

I think it’s important that we review licensing issues, so I’ll cancel this RC.

Kudos to Stig for paying attention to license hygiene!

-Taylor

> On Mar 25, 2019, at 1:21 PM, Stig Rohde Døssing  
> wrote:
> 
> Maybe something like this? https://github.com/apache/storm/pull/2980
> 
> Den man. 25. mar. 2019 kl. 14.12 skrev Stig Rohde Døssing <
> stigdoess...@gmail.com>:
> 
>> The ASF guideline says the file "should identify the third-party product,
>> its licensing, and a url to the its homepage". If we can get away with
>> including the license name and not the license text, I think
>> THIRD-PARTY.txt contains what we need. E.g. Spark also only lists the
>> license names, and not the texts.
>> 
>> We can clean up the output a bit more, e.g. collapse all the Apache
>> licenses together under one header, I just didn't bother because I didn't
>> expect the file to be user facing.
>> 
>> Den man. 25. mar. 2019 kl. 13.47 skrev Jungtaek Lim :
>> 
>>> According to how other projects are doing right now, looks like we are
>>> not doing.
>>> 
>>> https://github.com/apache/flink/blob/master/NOTICE-binary
>>> https://github.com/apache/spark/blob/master/LICENSE-binary
>>> https://github.com/apache/kafka/blob/trunk/LICENSE
>>> 
>>> If I understand correct, aether in storm-submit-tool is also EPL v1.0.
>>> 
>>> Btw, I just ran the command "mvn generate-resources
>>> -Dlicense.skipAggregateAddThirdParty=false" and see the output: the format
>>> of output looks good though the output is a bit verbose. (Attached the
>>> output file.)
>>> 
>>> Would it be OK to include the file without cleaning up?
>>> 
>>> 2019년 3월 25일 (월) 오후 8:19, Stig Rohde Døssing 님이
>>> 작성:
>>> 
>>>> 0
>>>> 
>>>> Built and ran tests from source zip.
>>>> Ran ExclamationTopology on local install set up from binary zip.
>>>> Verified no unexpected error logs.
>>>> Ran integration test locally.
>>>> Clicked around in UI for a bit, checked that logviewer works.
>>>> Ran the license check plugin, and verified that all dependency licenses
>>>> are
>>>> either category A or B.
>>>> 
>>>> We have some category B dependencies, e.g. JAXB and Jersey under CDDL.
>>>> https://apache.org/legal/resolved.html#appropriately-labelled-condition
>>>> mentions that we should list category B dependencies somewhere visible to
>>>> users. Do we do this currently?
>>>> 
>>>> Den fre. 22. mar. 2019 kl. 21.23 skrev P. Taylor Goetz <
>>>> ptgo...@gmail.com>:
>>>> 
>>>>> This is a call to vote on releasing Apache Storm 2.0.0 (rc5)
>>>>> 
>>>>> Full list of changes in this release:
>>>>> 
>>>>> 
>>>>> 
>>>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc5/RELEASE_NOTES.html
>>>>> 
>>>>> The tag/commit to be voted upon is v2.0.0:
>>>>> 
>>>>> 
>>>>> 
>>>> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=7e0a711e4ed5315f04f9f726caff61e0f169e320;hb=b5823809bd4b438e789a36f163f318d4b161ad13
>>>>> 
>>>>> The source archive being voted upon can be found here:
>>>>> 
>>>>> 
>>>>> 
>>>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc5/apache-storm-2.0.0-src.tar.gz
>>>>> 
>>>>> Other release files, signatures and digests can be found here:
>>>>> 
>>>>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc5/
>>>>> 
>>>>> The release artifacts are signed with the following key:
>>>>> 
>>>>> 
>>>>> 
>>>> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
>>>>> 
>>>>> The Nexus staging repository for this release is:
>>>>> 
>>>>> https://repository.apache.org/content/repositories/orgapachestorm-1076
>>>>> 
>>>>> Please vote on releasing this package as Apache Storm 2.0.0.
>>>>> 
>>>>> When voting, please list the actions taken to verify the release.
>>>>> 
>>>>> This vote will be open for at least 72 hours.
>>>>> 
>>>>> [ ] +1 Release this package as Apache Storm 2.0.0
>>>>> [ ]  0 No opinion
>>>>> [ ] -1 Do not release this package because...
>>>>> 
>>>>> Thanks to everyone who contributed to this release.
>>>>> 
>>>>> -Taylor
>>>> 
>>> 

[VOTE] Release Apache Storm 2.0.0 RC5

[P. Taylor Goetz]

This is a call to vote on releasing Apache Storm 2.0.0 (rc5)

Full list of changes in this release:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc5/RELEASE_NOTES.html

The tag/commit to be voted upon is v2.0.0:

https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=7e0a711e4ed5315f04f9f726caff61e0f169e320;hb=b5823809bd4b438e789a36f163f318d4b161ad13

The source archive being voted upon can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc5/apache-storm-2.0.0-src.tar.gz

Other release files, signatures and digests can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc5/

The release artifacts are signed with the following key:

https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd

The Nexus staging repository for this release is:

https://repository.apache.org/content/repositories/orgapachestorm-1076

Please vote on releasing this package as Apache Storm 2.0.0.

When voting, please list the actions taken to verify the release.

This vote will be open for at least 72 hours.

[ ] +1 Release this package as Apache Storm 2.0.0
[ ]  0 No opinion
[ ] -1 Do not release this package because...

Thanks to everyone who contributed to this release.

-Taylor

Re: [VOTE] Release Apache Storm 2.0.0 (rc4)

[P. Taylor Goetz]

This vote is now closed and passes with 8 +1 votes and no -1 or 0 votes.

I will push the release artifacts and publish a release announcement after the 
24 hour waiting period.

-Taylor

> On Jan 8, 2019, at 1:47 PM, P. Taylor Goetz  wrote:
> 
> This is a call to vote on releasing Apache Storm 2.0.0 (rc4)
> 
> Full list of changes in this release:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc4/RELEASE_NOTES.html
> 
> The tag/commit to be voted upon is v2.0.0:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=1eece73e8c9ed7f41d2f20f727bc7f644c499360;hb=ddee8decac57d1a4a0aa23cc76066609a2abc8d2
> 
> The source archive being voted upon can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc4/apache-storm-2.0.0-src.tar.gz
> 
> Other release files, signatures and digests can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc4/
> 
> The release artifacts are signed with the following key:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
> 
> The Nexus staging repository for this release is:
> 
> https://repository.apache.org/content/repositories/orgapachestorm-1073
> 
> Please vote on releasing this package as Apache Storm 2.0.0.
> 
> When voting, please list the actions taken to verify the release.
> 
> This vote will be open for at least 72 hours.
> 
> [ ] +1 Release this package as Apache Storm 2.0.0
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
> 
> Thanks to everyone who contributed to this release.
> 
> -Taylor



signature.asc
Description: Message signed with OpenPGP

[RESULT] [VOTE] Release Apache Storm 1.1.4 (rc1)

[P. Taylor Goetz]

This vote is now closed and passes with 3 binding +1 votes and no -1 or 0 votes.

I will push the release artifacts and post the release announcement after the 
24 hour waiting period.

-Taylor

> On Jan 9, 2019, at 12:01 PM, P. Taylor Goetz  wrote:
> 
> This is a call to vote on releasing Apache Storm 1.1.4 (rc1)
> 
> Full list of changes in this release:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.1.4-rc1/RELEASE_NOTES.html
> 
> The tag/commit to be voted upon is v1.1.4:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=dfb1f971c35ca985a35692aed6d28be3d7e707de;hb=babab9648a6deb3d444c45bdd6d0ec30804e91f1
> 
> The source archive being voted upon can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.1.4-rc1/apache-storm-1.1.4-src.tar.gz
> 
> Other release files, signatures and digests can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.1.4-rc1/
> 
> The release artifacts are signed with the following key:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
> 
> The Nexus staging repository for this release is:
> 
> https://repository.apache.org/content/repositories/orgapachestorm-1075
> 
> Please vote on releasing this package as Apache Storm 1.1.4.
> 
> When voting, please list the actions taken to verify the release.
> 
> This vote will be open for at least 72 hours.
> 
> [ ] +1 Release this package as Apache Storm 1.1.4
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
> 
> Thanks to everyone who contributed to this release.
> 
> -Taylor



signature.asc
Description: Message signed with OpenPGP

[RESULT] [VOTE] Release Apache Storm 1.2.3 (rc1)

[P. Taylor Goetz]

This vote is now closed and passes with 3 binding +1 votes, 2 non-binding +1 
votes and no -1 or 0 votes.

I will push the release and announce after the 24 hour waiting period.

-Taylor

> On Jan 8, 2019, at 3:18 PM, P. Taylor Goetz  wrote:
> 
> This is a call to vote on releasing Apache Storm 1.2.3 (rc1)
> 
> Full list of changes in this release:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.3-rc1/RELEASE_NOTES.html
> 
> The tag/commit to be voted upon is v1.2.3:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=5eaaa51591f2e4dc3e31f22bcc581af4a1f39c03;hb=6ba98b215857656e0186887b5d1a6a5aceee10c4
> 
> The source archive being voted upon can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.3-rc1/apache-storm-1.2.3-src.tar.gz
> 
> Other release files, signatures and digests can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.3-rc1/
> 
> The release artifacts are signed with the following key:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
> 
> The Nexus staging repository for this release is:
> 
> https://repository.apache.org/content/repositories/orgapachestorm-1074
> 
> Please vote on releasing this package as Apache Storm 1.2.3.
> 
> When voting, please list the actions taken to verify the release.
> 
> This vote will be open for at least 72 hours.
> 
> [ ] +1 Release this package as Apache Storm 1.2.3
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
> 
> Thanks to everyone who contributed to this release.
> 
> -Taylor



signature.asc
Description: Message signed with OpenPGP

Re: [VOTE] Release Apache Storm 2.0.0 (rc4)

[P. Taylor Goetz]

Hey Roshan,

A couple factors: A big release, comments/feedback trickling in, and my having 
started a new position that’s got me really busy (though not out of the loop). 
I need to find some time to write up the release announcement, which I hope to 
do over the weekend.

Tomorrow I’ll close all the votes, and publish the 1.1.x and 1.2.x artifacts 
and announcements.

After this round of releases, I’d like to discussion about rotating release 
managers, and as we’ve discussed before, breaking up some components to version 
them independently.

I don’t want to be the bottleneck. ;)

-Taylor

> On Jan 31, 2019, at 9:07 PM, Roshan Naik  
> wrote:
> 
> Hi Taylor,  Looks like this vote and the one for v1.2.3 has been open for 
> quite a while. Any reason to not close it and move forward ?Roshan
> 
> 
> Sent from Yahoo Mail for iPhone
> 
> 
> On Wednesday, January 30, 2019, 9:25 AM, Hugo Louro  
> wrote:
> 
> +1 to continuing with release candidate.
> 
> On Wed, Jan 30, 2019 at 8:22 AM Govind Menon  wrote:
> 
>> +1 for continuing with the RC
>> 
>> On Tue, 29 Jan 2019 at 16:49, Arun Mahadevan  wrote:
>> 
>>> Agree with continuing with the RC if this is not a blocker.
>>> 
>>> On Tue, 29 Jan 2019 at 12:29, Roshan Naik >> 
>>> wrote:
>>> 
>>>>   Correct me if I am wrong, this seems to be a bug with a workaround but
>>>> not an exploitable security hole. ? if this is not a security hole, and
>>> the
>>>> workaround is realistic then we should go ahead with the current RC
>>>> IMO.-roshan
>>>> On Tuesday, January 29, 2019, 10:26:53 AM PST, Kishorkumar Patil <
>>>> kishorvpa...@apache.org> wrote:
>>>> 
>>>>   Aaron,
>>>> Thank you for patch and suggesting the work around in the mean time.
>> The
>>> PR
>>>> for STORM-3317 is merged into master now.
>>>> Considering the work around exists for STORM-3317, I am open to either
>> go
>>>> ahead with current RC or create a new one.
>>>> 
>>>> Thanks,
>>>> Kishor
>>>> 
>>>> On Tue, Jan 29, 2019 at 11:19 AM Aaron Gresch 
>> wrote:
>>>> 
>>>>> The workaround for STORM-3317 is to force your
>>>>> java.security.auth.login.config file on the launcher box to remain in
>>> the
>>>>> same location as where it is hosted on the supervisors.
>>>>> 
>>>>> 
>>>>> On Mon, Jan 28, 2019 at 10:10 AM Aaron Gresch 
>>> wrote:
>>>>> 
>>>>>> 
>>>>>> Not sure if it affects the release, but STORM-3317 is a new bug in
>>> 2.0
>>>>>> where if your launcher box has the java.security.auth.login.config
>>>> file
>>>>> in
>>>>>> a different location than the supervisors, uploading credentials
>> will
>>>> not
>>>>>> work.
>>>>>> 
>>>>>> A PR is available that fixes the issue.
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> On Tue, Jan 8, 2019 at 1:03 PM P. Taylor Goetz 
>>>>> wrote:
>>>>>> 
>>>>>>> This is a call to vote on releasing Apache Storm 2.0.0 (rc4)
>>>>>>> 
>>>>>>> Full list of changes in this release:
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>> 
>>>> 
>>> 
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc4/RELEASE_NOTES.html
>>>>>>> 
>>>>>>> The tag/commit to be voted upon is v2.0.0:
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>> 
>>>> 
>>> 
>> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=1eece73e8c9ed7f41d2f20f727bc7f644c499360;hb=ddee8decac57d1a4a0aa23cc76066609a2abc8d2
>>>>>>> 
>>>>>>> The source archive being voted upon can be found here:
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>> 
>>>> 
>>> 
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc4/apache-storm-2.0.0-src.tar.gz
>>>>>>> 
>>>>>>> Other release files, signatures and digests can be found here:
>>>>>>> 
>>>>>>> 
>>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc4/
>>>>>>> 
>>>>>>> The release artifacts are signed with the following key:
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>> 
>>>> 
>>> 
>> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
>>>>>>> 
>>>>>>> The Nexus staging repository for this release is:
>>>>>>> 
>>>>>>> 
>>>> https://repository.apache.org/content/repositories/orgapachestorm-1073
>>>>>>> 
>>>>>>> Please vote on releasing this package as Apache Storm 2.0.0.
>>>>>>> 
>>>>>>> When voting, please list the actions taken to verify the release.
>>>>>>> 
>>>>>>> This vote will be open for at least 72 hours.
>>>>>>> 
>>>>>>> [ ] +1 Release this package as Apache Storm 2.0.0
>>>>>>> [ ]  0 No opinion
>>>>>>> [ ] -1 Do not release this package because...
>>>>>>> 
>>>>>>> Thanks to everyone who contributed to this release.
>>>>>>> 
>>>>>>> -Taylor
>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>>> 
>> 
> 
> 
> 



signature.asc
Description: Message signed with OpenPGP

Re: Storm 2.0 blogs ?

[P. Taylor Goetz]

If you need to format (e.g. code examples, etc.) then markdown is fine. So is 
plain text.

-Taylor

> On Jan 23, 2019, at 5:24 AM, Stig Rohde Døssing  
> wrote:
> 
> I'll write something for 5 - Kafka related changes.
> 
> We have dropped Druid support, so 13 should be only Kinesis.
> 
> Which format should the blurbs be written in? (Markdown?)
> 
> Den ons. 23. jan. 2019 kl. 08.57 skrev Roshan Naik
> :
> 
>> Like Taylor’s suggestion of collectively contributing small blurbs on
>> features for the Release announcement. Thats the first thing people look on
>> hearing a release announcement. The jira list is not very understandable at
>> first glance.
>> 
>> 
>> Based on suggestions so far and a quick scan of the jiras in release notes
>> here is a draft list in no particular order. I am sure I am missing a few
>> impt ones. This can be pruned or modified as needed:
>> 
>> 1- Re-architecture - [Roshan]
>> 2- Windowing enhancements
>> 3- SQL enhancements
>> 4- Metrics
>> 5- Kafka related changes
>> 6- Security (nimbus admin groups, delegation tokens, optional
>> impersonation)
>> 7- PMML (Machine Learning) support.
>> 8- Streams API
>> 9- Module restructuring & dependency mitigation
>> 10- Java porting
>> 11- DRPC cmd line
>> 12- Lambda support
>> 13- New spouts: Kinesis & Druid ?
>> 14- Changes to deployment and cli submission
>> 15- RAS changes
>> 16- Trident enhancements
>> 17- New Admin cmds to debug cluster state
>> 18 ... others ?
>> 
>> Please pick the topics you can contribute blurbs for. I have put my name
>> against one. It will help Taylor aggregate them and do the necessary final
>> edits.
>> 
>> 
>> -Roshan
>> 
>> 
>> 
>> 
>> 



signature.asc
Description: Message signed with OpenPGP

Re: Storm 2.0 blogs ?

[P. Taylor Goetz]

Awesome. I’ve been thinking about this as well.

The release notes don’t really tell the story of everything in this release, 
and some of the new features and improvements elude my memory.

If others could point out new features that they’d like to be pointed out in 
the release announcement, please list them in this thread. Better yet would be 
a blurb describing the feature/improvement and what benefits it brings users. 
Then I can stitch them together into a release announcement. Basically 
crowd/dev-sourcing the release announcement.

Or, instead of one big announcement, do we want to do a series of blog posts? 
If we go the latter route, the first post should probably cover the most 
significant features. What would those be? Roshan has a pretty good start.

What would others add?

If anyone wants to help out, let me know.

-Taylor

> On Jan 22, 2019, at 10:37 AM, Bobby Evans  wrote:
> 
> I totally agree, especially with the performance improvements in it.
> 
> Thanks,
> 
> Bobby
> 
> On Tue, Jan 22, 2019 at 12:40 AM Roshan Naik 
> wrote:
> 
>> Now that  2.0 has all the votes it needs to move forward, maybe a good
>> time to think of some blogs to go with this long awaited release.
>> Some potential topics that come to mind are:
>> 1- Overview of new features and major changes since 1.x2- Re-architecture
>> (messaging, threading, back pressure)3- Micro benchmarks4- Revisit the
>> famous Yahoo benchmark5- Window state persistence6- SQL enhancements7- new
>> Metrics stuff8- Kafka related changes9- Security10- An area you have worked
>> on ?11- Other ideas ?
>> Anyone interested in contributing blogs ?
>> FYI: I am working on content for topics 2 & 3.
>> 
>> -roshan



signature.asc
Description: Message signed with OpenPGP

[VOTE] Release Apache Storm 1.1.4 (rc1)

[P. Taylor Goetz]

This is a call to vote on releasing Apache Storm 1.1.4 (rc1)

Full list of changes in this release:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.1.4-rc1/RELEASE_NOTES.html

The tag/commit to be voted upon is v1.1.4:

https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=dfb1f971c35ca985a35692aed6d28be3d7e707de;hb=babab9648a6deb3d444c45bdd6d0ec30804e91f1

The source archive being voted upon can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.1.4-rc1/apache-storm-1.1.4-src.tar.gz

Other release files, signatures and digests can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.1.4-rc1/

The release artifacts are signed with the following key:

https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd

The Nexus staging repository for this release is:

https://repository.apache.org/content/repositories/orgapachestorm-1075

Please vote on releasing this package as Apache Storm 1.1.4.

When voting, please list the actions taken to verify the release.

This vote will be open for at least 72 hours.

[ ] +1 Release this package as Apache Storm 1.1.4
[ ]  0 No opinion
[ ] -1 Do not release this package because...

Thanks to everyone who contributed to this release.

-Taylor

[VOTE] Release Apache Storm 1.2.3 (rc1)

[P. Taylor Goetz]

This is a call to vote on releasing Apache Storm 1.2.3 (rc1)

Full list of changes in this release:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.3-rc1/RELEASE_NOTES.html

The tag/commit to be voted upon is v1.2.3:

https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=5eaaa51591f2e4dc3e31f22bcc581af4a1f39c03;hb=6ba98b215857656e0186887b5d1a6a5aceee10c4

The source archive being voted upon can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.3-rc1/apache-storm-1.2.3-src.tar.gz

Other release files, signatures and digests can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.3-rc1/

The release artifacts are signed with the following key:

https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd

The Nexus staging repository for this release is:

https://repository.apache.org/content/repositories/orgapachestorm-1074

Please vote on releasing this package as Apache Storm 1.2.3.

When voting, please list the actions taken to verify the release.

This vote will be open for at least 72 hours.

[ ] +1 Release this package as Apache Storm 1.2.3
[ ]  0 No opinion
[ ] -1 Do not release this package because...

Thanks to everyone who contributed to this release.

-Taylor

[VOTE] Release Apache Storm 2.0.0 (rc4)

[P. Taylor Goetz]

This is a call to vote on releasing Apache Storm 2.0.0 (rc4)

Full list of changes in this release:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc4/RELEASE_NOTES.html

The tag/commit to be voted upon is v2.0.0:

https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=1eece73e8c9ed7f41d2f20f727bc7f644c499360;hb=ddee8decac57d1a4a0aa23cc76066609a2abc8d2

The source archive being voted upon can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc4/apache-storm-2.0.0-src.tar.gz

Other release files, signatures and digests can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc4/

The release artifacts are signed with the following key:

https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd

The Nexus staging repository for this release is:

https://repository.apache.org/content/repositories/orgapachestorm-1073

Please vote on releasing this package as Apache Storm 2.0.0.

When voting, please list the actions taken to verify the release.

This vote will be open for at least 72 hours.

[ ] +1 Release this package as Apache Storm 2.0.0
[ ]  0 No opinion
[ ] -1 Do not release this package because...

Thanks to everyone who contributed to this release.

-Taylor

Re: Maintenance releases

[P. Taylor Goetz]

Not that I’m aware of. I’ll cue up the 1.x releases behind the 2.0 release.

-Taylor

> On Jan 7, 2019, at 3:58 AM, Stig Rohde Døssing  wrote:
> 
> I think we should try to get the next 1.x releases out soon. Are there any
> blockers?

Re: Storm 2.0.0 release?

[P. Taylor Goetz]

If no one objects, I’ll kick off a release candidate.

-Taylor

> On Jan 4, 2019, at 9:06 PM, saurabh mimani  wrote:
> 
> Hey, Any approximate date for 2.0 release given there are no blockers?
> 
> 
> 
> Best Regards
> 
> Saurabh Kumar Mimani
> 
> 
> 
> 
> On Sat, Dec 22, 2018 at 1:13 AM Stig Rohde Døssing 
> wrote:
> 
>> Looks good to me, the blockers list in JIRA is empty for 2.0.0.
>> 
>>> Den fre. 21. dec. 2018 kl. 19.52 skrev Bobby Evans :
>>> 
>>> I think all of the blockers are in now.  Please take a look and
>> hopefully,
>>> we can get a release out soon.
>>> 
>>> Thanks,
>>> 
>>> Bobby
>>> 
>>> 
 On Fri, Dec 14, 2018 at 9:02 AM Bobby Evans  wrote:
 
 Sorry I was out at a conference for the past week, and have been heads
>>> down
 on a different project for a while before that.  I'll respond to the
>>> JIRA.
 I am happy to let it go in.
 
 Thanks,
 
 Bobby
 
 On Thu, Dec 13, 2018 at 1:07 PM Stig Rohde Døssing <
>>> stigdoess...@gmail.com
> 
 wrote:
 
> I think STORM-2990/3279 is ready. Bobby had a question (
> https://github.com/apache/storm/pull/2907#discussion_r234329136)
 regarding
> whether Kafka offsets loop, but I wasn't sure where he was going with
>>> it,
> so I didn't want to merge prematurely.
> 
> I agree that we can postpone STORM-2720. As far as I know it's
>> waiting
 for
> STORM-2990 to go in, since it's going to be touching the same code.
> 
> Den tor. 13. dec. 2018 kl. 19.54 skrev Roshan Naik
> :
> 
>> Sounds like -  https://github.com/apache/storm/pull/2913
>>> (STORM-3290)
> is
>> merged -  https://github.com/apache/storm/pull/2908 (STORM-3276)
>> is
>> nearly complete and may need some small tweaks. -
>> https://github.com/apache/storm/pull/2907  (STORM-2990,
>> STORM-3279)
>> appears ready to be committed ?
>> 
>> and- https://github.com/apache/storm/pull/2911   - (STORM-2720)
 seems a
>> bit inactive and may not be critical enough to wait on.
>> 
>> -roshan
>>On Monday, November 26, 2018, 9:49:30 AM PST, Stig Rohde
>> Døssing
>>> <
>> stigdoess...@gmail.com> wrote:
>> 
>> I would like to get at least
 https://github.com/apache/storm/pull/2913
>> (breaking changes) and https://github.com/apache/storm/pull/2908
>> (regression) in.
>> 
>> I think it would be nice to also get
>> https://github.com/apache/storm/pull/2907 and
>> https://github.com/apache/storm/pull/2911 in, but if we're in a
>>> hurry
> they
>> could go in the next release.
>> 
>> Den man. 26. nov. 2018 kl. 17.37 skrev Julien Nioche <
>> lists.digitalpeb...@gmail.com>:
>> 
>>> Hi devs,
>>> 
>>> Is there anything blocking the release of Storm 2.0? Any idea of
>>> when
> it
>>> could happen?
>>> 
>>> Thanks
>>> 
>>> Julien
>>> 
>>> --
>>> 
>>> *Open Source Solutions for Text Engineering*
>>> 
>>> http://www.digitalpebble.com
>>> http://digitalpebble.blogspot.com/
>>> #digitalpebble 
>>> 
>> 
> 
 
>>> 
>> 

[CANCELED] [VOTE] Release Apache Storm 2.0.0 (rc3)

[P. Taylor Goetz]

Canceling this vote due to blocker issues.

-Taylor

> On Oct 16, 2018, at 3:48 PM, P. Taylor Goetz  wrote:
> 
> This is a call to vote on releasing Apache Storm 2.0.0 (rc3)
> 
> Full list of changes in this release:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc3/RELEASE_NOTES.html
> 
> The tag/commit to be voted upon is v2.0.0:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=commit;h=d2d6f40344e6cc92ab07f3a462d577ef6b61f8b1
> 
> The source archive being voted upon can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc3/apache-storm-2.0.0-src.tar.gz
> 
> Other release files, signatures and digests can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc3/
> 
> The release artifacts are signed with the following key:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
> 
> The Nexus staging repository for this release is:
> 
> https://repository.apache.org/content/repositories/orgapachestorm-1072
> 
> Please vote on releasing this package as Apache Storm 2.0.0.
> 
> When voting, please list the actions taken to verify the release.
> 
> This vote will be open for at least 72 hours.
> 
> [ ] +1 Release this package as Apache Storm 2.0.0
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
> 
> Thanks to everyone who contributed to this release.
> 
> -Taylor



signature.asc
Description: Message signed with OpenPGP

[VOTE] Release Apache Storm 2.0.0 (rc3)

[P. Taylor Goetz]

This is a call to vote on releasing Apache Storm 2.0.0 (rc3)

Full list of changes in this release:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc3/RELEASE_NOTES.html

The tag/commit to be voted upon is v2.0.0:

https://git-wip-us.apache.org/repos/asf?p=storm.git;a=commit;h=d2d6f40344e6cc92ab07f3a462d577ef6b61f8b1

The source archive being voted upon can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc3/apache-storm-2.0.0-src.tar.gz

Other release files, signatures and digests can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc3/

The release artifacts are signed with the following key:

https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd

The Nexus staging repository for this release is:

https://repository.apache.org/content/repositories/orgapachestorm-1072

Please vote on releasing this package as Apache Storm 2.0.0.

When voting, please list the actions taken to verify the release.

This vote will be open for at least 72 hours.

[ ] +1 Release this package as Apache Storm 2.0.0
[ ]  0 No opinion
[ ] -1 Do not release this package because...

Thanks to everyone who contributed to this release.

-Taylor


signature.asc
Description: Message signed with OpenPGP

Re: Ready for another 2.0.0 RC

[P. Taylor Goetz]

Great. Expect one later today or tomorrow.

-Taylor

> On Oct 15, 2018, at 12:03 PM, Bobby Evans  wrote:
> 
> Taylor,
> 
> I think we have everything merged that was blocking the last 2.0.0
> release.  If you have time please take a look at doing another one.
> 
> Thanks,
> 
> Bobby

[CANCELED] [VOTE] Release Apache Storm 2.0.0 (rc2)

[P. Taylor Goetz]

Canceling so blockers can be fixed for the 2.0.0 release.

-Taylor

> On Oct 9, 2018, at 4:03 PM, P. Taylor Goetz  wrote:
> 
> This is a call to vote on releasing Apache Storm 2.0.0 (rc2)
> 
> Full list of changes in this release:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc2/RELEASE_NOTES.html
> 
> The tag/commit to be voted upon is v2.0.0:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=f8d04910dc3fd14534c186232ecf7882d8916f67;hb=f8d04910dc3fd14534c186232ecf7882d8916f67
> 
> The source archive being voted upon can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc2/apache-storm-2.0.0-src.tar.gz
> 
> Other release files, signatures and digests can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc2/
> 
> The release artifacts are signed with the following key:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
> 
> The Nexus staging repository for this release is:
> 
> https://repository.apache.org/content/repositories/orgapachestorm-1071
> 
> Please vote on releasing this package as Apache Storm 2.0.0.
> 
> When voting, please list the actions taken to verify the release.
> 
> This vote will be open for at least 72 hours.
> 
> [ ] +1 Release this package as Apache Storm 2.0.0
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
> 
> Thanks to everyone who contributed to this release.
> 
> -Taylor



signature.asc
Description: Message signed with OpenPGP

[VOTE] Release Apache Storm 2.0.0 (rc2)

[P. Taylor Goetz]

This is a call to vote on releasing Apache Storm 2.0.0 (rc2)

Full list of changes in this release:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc2/RELEASE_NOTES.html

The tag/commit to be voted upon is v2.0.0:

https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=f8d04910dc3fd14534c186232ecf7882d8916f67;hb=f8d04910dc3fd14534c186232ecf7882d8916f67

The source archive being voted upon can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc2/apache-storm-2.0.0-src.tar.gz

Other release files, signatures and digests can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc2/

The release artifacts are signed with the following key:

https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd

The Nexus staging repository for this release is:

https://repository.apache.org/content/repositories/orgapachestorm-1071

Please vote on releasing this package as Apache Storm 2.0.0.

When voting, please list the actions taken to verify the release.

This vote will be open for at least 72 hours.

[ ] +1 Release this package as Apache Storm 2.0.0
[ ]  0 No opinion
[ ] -1 Do not release this package because...

Thanks to everyone who contributed to this release.

-Taylor


signature.asc
Description: Message signed with OpenPGP

[CANCELED] [VOTE] Release Apache Storm 2.0.0 (rc1)

[P. Taylor Goetz]

Canceling in order to include new fixes.

-Taylor

> On Sep 21, 2018, at 2:22 PM, P. Taylor Goetz  wrote:
> 
> This is a call to vote on releasing Apache Storm 2.0.0 (rc1)
> 
> Full list of changes in this release:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc1/RELEASE_NOTES.html
> 
> The tag/commit to be voted upon is v2.0.0:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=062bb2f158a66b802a3ad7bdda14fb8f70cf9b88;hb=062bb2f158a66b802a3ad7bdda14fb8f70cf9b88
> 
> The source archive being voted upon can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc1/apache-storm-2.0.0-src.tar.gz
> 
> Other release files, signatures and digests can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc1/
> 
> The release artifacts are signed with the following key:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
> 
> The Nexus staging repository for this release is:
> 
> https://repository.apache.org/content/repositories/orgapachestorm-1070
> 
> Please vote on releasing this package as Apache Storm 2.0.0.
> 
> When voting, please list the actions taken to verify the release.
> 
> This vote will be open for at least 72 hours.
> 
> [ ] +1 Release this package as Apache Storm 2.0.0
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
> 
> Thanks to everyone who contributed to this release.
> 
> -Taylor



signature.asc
Description: Message signed with OpenPGP

Re: [VOTE] Release Apache Storm 2.0.0 (rc1)

[P. Taylor Goetz]

If we can keep the JIRA fix version for this release 2.0.0 it will keep the 
release notes cleaner.

I can put together a release candidate tomorrow.

-Taylor

> On Oct 8, 2018, at 9:44 AM, Bobby Evans  wrote:
> 
> Taylor,
> 
> All of the blockers are now merged into master.  I think we are ready to do
> another release.  Just so you know I marked all of the JIRAs that were
> merged into master since this vote with 2.0.1 release version.  Not sure if
> we just want to fast forward to 2.0.1, or if you want it to stay as 2.0.0.
> If it is the later let me know and I am happy to move all of the JIRA to
> 2.0.0 release version.
> 
> Thanks,
> 
> Bobby
> 
> On Sun, Sep 30, 2018 at 2:55 AM Jungtaek Lim  wrote:
> 
>> Just filed STORM-3238 [1] for topology log search error, and STORM-3239 [2]
>> for worker profile.
>> 
>> - Jungtaek Lim (HeartSaVioR)
>> 
>> 1. https://issues.apache.org/jira/browse/STORM-3238
>> 2. https://issues.apache.org/jira/browse/STORM-3239
>> 
>> 2018년 9월 28일 (금) 오전 12:13, Govind Menon 님이 작성:
>> 
>>> I have a fix for the worker profiling that I'm testing now - I should
>> have
>>> a PR up today.
>>> 
>>> On Thu, Sep 27, 2018 at 3:50 AM Jungtaek Lim  wrote:
>>> 
>>>> Sorry I was in a long holidays in South Korea and am just back today.
>>> I'll
>>>> reproduce them and file JIRAs but it is pretty simple to reproduce,
>> basic
>>>> search in topology didn't work as well as operations in worker
>> profiling
>>>> didn't work. So if someone would like to tackle them it should be
>> pretty
>>>> easy to reproduce for someone as well.
>>>> 
>>>> -Jungtaek Lim (HeartSaVioR)
>>>> 
>>>> 2018년 9월 26일 (수) 오후 9:02, Kishorkumar Patil >> 님이
>>>> 작성:
>>>> 
>>>>> I have patch up for  WorkerToken Auto renewal fix. I think this
>> should
>>> be
>>>>> added to 2.x RC.
>>>>> 
>>>>> https://issues.apache.org/jira/browse/STORM-3235
>>>>> https://github.com/apache/storm/pull/2850
>>>>> 
>>>>> -Kishor
>>>>> 
>>>>> On Tue, Sep 25, 2018 at 8:04 PM P. Taylor Goetz 
>>>> wrote:
>>>>> 
>>>>>> Jungtaek, can you elaborate on the issues you ran into when testing
>>> the
>>>>> rc
>>>>>> and/or file JIRAs?
>>>>>> 
>>>>>> -Taylor
>>>>>> 
>>>>>>> On Sep 25, 2018, at 4:02 PM, Bobby Evans 
>> wrote:
>>>>>>> 
>>>>>>> Nope.  I plan to start looking into them, unless someone else is
>>>>> already
>>>>>>> doing so.
>>>>>>> 
>>>>>>> Thanks,
>>>>>>> 
>>>>>>> Bobby
>>>>>>> 
>>>>>>> On Tue, Sep 25, 2018 at 2:48 PM P. Taylor Goetz <
>> ptgo...@gmail.com
>>>> 
>>>>>> wrote:
>>>>>>> 
>>>>>>>> Thanks for the update. I will cancel the vote.
>>>>>>>> 
>>>>>>>> Do the fixes you merged cover the bugs that Jungtaek pointed
>> out?
>>>>>>>> 
>>>>>>>> -Taylor
>>>>>>>> 
>>>>>>>>> On Sep 25, 2018, at 1:56 PM, Bobby Evans 
>>> wrote:
>>>>>>>>> 
>>>>>>>>> Just FYI Taylor I just merged in 3 JIRA to the master branch
>> and
>>>> will
>>>>>>>>> probably merge in the fix for the UI that Govind mentioned, but
>>> all
>>>>> of
>>>>>>>> them
>>>>>>>>> would be okay to go into 2.0.0 as well.  Since this RC looks
>> like
>>>> it
>>>>> is
>>>>>>>> not
>>>>>>>>> going to pass if you want to move the tag up on the master
>>> branch,
>>>>> that
>>>>>>>>> would be fine, once we have the fixes in.
>>>>>>>>> 
>>>>>>>>> Thanks,
>>>>>>>>> 
>>>>>>>>> Bobby
>>>>>>>>> 
>>>>>>>>> On Tue, Sep 25, 2018 at 9:31 AM Govind Menon
>>>> >>>>> 
>>>>>>>>> wrote:
>>>>>>

Re: [GitHub] storm issue #1136: [STORM-1565] Multi-Lang Performance Improvements

[P. Taylor Goetz]

Andrew,

Thanks for bringing the private conversation back to the dev@ list so everyone 
has more context.

That being said, I’d encourage the use of the public mailing lists as much as 
possible. Private conversations exclude the larger community from participating 
in potentially fruitful discussions.

Don’t get me wrong, I applaud you doing the right thing in bringing this back 
to the community. I just wish it could have happened sooner.

All good. We just do better next time. :)

-Taylor

> On Sep 26, 2018, at 5:58 PM, amontalenti  wrote:
> 
> Github user amontalenti commented on the issue:
> 
>https://github.com/apache/storm/pull/1136
> 
>Was chatting with @roshannaik and @dan-blanchard today, and this PR came 
> up.
> 
>Someone on Storm team may benefit from taking a look at this as part of 
> the performance revisions being done for Storm 2.0. As mentioned in [#428 in 
> streamparse](https://github.com/Parsely/streamparse/issues/428#issuecomment-380135343)
>  -- the community project for running Python multi-lang topologies with Storm 
> -- getting this merged somewhere in the Storm codebase would open up the 
> possibility to switch serializer from Kryo & JSON to msgpack throughout, 
> which would speed up multi-lang use cases considerably. This PR includes a 
> pure Java implementation of a msgpack serializer, as well as pointers to the 
> right msgpack library in the Java community; it just needs to be reviewed, 
> tested, and merged.
> 
> 
> ---

Re: [VOTE] Release Apache Storm 2.0.0 (rc1)

[P. Taylor Goetz]

Jungtaek, can you elaborate on the issues you ran into when testing the rc 
and/or file JIRAs?

-Taylor

> On Sep 25, 2018, at 4:02 PM, Bobby Evans  wrote:
> 
> Nope.  I plan to start looking into them, unless someone else is already
> doing so.
> 
> Thanks,
> 
> Bobby
> 
> On Tue, Sep 25, 2018 at 2:48 PM P. Taylor Goetz  wrote:
> 
>> Thanks for the update. I will cancel the vote.
>> 
>> Do the fixes you merged cover the bugs that Jungtaek pointed out?
>> 
>> -Taylor
>> 
>>> On Sep 25, 2018, at 1:56 PM, Bobby Evans  wrote:
>>> 
>>> Just FYI Taylor I just merged in 3 JIRA to the master branch and will
>>> probably merge in the fix for the UI that Govind mentioned, but all of
>> them
>>> would be okay to go into 2.0.0 as well.  Since this RC looks like it is
>> not
>>> going to pass if you want to move the tag up on the master branch, that
>>> would be fine, once we have the fixes in.
>>> 
>>> Thanks,
>>> 
>>> Bobby
>>> 
>>> On Tue, Sep 25, 2018 at 9:31 AM Govind Menon 
>>> wrote:
>>> 
>>>> Hi all,
>>>> 
>>>> I introduced a bug with the visualization as part of the UI migration
>> with
>>>> the following fix - https://github.com/apache/storm/pull/2849. It's
>> not a
>>>> show stopper by any means and there's a workaround (specifically hiding
>>>> system stats on the UI). I think we should include this in the RC.
>>>> 
>>>> Thanks,
>>>> Govind.
>>>> 
>>>> 
>>>> On Mon, Sep 24, 2018 at 3:09 PM Alexandre Vermeerbergen <
>>>> avermeerber...@gmail.com> wrote:
>>>> 
>>>>> Hello All,
>>>>> 
>>>>> I will need a little bit time to test this new release with our 15+
>>>>> topologies, but it's definitely worth and exiting !
>>>>> "stay tuned" :)
>>>>> 
>>>>> Best regards,
>>>>> Alexandre Vermeerbergen
>>>>> 
>>>>> Le ven. 21 sept. 2018 à 20:23, P. Taylor Goetz  a
>>>>> écrit :
>>>>>> 
>>>>>> This is a call to vote on releasing Apache Storm 2.0.0 (rc1)
>>>>>> 
>>>>>> Full list of changes in this release:
>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc1/RELEASE_NOTES.html
>>>>>> 
>>>>>> The tag/commit to be voted upon is v2.0.0:
>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=062bb2f158a66b802a3ad7bdda14fb8f70cf9b88;hb=062bb2f158a66b802a3ad7bdda14fb8f70cf9b88
>>>>>> 
>>>>>> The source archive being voted upon can be found here:
>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc1/apache-storm-2.0.0-src.tar.gz
>>>>>> 
>>>>>> Other release files, signatures and digests can be found here:
>>>>>> 
>>>>>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc1/
>>>>>> 
>>>>>> The release artifacts are signed with the following key:
>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
>>>>>> 
>>>>>> The Nexus staging repository for this release is:
>>>>>> 
>>>>>> 
>> https://repository.apache.org/content/repositories/orgapachestorm-1070
>>>>>> 
>>>>>> Please vote on releasing this package as Apache Storm 2.0.0.
>>>>>> 
>>>>>> When voting, please list the actions taken to verify the release.
>>>>>> 
>>>>>> This vote will be open for at least 72 hours.
>>>>>> 
>>>>>> [ ] +1 Release this package as Apache Storm 2.0.0
>>>>>> [ ]  0 No opinion
>>>>>> [ ] -1 Do not release this package because...
>>>>>> 
>>>>>> Thanks to everyone who contributed to this release.
>>>>>> 
>>>>>> -Taylor
>>>>> 
>>>> 
>> 
>> 



signature.asc
Description: Message signed with OpenPGP

Re: [VOTE] Release Apache Storm 2.0.0 (rc1)

[P. Taylor Goetz]

Thanks for the update. I will cancel the vote.

Do the fixes you merged cover the bugs that Jungtaek pointed out?

-Taylor

> On Sep 25, 2018, at 1:56 PM, Bobby Evans  wrote:
> 
> Just FYI Taylor I just merged in 3 JIRA to the master branch and will
> probably merge in the fix for the UI that Govind mentioned, but all of them
> would be okay to go into 2.0.0 as well.  Since this RC looks like it is not
> going to pass if you want to move the tag up on the master branch, that
> would be fine, once we have the fixes in.
> 
> Thanks,
> 
> Bobby
> 
> On Tue, Sep 25, 2018 at 9:31 AM Govind Menon 
> wrote:
> 
>> Hi all,
>> 
>> I introduced a bug with the visualization as part of the UI migration with
>> the following fix - https://github.com/apache/storm/pull/2849. It's not a
>> show stopper by any means and there's a workaround (specifically hiding
>> system stats on the UI). I think we should include this in the RC.
>> 
>> Thanks,
>> Govind.
>> 
>> 
>> On Mon, Sep 24, 2018 at 3:09 PM Alexandre Vermeerbergen <
>> avermeerber...@gmail.com> wrote:
>> 
>>> Hello All,
>>> 
>>> I will need a little bit time to test this new release with our 15+
>>> topologies, but it's definitely worth and exiting !
>>> "stay tuned" :)
>>> 
>>> Best regards,
>>> Alexandre Vermeerbergen
>>> 
>>> Le ven. 21 sept. 2018 à 20:23, P. Taylor Goetz  a
>>> écrit :
>>>> 
>>>> This is a call to vote on releasing Apache Storm 2.0.0 (rc1)
>>>> 
>>>> Full list of changes in this release:
>>>> 
>>>> 
>>> 
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc1/RELEASE_NOTES.html
>>>> 
>>>> The tag/commit to be voted upon is v2.0.0:
>>>> 
>>>> 
>>> 
>> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=062bb2f158a66b802a3ad7bdda14fb8f70cf9b88;hb=062bb2f158a66b802a3ad7bdda14fb8f70cf9b88
>>>> 
>>>> The source archive being voted upon can be found here:
>>>> 
>>>> 
>>> 
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc1/apache-storm-2.0.0-src.tar.gz
>>>> 
>>>> Other release files, signatures and digests can be found here:
>>>> 
>>>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc1/
>>>> 
>>>> The release artifacts are signed with the following key:
>>>> 
>>>> 
>>> 
>> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
>>>> 
>>>> The Nexus staging repository for this release is:
>>>> 
>>>> https://repository.apache.org/content/repositories/orgapachestorm-1070
>>>> 
>>>> Please vote on releasing this package as Apache Storm 2.0.0.
>>>> 
>>>> When voting, please list the actions taken to verify the release.
>>>> 
>>>> This vote will be open for at least 72 hours.
>>>> 
>>>> [ ] +1 Release this package as Apache Storm 2.0.0
>>>> [ ]  0 No opinion
>>>> [ ] -1 Do not release this package because...
>>>> 
>>>> Thanks to everyone who contributed to this release.
>>>> 
>>>> -Taylor
>>> 
>> 



signature.asc
Description: Message signed with OpenPGP

[VOTE] Release Apache Storm 2.0.0 (rc1)

[P. Taylor Goetz]

This is a call to vote on releasing Apache Storm 2.0.0 (rc1)

Full list of changes in this release:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc1/RELEASE_NOTES.html

The tag/commit to be voted upon is v2.0.0:

https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=062bb2f158a66b802a3ad7bdda14fb8f70cf9b88;hb=062bb2f158a66b802a3ad7bdda14fb8f70cf9b88

The source archive being voted upon can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc1/apache-storm-2.0.0-src.tar.gz

Other release files, signatures and digests can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc1/

The release artifacts are signed with the following key:

https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd

The Nexus staging repository for this release is:

https://repository.apache.org/content/repositories/orgapachestorm-1070

Please vote on releasing this package as Apache Storm 2.0.0.

When voting, please list the actions taken to verify the release.

This vote will be open for at least 72 hours.

[ ] +1 Release this package as Apache Storm 2.0.0
[ ]  0 No opinion
[ ] -1 Do not release this package because...

Thanks to everyone who contributed to this release.

-Taylor


signature.asc
Description: Message signed with OpenPGP

Re: Regarding releasing Apache Storm 2.0.0

[P. Taylor Goetz]

I’m hitting lots of issues with SNAPSHOT dependencies (as I expected). This is 
internal to storm’s pom structure and likely the result of all the module 
reorganization. I’ll probably create a temporary release branch so I can create 
a pull request for the necessary changes back to master, but continue with the 
release candidate.

-Taylor

> On Sep 20, 2018, at 3:58 PM, P. Taylor Goetz  wrote:
> 
> I’ll put together a release candidate.
> 
> -Taylor
> 
>> On Sep 20, 2018, at 1:55 PM, Bobby Evans  wrote:
>> 
>> I just merged in the last outstanding JIRA/pull request.  I think we are
>> good for a 2.0.0 RC.
>> 
>> Thanks,
>> 
>> Bobby
>> 
>> On Wed, Sep 19, 2018 at 12:33 PM Bobby Evans  wrote:
>> 
>>> Sounds good.
>>> 
>>> I just filed https://issues.apache.org/jira/browse/STORM-3230 and I'll be
>>> putting up a pull request shortly. I would like to see it in before a 2.x
>>> release, but it is kind of minor because ZK has to really be overloaded to
>>> hit this, and we tend to recover after a while.
>>> 
>>> I'll look at getting the rest in ASAP.
>>> 
>>> Thanks,
>>> 
>>> Bobby
>>> 
>>> 
>>> On Tue, Sep 18, 2018 at 3:54 PM P. Taylor Goetz  wrote:
>>> 
>>>> I’m ready to release when everything is ready to go. Since we haven’t
>>>> released from the 2.0-based master branch, I wouldn’t be surprised if I run
>>>> into release issues, but I’ll slog through it.
>>>> 
>>>> -Taylor
>>>> 
>>>>> On Sep 18, 2018, at 10:46 AM, Bobby Evans  wrote:
>>>>> 
>>>>> Great work everyone.  We are really close on this.  We have everything
>>>> in
>>>>> except for https://github.com/apache/storm/pull/2719, but there has
>>>> been no
>>>>> movement there, so I will try and put up an alternative pull request.
>>>>> 
>>>>> Also We noticed that a recent merge broke some things fairly badly so we
>>>>> need to get https://github.com/apache/storm/pull/2839 in, but that is
>>>> just
>>>>> a matter of waiting a few more hours for the 24 hours to be up.
>>>>> 
>>>>> Great work everyone, hopefully we will have an RC up for a vote a little
>>>>> over a day from now.
>>>>> 
>>>>> Thanks,
>>>>> 
>>>>> Bobby
>>>>> 
>>>>> P.S. Taylor,  You have put up all of the release candidates in the past
>>>> and
>>>>> done all of the votes for them.  If you want to continue the trend that
>>>> is
>>>>> fine with me, but if not I am happy to do it, but I might have to bug
>>>> you
>>>>> to be sure I do it all correctly.
>>>>> 
>>>>> On Mon, Sep 17, 2018 at 9:13 AM Bobby Evans  wrote:
>>>>> 
>>>>>> I think we are really close on this and I would love to see us get an
>>>> RC
>>>>>> out ASAP.
>>>>>> 
>>>>>> We are still missing some things that Stig called out.
>>>>>> 
>>>>>> https://github.com/apache/storm/pull/2719 has a build issue, not sure
>>>> if
>>>>>> we need to make an alternative patch or not.
>>>>>> https://github.com/apache/storm/pull/2800  has a newer alternative
>>>> patch
>>>>>> https://github.com/apache/storm/pull/2836 please take a look.
>>>>>> https://github.com/apache/storm/pull/2805 has some merge conflicts
>>>>>> currently, but everyone please take a chance to review it.
>>>>>> 
>>>>>> Thanks,
>>>>>> 
>>>>>> Bobby
>>>>>> 
>>>>>> On Fri, Sep 14, 2018 at 2:57 AM Jungtaek Lim 
>>>> wrote:
>>>>>> 
>>>>>>> I have sought the name of client artifact from some of streaming
>>>>>>> frameworks. Please refer below:
>>>>>>> 
>>>>>>> Spark: spark-core
>>>>>>> Kafka: kafka-clients
>>>>>>> Flink: flink-clients
>>>>>>> Heron: heron-api
>>>>>>> 
>>>>>>> Based on divergence, I don't see the reason "storm-core" is the only
>>>> name
>>>>>>> which avoid confusion. Actually, if my understanding is right, we
>>>> need to
>>

Re: Regarding releasing Apache Storm 2.0.0

[P. Taylor Goetz]

I’ll put together a release candidate.

-Taylor

> On Sep 20, 2018, at 1:55 PM, Bobby Evans  wrote:
> 
> I just merged in the last outstanding JIRA/pull request.  I think we are
> good for a 2.0.0 RC.
> 
> Thanks,
> 
> Bobby
> 
> On Wed, Sep 19, 2018 at 12:33 PM Bobby Evans  wrote:
> 
>> Sounds good.
>> 
>> I just filed https://issues.apache.org/jira/browse/STORM-3230 and I'll be
>> putting up a pull request shortly. I would like to see it in before a 2.x
>> release, but it is kind of minor because ZK has to really be overloaded to
>> hit this, and we tend to recover after a while.
>> 
>> I'll look at getting the rest in ASAP.
>> 
>> Thanks,
>> 
>> Bobby
>> 
>> 
>> On Tue, Sep 18, 2018 at 3:54 PM P. Taylor Goetz  wrote:
>> 
>>> I’m ready to release when everything is ready to go. Since we haven’t
>>> released from the 2.0-based master branch, I wouldn’t be surprised if I run
>>> into release issues, but I’ll slog through it.
>>> 
>>> -Taylor
>>> 
>>>> On Sep 18, 2018, at 10:46 AM, Bobby Evans  wrote:
>>>> 
>>>> Great work everyone.  We are really close on this.  We have everything
>>> in
>>>> except for https://github.com/apache/storm/pull/2719, but there has
>>> been no
>>>> movement there, so I will try and put up an alternative pull request.
>>>> 
>>>> Also We noticed that a recent merge broke some things fairly badly so we
>>>> need to get https://github.com/apache/storm/pull/2839 in, but that is
>>> just
>>>> a matter of waiting a few more hours for the 24 hours to be up.
>>>> 
>>>> Great work everyone, hopefully we will have an RC up for a vote a little
>>>> over a day from now.
>>>> 
>>>> Thanks,
>>>> 
>>>> Bobby
>>>> 
>>>> P.S. Taylor,  You have put up all of the release candidates in the past
>>> and
>>>> done all of the votes for them.  If you want to continue the trend that
>>> is
>>>> fine with me, but if not I am happy to do it, but I might have to bug
>>> you
>>>> to be sure I do it all correctly.
>>>> 
>>>> On Mon, Sep 17, 2018 at 9:13 AM Bobby Evans  wrote:
>>>> 
>>>>> I think we are really close on this and I would love to see us get an
>>> RC
>>>>> out ASAP.
>>>>> 
>>>>> We are still missing some things that Stig called out.
>>>>> 
>>>>> https://github.com/apache/storm/pull/2719 has a build issue, not sure
>>> if
>>>>> we need to make an alternative patch or not.
>>>>> https://github.com/apache/storm/pull/2800  has a newer alternative
>>> patch
>>>>> https://github.com/apache/storm/pull/2836 please take a look.
>>>>> https://github.com/apache/storm/pull/2805 has some merge conflicts
>>>>> currently, but everyone please take a chance to review it.
>>>>> 
>>>>> Thanks,
>>>>> 
>>>>> Bobby
>>>>> 
>>>>> On Fri, Sep 14, 2018 at 2:57 AM Jungtaek Lim 
>>> wrote:
>>>>> 
>>>>>> I have sought the name of client artifact from some of streaming
>>>>>> frameworks. Please refer below:
>>>>>> 
>>>>>> Spark: spark-core
>>>>>> Kafka: kafka-clients
>>>>>> Flink: flink-clients
>>>>>> Heron: heron-api
>>>>>> 
>>>>>> Based on divergence, I don't see the reason "storm-core" is the only
>>> name
>>>>>> which avoid confusion. Actually, if my understanding is right, we
>>> need to
>>>>>> let end users including "storm-server" when running local cluster,
>>> then
>>>>>> "storm-core" vs "storm-server" would give real confusion. I guess we
>>>>>> already discussed about the naming, and given that we don't rename it
>>> we
>>>>>> are OK with renamed artifacts.
>>>>>> 
>>>>>> 2018년 9월 14일 (금) 오후 4:07, Roshan Naik >>> 님이
>>>>>> 작성:
>>>>>> 
>>>>>>> Happy to see consensus in moving fwd with 2.0 soon.
>>>>>>> I will try to get a minor patch (STORM-3205) within 24 hours ... as
>>> it
>>>>>>> seems like it has potential to deliv

Re: Regarding releasing Apache Storm 2.0.0

[P. Taylor Goetz]

gt;>>> May be the RC can be cut once critical patches are merged.
>>>>>> 
>>>>>> On Tue, 11 Sep 2018 at 10:28, Stig Rohde Døssing <
>>>> stigdoess...@gmail.com>
>>>>>> wrote:
>>>>>> 
>>>>>>> +1 to cut an RC.
>>>>>>> 
>>>>>>> Here are a couple of PRs that could maybe go in
>>>>>>> 
>>>>>>> https://github.com/apache/storm/pull/2719
>>>>>>> https://github.com/apache/storm/pull/2800 (this one requires some
>>>>>> changes,
>>>>>>> but we should be able to fix it pretty quickly)
>>>>>>> also would like to get https://github.com/apache/storm/pull/2805
>>>>>> reviewed,
>>>>>>> it might change some public methods.
>>>>>>> 
>>>>>>> Other than that, we should try to remove as much deprecated code
>>> as we
>>>>>> can
>>>>>>> before release
>>>>>>> 
>>>>>>> https://issues.apache.org/jira/browse/STORM-2947
>>>>>>> 
>>>>>>> Den man. 10. sep. 2018 kl. 21.59 skrev Alexandre Vermeerbergen <
>>>>>>> avermeerber...@gmail.com>:
>>>>>>> 
>>>>>>>> +1 for an Storm 2.0 as soon as possible, let's jump into the
>>> future
>>>> :)
>>>>>>>> Le lun. 10 sept. 2018 à 21:50, Kishorkumar Patil
>>>>>>>>  a écrit :
>>>>>>>>> 
>>>>>>>>> Looking into all issues reported under epic
>>>>>>>>> https://issues.apache.org/jira/browse/STORM-2714 are
>>>>>> resolved/closed.
>>>>>>> I
>>>>>>>>> don't see any open issues/blockers at this point for going
>>> ahead
>>>>>> with
>>>>>>> 2.x
>>>>>>>>> release.
>>>>>>>>> 
>>>>>>>>> I am +1 to 2.0 release.
>>>>>>>>> 
>>>>>>>>> Regards,
>>>>>>>>> -Kishor
>>>>>>>>> 
>>>>>>>>> On Mon, Sep 10, 2018 at 2:24 PM, P. Taylor Goetz <
>>>> ptgo...@gmail.com
>>>>>>> 
>>>>>>>> wrote:
>>>>>>>>> 
>>>>>>>>>> I agree, and looking through the JIRAs against 2.0, I would
>>> say
>>>> a
>>>>>>>> majority
>>>>>>>>>> of the ones marked critical are not critical.
>>>>>>>>>> 
>>>>>>>>>> I’m +1 on moving forward with a 2.0 release, but will give
>>>> others
>>>>>>> time
>>>>>>>> to
>>>>>>>>>> respond with any JIRAs they think should be included.
>>>>>>>>>> 
>>>>>>>>>>> p.s. I don't want to create branch-2.x or branch-2.0.x
>>> until
>>>>>>>> absolutely
>>>>>>>>>>> necessary, I don't see any major features with pull
>>> requests
>>>> up
>>>>>> but
>>>>>>>> if
>>>>>>>>>> you
>>>>>>>>>>> do run across one please send something out before merging
>>> it
>>>>>> in,
>>>>>>> so
>>>>>>>> we
>>>>>>>>>> can
>>>>>>>>>>> set up the branches properly at that time.
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> Agree. We can always branch off the release tag/commit.
>>>>>>>>>> 
>>>>>>>>>> -Taylor
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>>> On Sep 10, 2018, at 12:25 PM, Bobby Evans <
>>> bo...@apache.org>
>>>>>>> wrote:
>>>>>>>>>>> 
>>>>>>>>>>> It has been nearly a month since this was originally sent
>>> out,
>>>>>> and
>>>>>>>> this
>>>>>>>>>> is
>>>>>>>>>>> not the first of these k

Re: Regarding releasing Apache Storm 2.0.0

[P. Taylor Goetz]

I agree, and looking through the JIRAs against 2.0, I would say a majority of 
the ones marked critical are not critical.

I’m +1 on moving forward with a 2.0 release, but will give others time to 
respond with any JIRAs they think should be included.

> p.s. I don't want to create branch-2.x or branch-2.0.x until absolutely
> necessary, I don't see any major features with pull requests up but if you
> do run across one please send something out before merging it in, so we can
> set up the branches properly at that time.


Agree. We can always branch off the release tag/commit.

-Taylor


> On Sep 10, 2018, at 12:25 PM, Bobby Evans  wrote:
> 
> It has been nearly a month since this was originally sent out, and this is
> not the first of these kinds of emails to go out about a 2.0.0 release.  I
> think we have made a lot of really good progress on getting ready for a 2.0
> release, and I really would like to see it happen before another month
> passes.
> 
> We have a 2.0 based deploy in some of our staging clusters, currently
> following the master branch with a little that is Yahoo specific on top. We
> would like to start pushing towards production with it soon.
> 
> There are a few issues that we are aware of.
> 
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20STORM%20AND%20affectedVersion%20in%20(2.0.0)%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC
> 
> There are no blockers still open, and only 4 issues listed as critical.
> 
> If others have any open issues that feel need to be addressed prior to a
> 2.0.0 release please respond to this with the JIRA number.  I would like to
> set a goal/tentative date of Sep 17th (one week from today) to put together
> a release candidate for a 2.0.0 release, and unless there are major
> blockers that show up I think we can do it.
> 
> Thanks,
> 
> Bobby Evans
> 
> p.s. I don't want to create branch-2.x or branch-2.0.x until absolutely
> necessary, I don't see any major features with pull requests up but if you
> do run across one please send something out before merging it in, so we can
> set up the branches properly at that time.
> 
> 
> On Wed, Jul 18, 2018 at 10:47 PM Jungtaek Lim  wrote:
> 
>> I'd like to say first, thanks Stig to take up remaining issues. Thanks to
>> his efforts, according to the epic, we have only one major issue left:
>> porting UI to Java [1], and pull request [2] is available for that.
>> There're another issues [3] [4] targeting 2.0.0 (since it is backward
>> incompatible) but they are all about removing deprecated things, so easier
>> to be reviewed and make decisions.
>> 
>> Once we have a patch for that now, IMHO it would be good to review and ship
>> in 2.0.0 if it wouldn't take a month or so. We could do some sanity tests
>> in parallel, so waiting for UI port would not block much time on releasing
>> Storm 2.0.0.
>> 
>> - Jungtaek Lim (HeartSaVioR)
>> 
>> 1. https://issues.apache.org/jira/browse/STORM-1311
>> 2. https://github.com/apache/storm/pull/2752
>> 3. https://issues.apache.org/jira/browse/STORM-2947
>> 4. https://issues.apache.org/jira/browse/STORM-3156
>> 
>> 
>> 2018년 7월 11일 (수) 오전 5:12, Alexandre Vermeerbergen <
>> avermeerber...@gmail.com>님이
>> 작성:
>> 
>>> +1 would love to try it when an RC is avail!
>>> 
>>> Alexandre Vermeerbergen
>>> 
>>> 2018-07-10 21:15 GMT+02:00 Arun Mahadevan :
>>>> +1 to get it out soon.
>>>> 
>>>> 
>>>> 
>>>> 
>>>> On 7/10/18, 11:52 AM, "P. Taylor Goetz"  wrote:
>>>> 
>>>>> +1 Sounds good to me.
>>>>> 
>>>>> -Taylor
>>>>> 
>>>>>> On Jul 10, 2018, at 2:18 AM, Jungtaek Lim  wrote:
>>>>>> 
>>>>>> Hi devs,
>>>>>> 
>>>>>> I hopefully have a time to sort out issues regarding Storm 2.0.0 and
>>> link
>>>>>> to epic issue.
>>>>>> 
>>>>>> https://issues.apache.org/jira/browse/STORM-2714
>>>>>> (require login to Apache JIRA to see issues in epic)
>>>>>> 
>>>>>> I guess we are close to the release, mostly left reviewing some
>> pending
>>>>>> pull requests, and some manual sanity tests.
>>>>>> 
>>>>>> Given that master branch is relatively stabilized for Travis CI
>> build,
>>> as
>>>>>> well as style check and Java port make codebase better (at least for
>>> me), I
>>>>>> would really want to make Storm 2.0.0 released sooner than later, and
>>> rely
>>>>>> majorly on 2.x version line.
>>>>>> 
>>>>>> So I would propose dev folks to concentrate on remaining tasks for
>>> Storm
>>>>>> 2.0.0 till we announce release. WDYT?
>>>>>> 
>>>>>> Thanks,
>>>>>> Jungtaek Lim (HeartSaVioR)
>>>>> 
>>>> 
>>> 
>> 



signature.asc
Description: Message signed with OpenPGP

Re: [DISCUSS] Plans for releasing Storm 1.2.3

[P. Taylor Goetz]

Sounds good to me. I’ll wait for others to weigh in to see if there’s anything 
pending that should be included. But IMO we can release at any time.

-Taylor

> On Aug 7, 2018, at 11:46 AM, Stig Rohde Døssing  
> wrote:
> 
> Hi devs,
> 
> I've seen a couple of requests for releasing Storm 1.2.3 soon on the users
> list. I know we're currently working toward a release for Storm 2.0.0, but
> I think it would be nice to release 1.2.3 first. It contains some decent
> bugfixes, and also contains the deprecation of storm-druid. Last release
> was a couple of months ago, so I think it's a good time to do another.
> 
> What do you think? Is there anything pending we should get in first?



signature.asc
Description: Message signed with OpenPGP

Re: Regarding releasing Apache Storm 2.0.0

[P. Taylor Goetz]

+1 Sounds good to me.

-Taylor

> On Jul 10, 2018, at 2:18 AM, Jungtaek Lim  wrote:
> 
> Hi devs,
> 
> I hopefully have a time to sort out issues regarding Storm 2.0.0 and link
> to epic issue.
> 
> https://issues.apache.org/jira/browse/STORM-2714
> (require login to Apache JIRA to see issues in epic)
> 
> I guess we are close to the release, mostly left reviewing some pending
> pull requests, and some manual sanity tests.
> 
> Given that master branch is relatively stabilized for Travis CI build, as
> well as style check and Java port make codebase better (at least for me), I
> would really want to make Storm 2.0.0 released sooner than later, and rely
> majorly on 2.x version line.
> 
> So I would propose dev folks to concentrate on remaining tasks for Storm
> 2.0.0 till we announce release. WDYT?
> 
> Thanks,
> Jungtaek Lim (HeartSaVioR)



signature.asc
Description: Message signed with OpenPGP

[CVE-2018-8008] Apache Storm arbitrary file write vulnerability

[P. Taylor Goetz]

CVE-2018-8008: Apache Storm arbitrary file write vulnerability

Severity: Important

Vendor:
The Apache Software Foundation

Versions Affected:
Apache Storm 1.2.1
Apache Storm 1.1.2

Description:
Apache Storm version 1.0.6 and earlier, 1.2.1 and earlier, and version 1.1.2 
and earlier expose an arbitrary file write vulnerability, that can be achieved 
using a specially crafted zip archive (affects other archives as well, bzip2, 
tar, xz, war, cpio, 7z), that holds path traversal filenames. So when the 
filename gets concatenated to the target extraction directory, the final path 
ends up outside of the target folder.

Mitigation:
1.2.1 users should upgrade to version 1.2.2.
1.1.2 users should upgrade to version 1.1.3.
1.0.6 users should upgrade to version 1.1.3.

Apache Storm 1.2.2 artifacts are available for immediate download here:

http://www.us.apache.org/dist/storm/apache-storm-1.2.2/

Apache Storm 1.1.3 artifacts are available for immediate download here:

http://www.us.apache.org/dist/storm/apache-storm-1.1.3/

Credit:
This issue was discovered by Snyk Security Research Team

References:
http://storm.apache.org/2018/06/04/storm122-released.html
http://storm.apache.org/2018/06/04/storm113-released.html

P. Taylor Goetz

[CVE-2018-1332] Apache Storm user impersonation vulnerability

[P. Taylor Goetz]

CVE-2018-1332: Apache Storm user impersonation vulnerability

Severity: Important

Vendor:
The Apache Software Foundation

Versions Affected:
Apache Storm 1.2.1
Apache Storm 1.1.2

Description:
Apache Storm version 1.0.6 and earlier, 1.2.1 and earlier, and version 1.1.2 
and earlier expose a vulnerability that could allow a user to impersonate 
another user when communicating with some Storm Daemons.


Mitigation:
1.2.1 users should upgrade to version 1.2.2.
1.1.2 users should upgrade to version 1.1.3.
1.0.6 users should upgrade to version 1.1.3.

Apache Storm 1.2.2 artifacts are available for immediate download here:

http://www.us.apache.org/dist/storm/apache-storm-1.2.2/

Apache Storm 1.1.3 artifacts are available for immediate download here:

http://www.us.apache.org/dist/storm/apache-storm-1.1.3/

Credit:
This issue was discovered by Bobby Evans of the Apache Storm PMC

References:
http://storm.apache.org/2018/06/04/storm122-released.html
http://storm.apache.org/2018/06/04/storm113-released.html

P. Taylor Goetz

[ANNOUNCE] Apache Storm 1.1.3 Released

[P. Taylor Goetz]

The Apache Storm community is pleased to announce the release of Apache Storm 
version 1.1.3.

Storm is a distributed, fault-tolerant, and high-performance realtime 
computation system that provides strong guarantees on the processing of data. 
You can read more about Storm on the project website:

http://storm.apache.org

Downloads of source and binary distributions are listed in our download
section:

http://storm.apache.org/downloads.html

You can read more about this release in the following blog post:

http://storm.apache.org/2018/02/19/storm121-released.html

Distribution artifacts are available in Maven Central at the following 
coordinates:

groupId: org.apache.storm
artifactId: storm-core
version: 1.1.3

The full list of changes is available here[1]. Please let us know [2] if you 
encounter any problems.

Regards,

The Apache Storm Team

[1]: http://www.us.apache.org/dist/storm/apache-storm-1.1.3/RELEASE_NOTES.html
[2]: https://issues.apache.org/jira/browse/STORM

[ANNOUNCE] Apache Storm 1.2.2 Released

[P. Taylor Goetz]

The Apache Storm community is pleased to announce the release of Apache Storm 
version 1.2.2.

Storm is a distributed, fault-tolerant, and high-performance realtime 
computation system that provides strong guarantees on the processing of data. 
You can read more about Storm on the project website:

http://storm.apache.org

Downloads of source and binary distributions are listed in our download
section:

http://storm.apache.org/downloads.html

You can read more about this release in the following blog post:

http://storm.apache.org/2018/02/19/storm121-released.html

Distribution artifacts are available in Maven Central at the following 
coordinates:

groupId: org.apache.storm
artifactId: storm-core
version: 1.2.2

The full list of changes is available here[1]. Please let us know [2] if you 
encounter any problems.

Regards,

The Apache Storm Team

[1]: http://www.us.apache.org/dist/storm/apache-storm-1.2.2/RELEASE_NOTES.html
[2]: https://issues.apache.org/jira/browse/STORM

[RESULT] [VOTE] Release Apache Storm 1.2.2 (rc3)

[P. Taylor Goetz]

Correcting subject line.

> On May 31, 2018, at 5:02 PM, P. Taylor Goetz  wrote:
> 
> This vote is now closed and passes with 4 binding +1, 1 non-binding +1 votes 
> and no 0 or -1 votes.
> 
> Vote tally (* indicates a binding vote):
> 
> +1
> Juntaek Lim*
> Kishor Patil*
> Ethan Li*
> Bobby Evans*
> Julian Nioche
> 
> 
> I will release the staged artifacts and announce the release in 24 hours.
> 
> -Taylor
> 
>> On May 17, 2018, at 3:59 PM, P. Taylor Goetz  wrote:
>> 
>> This is a call to vote on releasing Apache Storm 1.2.2 (rc3)
>> 
>> Full list of changes in this release:
>> 
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.2-rc3/RELEASE_NOTES.html
>> 
>> The tag/commit to be voted upon is v1.2.2:
>> 
>> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=d29eaa70280dd0ac4b7d393387fab4a91eee9e9d;hb=d2d6f40344e6cc92ab07f3a462d577ef6b61f8b1
>> 
>> The source archive being voted upon can be found here:
>> 
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.2-rc3/apache-storm-1.2.2-src.tar.gz
>> 
>> Other release files, signatures and digests can be found here:
>> 
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.2-rc3/
>> 
>> The release artifacts are signed with the following key:
>> 
>> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
>> 
>> The Nexus staging repository for this release is:
>> 
>> https://repository.apache.org/content/repositories/orgapachestorm-1068
>> 
>> Please vote on releasing this package as Apache Storm 1.2.2.
>> 
>> When voting, please list the actions taken to verify the release.
>> 
>> This vote will be open for 72 hours or until at least 3 PMC members vote +1.
>> 
>> [ ] +1 Release this package as Apache Storm 1.2.2
>> [ ]  0 No opinion
>> [ ] -1 Do not release this package because...
>> 
>> Thanks to everyone who contributed to this release.
>> 
>> -Taylor
> 



signature.asc
Description: Message signed with OpenPGP

[RESULT] [VOTE] Release Apache Storm 1.1.3 (rc2)

[P. Taylor Goetz]

This vote is now closed and passes with 3 binding +1 votes and no 0 or -1 votes.

Vote tally (* indicates a binding vote):

+1
Juntaek Lim*
Kishor Patil*
Ethan Li*


I will release the staged artifacts and announce the release in 24 hours.

-Taylor

> On May 18, 2018, at 3:39 PM, P. Taylor Goetz  wrote:
> 
> This is a call to vote on releasing Apache Storm 1.1.3 (rc2)
> 
> Full list of changes in this release:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.1.3-rc2/RELEASE_NOTES.html
> 
> The tag/commit to be voted upon is v1.1.3:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=e983fef3d4dcd35a821cecb462e198505458d1a4;hb=c51c8fc251856291597a5007a07e433f26951464
> 
> The source archive being voted upon can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.1.3-rc2/apache-storm-1.1.3-src.tar.gz
> 
> Other release files, signatures and digests can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.1.3-rc2/
> 
> The release artifacts are signed with the following key:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
> 
> The Nexus staging repository for this release is:
> 
> https://repository.apache.org/content/repositories/orgapachestorm-1069
> 
> Please vote on releasing this package as Apache Storm 1.1.3.
> 
> When voting, please list the actions taken to verify the release.
> 
> This vote will be open for 72 hours or until at least 3 PMC members vote +1.
> 
> [ ] +1 Release this package as Apache Storm 1.1.3
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
> 
> Thanks to everyone who contributed to this release.
> 
> -Taylor



signature.asc
Description: Message signed with OpenPGP

Re: [VOTE] Release Apache Storm 1.2.2 (rc3)

[P. Taylor Goetz]

This vote is now closed and passes with 4 binding +1, 1 non-binding +1 votes 
and no 0 or -1 votes.

Vote tally (* indicates a binding vote):

+1
Juntaek Lim*
Kishor Patil*
Ethan Li*
Bobby Evans*
Julian Nioche


I will release the staged artifacts and announce the release in 24 hours.

-Taylor

> On May 17, 2018, at 3:59 PM, P. Taylor Goetz  wrote:
> 
> This is a call to vote on releasing Apache Storm 1.2.2 (rc3)
> 
> Full list of changes in this release:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.2-rc3/RELEASE_NOTES.html
> 
> The tag/commit to be voted upon is v1.2.2:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=d29eaa70280dd0ac4b7d393387fab4a91eee9e9d;hb=d2d6f40344e6cc92ab07f3a462d577ef6b61f8b1
> 
> The source archive being voted upon can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.2-rc3/apache-storm-1.2.2-src.tar.gz
> 
> Other release files, signatures and digests can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.2-rc3/
> 
> The release artifacts are signed with the following key:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
> 
> The Nexus staging repository for this release is:
> 
> https://repository.apache.org/content/repositories/orgapachestorm-1068
> 
> Please vote on releasing this package as Apache Storm 1.2.2.
> 
> When voting, please list the actions taken to verify the release.
> 
> This vote will be open for 72 hours or until at least 3 PMC members vote +1.
> 
> [ ] +1 Release this package as Apache Storm 1.2.2
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
> 
> Thanks to everyone who contributed to this release.
> 
> -Taylor



signature.asc
Description: Message signed with OpenPGP

[VOTE] Release Apache Storm 1.1.3 (rc2)

[P. Taylor Goetz]

This is a call to vote on releasing Apache Storm 1.1.3 (rc2)

Full list of changes in this release:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.1.3-rc2/RELEASE_NOTES.html

The tag/commit to be voted upon is v1.1.3:

https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=e983fef3d4dcd35a821cecb462e198505458d1a4;hb=c51c8fc251856291597a5007a07e433f26951464

The source archive being voted upon can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.1.3-rc2/apache-storm-1.1.3-src.tar.gz

Other release files, signatures and digests can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.1.3-rc2/

The release artifacts are signed with the following key:

https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd

The Nexus staging repository for this release is:

https://repository.apache.org/content/repositories/orgapachestorm-1069

Please vote on releasing this package as Apache Storm 1.1.3.

When voting, please list the actions taken to verify the release.

This vote will be open for 72 hours or until at least 3 PMC members vote +1.

[ ] +1 Release this package as Apache Storm 1.1.3
[ ]  0 No opinion
[ ] -1 Do not release this package because...

Thanks to everyone who contributed to this release.

-Taylor


signature.asc
Description: Message signed with OpenPGP

[VOTE] Release Apache Storm 1.2.2 (rc3)

[P. Taylor Goetz]

This is a call to vote on releasing Apache Storm 1.2.2 (rc3)

Full list of changes in this release:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.2-rc3/RELEASE_NOTES.html

The tag/commit to be voted upon is v1.2.2:

https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=d29eaa70280dd0ac4b7d393387fab4a91eee9e9d;hb=d2d6f40344e6cc92ab07f3a462d577ef6b61f8b1

The source archive being voted upon can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.2-rc3/apache-storm-1.2.2-src.tar.gz

Other release files, signatures and digests can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.2-rc3/

The release artifacts are signed with the following key:

https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd

The Nexus staging repository for this release is:

https://repository.apache.org/content/repositories/orgapachestorm-1068

Please vote on releasing this package as Apache Storm 1.2.2.

When voting, please list the actions taken to verify the release.

This vote will be open for 72 hours or until at least 3 PMC members vote +1.

[ ] +1 Release this package as Apache Storm 1.2.2
[ ]  0 No opinion
[ ] -1 Do not release this package because...

Thanks to everyone who contributed to this release.

-Taylor


signature.asc
Description: Message signed with OpenPGP

Re: Updating the website

[P. Taylor Goetz]

Sometimes the gitpubsub process gets stuck. Pushing an empty or white space 
change usually helps.

-Taylor

> On May 12, 2018, at 2:06 PM, Stig Rohde Døssing <stigdoess...@gmail.com> 
> wrote:
> 
> Isn't the site content based on the asf-site branch at
> https://git-wip-us.apache.org/repos/asf?p=storm-site.git;a=
> log;h=refs/heads/asf-site? The site doesn't seem to update after I pushed
> changes. Maybe related(?) the latest commit I pushed seems to have made it
> to the ASF repo, but not to the Github mirror.
> 
> 2018-05-12 17:57 GMT+02:00 Stig Rohde Døssing <stigdoess...@gmail.com>:
> 
>> Will do, thanks.
>> 
>> 2018-05-12 16:00 GMT+02:00 P. Taylor Goetz <ptgo...@gmail.com>:
>> 
>>> Go for it.
>>> 
>>> -Taylor
>>> 
>>>> On May 12, 2018, at 5:45 AM, Stig Rohde Døssing <stigdoess...@gmail.com>
>>> wrote:
>>>> 
>>>> Hi,
>>>> 
>>>> I'd like to update the 2.0.0-SNAPSHOT documentation on the website, it's
>>>> been a while since it was last sync'ed with the docs in the main
>>>> repository. Can I just do this, or does it require a vote? I figure it
>>>> falls under non-code change in the bylaws.
>>> 
>> 
>> 

Re: Updating the website

[P. Taylor Goetz]

Go for it.

-Taylor

> On May 12, 2018, at 5:45 AM, Stig Rohde Døssing  
> wrote:
> 
> Hi,
> 
> I'd like to update the 2.0.0-SNAPSHOT documentation on the website, it's
> been a while since it was last sync'ed with the docs in the main
> repository. Can I just do this, or does it require a vote? I figure it
> falls under non-code change in the bylaws.

Re: [VOTE] Release Apache Storm 1.2.2 (rc2)

[P. Taylor Goetz]

Yes, that would be great. It should be fairly easy since the reporter part of 
the code hasn’t changed.

-Taylor

> On May 7, 2018, at 5:40 PM, Artem Ervits <artemerv...@gmail.com> wrote:
> 
> actually, hit sent too fast, the PR is addressing fix for 1.2.2, I know
> this thread is for 1.2 but do you want a patch for 2.x branch as well?
> 
>> On Mon, May 7, 2018 at 5:39 PM, Artem Ervits <artemerv...@gmail.com> wrote:
>> 
>> Taylor, patch is up https://github.com/apache/storm/pull/2665, please
>> include the PR in the 1.2.2.
>> 
>>> On Mon, May 7, 2018 at 4:41 PM, P. Taylor Goetz <ptgo...@gmail.com> wrote:
>>> 
>>> The build for 1.2.2-rc3 finished just as this arrived in my inbox. ;)
>>> 
>>> I’m happy to include a fix and rebuild the rc. But I won’t have time to
>>> put together a pull request today. It’s an easy fix that can be copied from
>>> one of the other reporters.
>>> 
>>> I’ll hold off on starting the rc3 until we come up with a decision.
>>> 
>>> -Taylor
>>> 
>>>> On May 7, 2018, at 4:18 PM, Priyank Shah <ps...@hortonworks.com> wrote:
>>>> 
>>>> Is it possible to include https://issues.apache.org/jira
>>> /browse/STORM-2988  in 1.2.2 release? Seems like a legit bug and a quick
>>> fix.
>>>> 
>>>> On 5/7/18, 8:45 AM, "P. Taylor Goetz" <ptgo...@gmail.com> wrote:
>>>> 
>>>>   Canceling in order to include STORM-3059 in this release.
>>>> 
>>>>   -Taylor
>>>> 
>>>>> On May 3, 2018, at 11:42 AM, P. Taylor Goetz <ptgo...@gmail.com>
>>> wrote:
>>>>> 
>>>>> This is a call to vote on releasing Apache Storm 1.2.2 (rc2)
>>>>> 
>>>>> Full list of changes in this release:
>>>>> 
>>>>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.
>>> 2.2-rc2/RELEASE_NOTES.html
>>>>> 
>>>>> The tag/commit to be voted upon is v1.2.2:
>>>>> 
>>>>> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h
>>> =7cb19fb3befa65e5ff9e5e02f38e16de865982a9;hb=e001672cf0ea59f
>>> e6989b563fb6bbb450fe8e7e5
>>>>> 
>>>>> The source archive being voted upon can be found here:
>>>>> 
>>>>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.
>>> 2.2-rc2/apache-storm-1.2.2-src.tar.gz
>>>>> 
>>>>> Other release files, signatures and digests can be found here:
>>>>> 
>>>>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.2-rc2/
>>>>> 
>>>>> The release artifacts are signed with the following key:
>>>>> 
>>>>> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_p
>>> lain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
>>>>> 
>>>>> The Nexus staging repository for this release is:
>>>>> 
>>>>> https://repository.apache.org/content/repositories/orgapachestorm-1062
>>>>> 
>>>>> Please vote on releasing this package as Apache Storm 1.2.2.
>>>>> 
>>>>> When voting, please list the actions taken to verify the release.
>>>>> 
>>>>> This vote will be open for 72 hours or until at least 3 PMC members
>>> vote +1.
>>>>> 
>>>>> [ ] +1 Release this package as Apache Storm 1.2.2
>>>>> [ ]  0 No opinion
>>>>> [ ] -1 Do not release this package because...
>>>>> 
>>>>> Thanks to everyone who contributed to this release.
>>>>> 
>>>>> -Taylor
>>>> 
>>>> 
>>>> 
>>> 
>>> 
>> 

Re: [VOTE] Release Apache Storm 1.2.2 (rc2)

[P. Taylor Goetz]

The build for 1.2.2-rc3 finished just as this arrived in my inbox. ;)

I’m happy to include a fix and rebuild the rc. But I won’t have time to put 
together a pull request today. It’s an easy fix that can be copied from one of 
the other reporters.

I’ll hold off on starting the rc3 until we come up with a decision.

-Taylor

> On May 7, 2018, at 4:18 PM, Priyank Shah <ps...@hortonworks.com> wrote:
> 
> Is it possible to include https://issues.apache.org/jira/browse/STORM-2988  
> in 1.2.2 release? Seems like a legit bug and a quick fix.
> 
> On 5/7/18, 8:45 AM, "P. Taylor Goetz" <ptgo...@gmail.com> wrote:
> 
>Canceling in order to include STORM-3059 in this release.
> 
>-Taylor
> 
>> On May 3, 2018, at 11:42 AM, P. Taylor Goetz <ptgo...@gmail.com> wrote:
>> 
>> This is a call to vote on releasing Apache Storm 1.2.2 (rc2)
>> 
>> Full list of changes in this release:
>> 
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.2-rc2/RELEASE_NOTES.html
>> 
>> The tag/commit to be voted upon is v1.2.2:
>> 
>> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=7cb19fb3befa65e5ff9e5e02f38e16de865982a9;hb=e001672cf0ea59fe6989b563fb6bbb450fe8e7e5
>> 
>> The source archive being voted upon can be found here:
>> 
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.2-rc2/apache-storm-1.2.2-src.tar.gz
>> 
>> Other release files, signatures and digests can be found here:
>> 
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.2-rc2/
>> 
>> The release artifacts are signed with the following key:
>> 
>> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
>> 
>> The Nexus staging repository for this release is:
>> 
>> https://repository.apache.org/content/repositories/orgapachestorm-1062
>> 
>> Please vote on releasing this package as Apache Storm 1.2.2.
>> 
>> When voting, please list the actions taken to verify the release.
>> 
>> This vote will be open for 72 hours or until at least 3 PMC members vote +1.
>> 
>> [ ] +1 Release this package as Apache Storm 1.2.2
>> [ ]  0 No opinion
>> [ ] -1 Do not release this package because...
>> 
>> Thanks to everyone who contributed to this release.
>> 
>> -Taylor
> 
> 
> 



signature.asc
Description: Message signed with OpenPGP

Re: [VOTE] Release Apache Storm 1.2.2 (rc2)

[P. Taylor Goetz]

Canceling in order to include STORM-3059 in this release.

-Taylor

> On May 3, 2018, at 11:42 AM, P. Taylor Goetz <ptgo...@gmail.com> wrote:
> 
> This is a call to vote on releasing Apache Storm 1.2.2 (rc2)
> 
> Full list of changes in this release:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.2-rc2/RELEASE_NOTES.html
> 
> The tag/commit to be voted upon is v1.2.2:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=7cb19fb3befa65e5ff9e5e02f38e16de865982a9;hb=e001672cf0ea59fe6989b563fb6bbb450fe8e7e5
> 
> The source archive being voted upon can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.2-rc2/apache-storm-1.2.2-src.tar.gz
> 
> Other release files, signatures and digests can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.2-rc2/
> 
> The release artifacts are signed with the following key:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
> 
> The Nexus staging repository for this release is:
> 
> https://repository.apache.org/content/repositories/orgapachestorm-1062
> 
> Please vote on releasing this package as Apache Storm 1.2.2.
> 
> When voting, please list the actions taken to verify the release.
> 
> This vote will be open for 72 hours or until at least 3 PMC members vote +1.
> 
> [ ] +1 Release this package as Apache Storm 1.2.2
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
> 
> Thanks to everyone who contributed to this release.
> 
> -Taylor



signature.asc
Description: Message signed with OpenPGP

[CANCELED] [VOTE] Release Apache Storm 1.1.3 (rc1)

[P. Taylor Goetz]

Canceling in order to include STORM-3059 in this release.

-Taylor

> On May 3, 2018, at 1:21 PM, P. Taylor Goetz <ptgo...@gmail.com> wrote:
> 
> This is a call to vote on releasing Apache Storm 1.1.3 (rc1)
> 
> Full list of changes in this release:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.1.3-rc1/RELEASE_NOTES.html
> 
> The tag/commit to be voted upon is v1.1.3:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=caffcf810cf28b8b8c7ea6e15a555a7160de1384;hb=e590a3289a9f7b9806a4c5cb78a2c06b4fbf019f
> 
> The source archive being voted upon can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.1.3-rc1/apache-storm-1.1.3-src.tar.gz
> 
> Other release files, signatures and digests can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.1.3-rc1/
> 
> The release artifacts are signed with the following key:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
> 
> The Nexus staging repository for this release is:
> 
> https://repository.apache.org/content/repositories/orgapachestorm-1065
> 
> Please vote on releasing this package as Apache Storm 1.1.3.
> 
> When voting, please list the actions taken to verify the release.
> 
> This vote will be open for 72 hours or until at least 3 PMC members vote +1.
> 
> [ ] +1 Release this package as Apache Storm 1.1.3
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
> 
> Thanks to everyone who contributed to this release.
> 
> -Taylor



signature.asc
Description: Message signed with OpenPGP

[VOTE] Release Apache Storm 1.1.3 (rc1)

[P. Taylor Goetz]

This is a call to vote on releasing Apache Storm 1.1.3 (rc1)

Full list of changes in this release:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.1.3-rc1/RELEASE_NOTES.html

The tag/commit to be voted upon is v1.1.3:

https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=caffcf810cf28b8b8c7ea6e15a555a7160de1384;hb=e590a3289a9f7b9806a4c5cb78a2c06b4fbf019f

The source archive being voted upon can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.1.3-rc1/apache-storm-1.1.3-src.tar.gz

Other release files, signatures and digests can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.1.3-rc1/

The release artifacts are signed with the following key:

https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd

The Nexus staging repository for this release is:

https://repository.apache.org/content/repositories/orgapachestorm-1065

Please vote on releasing this package as Apache Storm 1.1.3.

When voting, please list the actions taken to verify the release.

This vote will be open for 72 hours or until at least 3 PMC members vote +1.

[ ] +1 Release this package as Apache Storm 1.1.3
[ ]  0 No opinion
[ ] -1 Do not release this package because...

Thanks to everyone who contributed to this release.

-Taylor


signature.asc
Description: Message signed with OpenPGP

Re: [VOTE] Release Apache Storm 1.2.2 (rc2)

[P. Taylor Goetz]

CORRECTION: The Nexus staging repository for this rc is:

https://repository.apache.org/content/repositories/orgapachestorm-1064 
<https://repository.apache.org/content/repositories/orgapachestorm-1064>

> On May 3, 2018, at 11:42 AM, P. Taylor Goetz <ptgo...@gmail.com> wrote:
> 
> This is a call to vote on releasing Apache Storm 1.2.2 (rc2)
> 
> Full list of changes in this release:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.2-rc2/RELEASE_NOTES.html
> 
> The tag/commit to be voted upon is v1.2.2:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=7cb19fb3befa65e5ff9e5e02f38e16de865982a9;hb=e001672cf0ea59fe6989b563fb6bbb450fe8e7e5
> 
> The source archive being voted upon can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.2-rc2/apache-storm-1.2.2-src.tar.gz
> 
> Other release files, signatures and digests can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.2-rc2/
> 
> The release artifacts are signed with the following key:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
> 
> The Nexus staging repository for this release is:
> 
> https://repository.apache.org/content/repositories/orgapachestorm-1062
> 
> Please vote on releasing this package as Apache Storm 1.2.2.
> 
> When voting, please list the actions taken to verify the release.
> 
> This vote will be open for 72 hours or until at least 3 PMC members vote +1.
> 
> [ ] +1 Release this package as Apache Storm 1.2.2
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
> 
> Thanks to everyone who contributed to this release.
> 
> -Taylor



signature.asc
Description: Message signed with OpenPGP

[CANCELED] [VOTE] Release Apache Storm 1.2.2(rc1)

[P. Taylor Goetz]

Canceling in order to include the fix for STORM-3309 in this release.

-Taylor

> On May 2, 2018, at 4:29 PM, P. Taylor Goetz <ptgo...@gmail.com> wrote:
> 
> This is a call to vote on releasing Apache Storm 1.2.2 (rc1)
> 
> Full list of changes in this release:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.2-rc1/RELEASE_NOTES.html
> 
> The tag/commit to be voted upon is v1.2.2:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=721e834b1c00db6c6a623fce69dfffed51f437be;hb=bb9c253c9e462bee4f9b9e42867d37ea16219030
> 
> The source archive being voted upon can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.2-rc1/apache-storm-1.2.2-src.tar.gz
> 
> Other release files, signatures and digests can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.2-rc1/
> 
> The release artifacts are signed with the following key:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
> 
> The Nexus staging repository for this release is:
> 
> https://repository.apache.org/content/repositories/orgapachestorm-1062
> 
> Please vote on releasing this package as Apache Storm 1.2.2.
> 
> When voting, please list the actions taken to verify the release.
> 
> This vote will be open for 72 hours or until at least 3 PMC members vote +1.
> 
> [ ] +1 Release this package as Apache Storm 1.2.2
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
> 
> Thanks to everyone who contributed to this release.
> 
> -Taylor



signature.asc
Description: Message signed with OpenPGP

Re: [VOTE] Release Apache Storm 1.2.2(rc1)

[P. Taylor Goetz]

Yes, I will cancel the vote and spin up a new rc.

-Taylor

> On May 3, 2018, at 9:51 AM, Alexandre Vermeerbergen 
> <avermeerber...@gmail.com> wrote:
> 
> Hello,
> 
> Would it be possible to include
> https://issues.apache.org/jira/browse/STORM-3039 in Storm 1.2.2 ?
> 
> Best regards,
> Alexandre Vermeerbergen
> 
> 
> 2018-05-02 22:29 GMT+02:00 P. Taylor Goetz <ptgo...@gmail.com>:
>> This is a call to vote on releasing Apache Storm 1.2.2 (rc1)
>> 
>> Full list of changes in this release:
>> 
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.2-rc1/RELEASE_NOTES.html
>> 
>> The tag/commit to be voted upon is v1.2.2:
>> 
>> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=721e834b1c00db6c6a623fce69dfffed51f437be;hb=bb9c253c9e462bee4f9b9e42867d37ea16219030
>> 
>> The source archive being voted upon can be found here:
>> 
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.2-rc1/apache-storm-1.2.2-src.tar.gz
>> 
>> Other release files, signatures and digests can be found here:
>> 
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.2-rc1/
>> 
>> The release artifacts are signed with the following key:
>> 
>> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
>> 
>> The Nexus staging repository for this release is:
>> 
>> https://repository.apache.org/content/repositories/orgapachestorm-1062
>> 
>> Please vote on releasing this package as Apache Storm 1.2.2.
>> 
>> When voting, please list the actions taken to verify the release.
>> 
>> This vote will be open for 72 hours or until at least 3 PMC members vote +1.
>> 
>> [ ] +1 Release this package as Apache Storm 1.2.2
>> [ ]  0 No opinion
>> [ ] -1 Do not release this package because...
>> 
>> Thanks to everyone who contributed to this release.
>> 
>> -Taylor



signature.asc
Description: Message signed with OpenPGP

[VOTE] Release Apache Storm 1.2.2(rc1)

[P. Taylor Goetz]

This is a call to vote on releasing Apache Storm 1.2.2 (rc1)

Full list of changes in this release:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.2-rc1/RELEASE_NOTES.html

The tag/commit to be voted upon is v1.2.2:

https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=721e834b1c00db6c6a623fce69dfffed51f437be;hb=bb9c253c9e462bee4f9b9e42867d37ea16219030

The source archive being voted upon can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.2-rc1/apache-storm-1.2.2-src.tar.gz

Other release files, signatures and digests can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.2-rc1/

The release artifacts are signed with the following key:

https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd

The Nexus staging repository for this release is:

https://repository.apache.org/content/repositories/orgapachestorm-1062

Please vote on releasing this package as Apache Storm 1.2.2.

When voting, please list the actions taken to verify the release.

This vote will be open for 72 hours or until at least 3 PMC members vote +1.

[ ] +1 Release this package as Apache Storm 1.2.2
[ ]  0 No opinion
[ ] -1 Do not release this package because...

Thanks to everyone who contributed to this release.

-Taylor


signature.asc
Description: Message signed with OpenPGP

Re: New Committer/PMC Member: Ethan Li

[P. Taylor Goetz]

Congratulations! Welcome Ethan!

-Taylor

> On Apr 16, 2018, at 12:23 PM, Bobby Evans  wrote:
> 
> Please Join with me in welcoming Ethan Li as the newest Apache Storm
> committer and PMC member.
> 
> Great work!



signature.asc
Description: Message signed with OpenPGP

Re: Configuration mapping between storm-kafka & storm-kafka-client

[P. Taylor Goetz]

+1 I think that would be helpful for a lot of users.

-Taylor

> On Apr 14, 2018, at 10:46 AM, Stig Rohde Døssing  
> wrote:
> 
> Looks good, left a comment with some feedback. I really like the idea of
> providing a table like this to help users migrate, maybe we could put it in
> the storm-kafka-client documentation?
> 
> 2018-04-14 2:54 GMT+02:00 Srishty Agrawal :
> 
>> Hi,
>> 
>> Is there a document which contains mapping of configurations from
>> storm-kafka SpoutConfig to storm-kafka-client KafkaSpoutConfig? I am
>> working towards migrating Storm-0.9.6 topologies to use Storm-1.0.6.
>> 
>> I have compiled all the information I could find online in this gist
>> ,
>> although I am not sure how correct it is.
>> 
>> Thanks,
>> Srishty Agrawal
>> 

New Committer/PMC Member: Roshan Naik

[P. Taylor Goetz]

Please join me in congratulating and welcoming Roshan Naik as the latest Apache 
Storm committer and PMC member.

Welcome Roshan!

-Taylor

Re: Storm multilang - .net core

[P. Taylor Goetz]

+1 I think that’s a good idea. It would also help to have some wording 
regarding how one requests a project be added to that page.

-Taylor

> On Apr 2, 2018, at 10:03 AM, Stig Rohde Døssing  
> wrote:
> 
> Sorry about necro'ing this thread, but I think this is relevant again, due
> to https://github.com/apache/storm/pull/2613.
> 
> I think it makes more sense to have adapters like this in separate
> repositories from Storm, as they can then release fixes when they need to,
> without being coupled to the Storm release schedule. For example,
> https://github.com/Parsely/streamparse is released this way. Releasing
> separately also makes it easier for users to tell whether the adapter is
> still being actively developed.
> 
> Maybe we should add an "Ecosystem" section to the web page, similar to what
> Kafka has here https://cwiki.apache.org/confluence/display/KAFKA/Ecosystem.
> It would help users find projects related to Storm, which is one of the few
> advantages I can see to adding the adapter to the Storm repo (visibility).
> 
> 2018-02-02 5:23 GMT+01:00 Jungtaek Lim :
> 
>> CORRECTION: I don't work on multilang for now. "had some works" on
>> multilang and introduced small changes on multilang protocol.
>> 
>> 2018년 2월 2일 (금) 오전 9:12, Jungtaek Lim 님이 작성:
>> 
>>> Please remove or bcc. for company mail/mailing list which don't allow
>>> sending mail outside of MS. My previous mail bounced. I just removed CCC
>>> from recipient in current mail.
>>> 
>>> 2018년 2월 2일 (금) 오전 9:08, Jungtaek Lim 님이 작성:
>>> 
 Mauro,
 
 First of all, thanks for proposing contribution of valuable effort on
 Apache Storm! Really appreciated.
 
 I don't know about C#/.net but I have been working on the change of
 multilang, so adding my voice here.
 
 1.
 Major concern from my side for code donation is sustainability. Not sure
 but according to my experience, most of Storm PMCs and contributors
>> don't
 look using Windows at their dev. environment. It doesn't strictly mean
>> they
 don't have experience with C#, but relatively higher chance. I'm sorry
>> to
 the Azure team, but I recently found a forgotten major pull request on
 storm-eventhubs, which doesn't look like no one could review and
>> maintain.
 It might become real pain if we receive the code which we can't/don't
 maintain, hence I'd rather not vote +1 unless at least two PMCs know C#
 well, understand the code completely, and willing to volunteer to
>> maintain.
 
 2.
 As you may know, all of multilang adapters in Storm repo are actually
 close to "example" of implementations. They're just implementations of
>> the
 protocol, and don't provide any language specific optimization as well
>> as
 language-standard code style. Most of Python users in Storm community
>> would
 rather use StreamParse, and it is not uncommon to see StreamParse
>> question
 in user group (whereas they have their own Github repo and issue as
>> well).
 I would like to see adapter (and more) projects really looking
>> attractive
 for other languages as well.
 
 3.
 How it affect releasing Storm? We don't publish them as package in its
 language package environment. If NuGet is one of them, we need to add
>> the
 sequence of release phase for NuGet while releasing Storm, which was not
 happened yet, and will become another pain. Moreover, if it's the case,
>> I
 don't feel needs for having strict coupled between Storm and .net
>> adapter
 package. For user side it's not a "battery-included" and there's no
 difference between maintaining inside/outside. You could freely use
 user/dev list to announce new .net adapter release and such
>> announcements
 are happening from other projects as well.
 
 4.
 It's completely a thought on my own, but I feel more needs of having
>> more
 language-native way of supporting language instead of keep improving
 multilang. (Not meant to discontinue.) We will introduce streams API in
 Storm 2.0.0, a higher-level API like Trident but typed and
>> record-to-record
 processing. We haven't supported Trident in multilang, but I'd like to
>> see
 support streams API in non-JVM language, not only defining protocol, but
 also have it as first-class support (users should be able to construct
 their own topology with only using the language. there's thrift but not
 that convenient.). IMHO, according to Spark's "Lesson learned"
>> (Databricks
 had a poll and published it), I think it's really clear that Python
>> should
 be first (and only, R might be another good to have).
 
 Thanks for reading a wall of text. Regardless of whether we could
>> include
 .net adapter into Storm core or not, thanks again for crafting .net
>> adapter
 and proposing for donation.
 
 

Re: New Metrics Reporting API - for 2.0.0

[P. Taylor Goetz]

It’s currently in progress.

Aaron, if you want to help let me know and we can set up,a feature branch for 
collaboration.

-Taylor

> On Mar 13, 2018, at 4:25 PM, Jungtaek Lim  wrote:
> 
> Aaron,
> 
> please feel free to take up STORM-2908 and STORM-2909 as well. I'd be much
> appreciated. I asked Taylor to take them up but didn't work.
> They're coupled with Storm 2.0.0 release so sooner is better, but no hard
> due date for now.
> 
> -Jungtaek Lim (HeartSaVioR)
> 
> 2018년 3월 14일 (수) 오전 12:35, Aaron Gresch 님이 작성:
> 
>> I was wondering what the plan/timeline is for STORM-2909 for the Storm 2
>> release.
>> 
>> If I can help, please let me know.
>> 
>> Thanks,
>> Aaron
>> 

New Committer/PMC Member: Erik Weathers

[P. Taylor Goetz]

The Apache Storm PMC has voted to add Erik Weathers as a Committer and PMC 
Member.

Please join me in congratulating Erik on his new role!

-Taylor

[ANNOUNCE] Apache Storm 1.2.1 Released

[P. Taylor Goetz]

The Apache Storm community is pleased to announce the release of Apache Storm 
version 1.2.1.

Storm is a distributed, fault-tolerant, and high-performance realtime 
computation system that provides strong guarantees on the processing of data. 
You can read more about Storm on the project website:

http://storm.apache.org

Downloads of source and binary distributions are listed in our download
section:

http://storm.apache.org/downloads.html

You can read more about this release in the following blog post:

http://storm.apache.org/2018/02/19/storm121-released.html

Distribution artifacts are available in Maven Central at the following 
coordinates:

groupId: org.apache.storm
artifactId: storm-core
version: 1.2.1

The full list of changes is available here[1]. Please let us know [2] if you 
encounter any problems.

Regards,

The Apache Storm Team

[1]: http://www.us.apache.org/dist/storm/apache-storm-1.2.1/RELEASE_NOTES.html
[2]: https://issues.apache.org/jira/browse/STORM

[ANNOUNCE] Apache Storm 1.2.1 Released

[P. Taylor Goetz]

The Apache Storm community is pleased to announce the release of Apache Storm 
version 1.2.1.

Storm is a distributed, fault-tolerant, and high-performance realtime 
computation system that provides strong guarantees on the processing of data. 
You can read more about Storm on the project website:

http://storm.apache.org

Downloads of source and binary distributions are listed in our download
section:

http://storm.apache.org/downloads.html

You can read more about this release in the following blog post:

http://storm.apache.org/2018/02/19/storm121-released.html

Distribution artifacts are available in Maven Central at the following 
coordinates:

groupId: org.apache.storm
artifactId: storm-core
version: 1.2.1

The full list of changes is available here[1]. Please let us know [2] if you 
encounter any problems.

Regards,

The Apache Storm Team

[1]: http://www.us.apache.org/dist/storm/apache-storm-1.2.1/RELEASE_NOTES.html
[2]: https://issues.apache.org/jira/browse/STORM

[RESULT] [VOTE] Release Apache Storm 1.2.1 (rc1)

[P. Taylor Goetz]

This VOTE is now closed, and passes with 5 binding +1 votes, and no 0 or -1 
votes.

Vote tally:

+1:
- Hugo Da Cruz Louro
- P. Taylor Goetz
- Jungtaek Lim
- Satish Duggana
- Arun Mahadevan

Thank you to all who took the time to review this release.

I will release the staged artifacts and announce the release after the 24 hour 
waiting period.

-Taylor

> On Feb 16, 2018, at 4:01 PM, P. Taylor Goetz <ptgo...@gmail.com> wrote:
> 
> This is a call to vote on releasing Apache Storm 1.2.1 (rc1)
> 
> NOTE: The primary purpose of this release is to remove an LGPL-licensed 
> binary that was inadvertently included in the 1.2.0 binary release.
> 
> Full list of changes in this release:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.1-rc1/RELEASE_NOTES.html
> 
> The tag/commit to be voted upon is v1.2.1:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=89646c86c667e0a35aed45c8063d777ae1f32b30;hb=d156d25d991311eaa1f5131d3dc34787f87ce684
> 
> The source archive being voted upon can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.1-rc1/apache-storm-1.2.1-src.tar.gz
> 
> Other release files, signatures and digests can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.1-rc1/
> 
> The release artifacts are signed with the following key:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
> 
> The Nexus staging repository for this release is:
> 
> https://repository.apache.org/content/repositories/orgapachestorm-1061
> 
> Please vote on releasing this package as Apache Storm 1.2.1.
> 
> When voting, please list the actions taken to verify the release.
> 
> This vote will be open for 72 hours or until at least 3 PMC members vote +1.
> 
> [ ] +1 Release this package as Apache Storm 1.2.1
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
> 
> Thanks to everyone who contributed to this release.
> 
> -Taylor



signature.asc
Description: Message signed with OpenPGP

Re: [VOTE] Release Apache Storm 1.2.1 (rc1)

[P. Taylor Goetz]

Thank you to all who have voted thus far. Although we have enough PMC +1’s to 
release, I’d like to hold the vote open until at least 24 hours have passed so 
those in other timezones have a chance to weigh in an understand what’s going 
on.

-Taylor

> On Feb 16, 2018, at 7:04 PM, Arun Mahadevan <ar...@apache.org> wrote:
> 
> +1 (binding)
> 
> - Downloaded .zip/.tar.gz and verified md5.
> 
> - Verified the oncrpc jar is not included in the distribution
> 
> - Ran a few sample topologies, checked log viewer.
> 
> - Built the source code from .zip file
> 
> 
> Thanks,
> Arun
> 
> 
> 
> On 2/16/18, 3:27 PM, "Satish Duggana" <satish.dugg...@gmail.com> wrote:
> 
>> +1 (binding)
>> 
>> On Sat, Feb 17, 2018 at 3:03 AM, P. Taylor Goetz <ptgo...@gmail.com> wrote:
>> 
>>> +1 (binding)
>>> 
>>> Verified that the LGPL dependency is no longer included in the binary
>>> distribution.
>>> 
>>> -Taylor
>>> 
>>>> On Feb 16, 2018, at 4:01 PM, P. Taylor Goetz <ptgo...@gmail.com> wrote:
>>>> 
>>>> This is a call to vote on releasing Apache Storm 1.2.1 (rc1)
>>>> 
>>>> NOTE: The primary purpose of this release is to remove an LGPL-licensed
>>> binary that was inadvertently included in the 1.2.0 binary release.
>>>> 
>>>> Full list of changes in this release:
>>>> 
>>>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.
>>> 2.1-rc1/RELEASE_NOTES.html
>>>> 
>>>> The tag/commit to be voted upon is v1.2.1:
>>>> 
>>>> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=
>>> 89646c86c667e0a35aed45c8063d777ae1f32b30;hb=d156d25d991311eaa1f5131d3dc347
>>> 87f87ce684
>>>> 
>>>> The source archive being voted upon can be found here:
>>>> 
>>>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.
>>> 2.1-rc1/apache-storm-1.2.1-src.tar.gz
>>>> 
>>>> Other release files, signatures and digests can be found here:
>>>> 
>>>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.1-rc1/
>>>> 
>>>> The release artifacts are signed with the following key:
>>>> 
>>>> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_
>>> plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
>>>> 
>>>> The Nexus staging repository for this release is:
>>>> 
>>>> https://repository.apache.org/content/repositories/orgapachestorm-1061
>>>> 
>>>> Please vote on releasing this package as Apache Storm 1.2.1.
>>>> 
>>>> When voting, please list the actions taken to verify the release.
>>>> 
>>>> This vote will be open for 72 hours or until at least 3 PMC members vote
>>> +1.
>>>> 
>>>> [ ] +1 Release this package as Apache Storm 1.2.1
>>>> [ ]  0 No opinion
>>>> [ ] -1 Do not release this package because...
>>>> 
>>>> Thanks to everyone who contributed to this release.
>>>> 
>>>> -Taylor
>>> 
>>> 
> 



signature.asc
Description: Message signed with OpenPGP

Re: [VOTE] Release Apache Storm 1.2.1 (rc1)

[P. Taylor Goetz]

+1 (binding)

Verified that the LGPL dependency is no longer included in the binary 
distribution.

-Taylor

> On Feb 16, 2018, at 4:01 PM, P. Taylor Goetz <ptgo...@gmail.com> wrote:
> 
> This is a call to vote on releasing Apache Storm 1.2.1 (rc1)
> 
> NOTE: The primary purpose of this release is to remove an LGPL-licensed 
> binary that was inadvertently included in the 1.2.0 binary release.
> 
> Full list of changes in this release:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.1-rc1/RELEASE_NOTES.html
> 
> The tag/commit to be voted upon is v1.2.1:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=89646c86c667e0a35aed45c8063d777ae1f32b30;hb=d156d25d991311eaa1f5131d3dc34787f87ce684
> 
> The source archive being voted upon can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.1-rc1/apache-storm-1.2.1-src.tar.gz
> 
> Other release files, signatures and digests can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.1-rc1/
> 
> The release artifacts are signed with the following key:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
> 
> The Nexus staging repository for this release is:
> 
> https://repository.apache.org/content/repositories/orgapachestorm-1061
> 
> Please vote on releasing this package as Apache Storm 1.2.1.
> 
> When voting, please list the actions taken to verify the release.
> 
> This vote will be open for 72 hours or until at least 3 PMC members vote +1.
> 
> [ ] +1 Release this package as Apache Storm 1.2.1
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
> 
> Thanks to everyone who contributed to this release.
> 
> -Taylor



signature.asc
Description: Message signed with OpenPGP

[VOTE] Release Apache Storm 1.2.1 (rc1)

[P. Taylor Goetz]

This is a call to vote on releasing Apache Storm 1.2.1 (rc1)

NOTE: The primary purpose of this release is to remove an LGPL-licensed binary 
that was inadvertently included in the 1.2.0 binary release.

Full list of changes in this release:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.1-rc1/RELEASE_NOTES.html

The tag/commit to be voted upon is v1.2.1:

https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=89646c86c667e0a35aed45c8063d777ae1f32b30;hb=d156d25d991311eaa1f5131d3dc34787f87ce684

The source archive being voted upon can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.1-rc1/apache-storm-1.2.1-src.tar.gz

Other release files, signatures and digests can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.1-rc1/

The release artifacts are signed with the following key:

https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd

The Nexus staging repository for this release is:

https://repository.apache.org/content/repositories/orgapachestorm-1061

Please vote on releasing this package as Apache Storm 1.2.1.

When voting, please list the actions taken to verify the release.

This vote will be open for 72 hours or until at least 3 PMC members vote +1.

[ ] +1 Release this package as Apache Storm 1.2.1
[ ]  0 No opinion
[ ] -1 Do not release this package because...

Thanks to everyone who contributed to this release.

-Taylor


signature.asc
Description: Message signed with OpenPGP

Re: [DISCUSS] consider EOL for version lines

[P. Taylor Goetz]

As part of the release process I updated the download page [1] to move older 
releases to archive.a.o as requested by INFRA. I also removed the “Current 
Release” sections for 0.9.x and 0.10.x to make it more clear that those lines 
are no longer supported.

If we want to add a more explicit statement to the download page, we can 
certainly do that as well.

-Taylor

[1] http://storm.apache.org/downloads.html

> On Feb 13, 2018, at 4:45 PM, Jungtaek Lim  wrote:
> 
> We're in discussion to split out storm-kafka-client to have separate
> release version and cycle. Since we have applied necessary changes to
> storm-core of 1.1.x/1.0.x, unless storm-kafka-client needs more changes on
> storm-core, storm-core 1.1.x/1.0.x should be compatible with
> storm-kafka-client be compatible with storm-core 1.x.
> 
> I'm OK to keep the 1.0.x version lines specifically for storm-mesos (and
> then we would end up keeping 1.1.x version line too) if we can't avoid the
> case, but I couldn't guarantee all the bug fixes should be ported back to
> 1.0.x. We even often don't port back the bug fixes to 1.0.x version lines
> when 1.1 is the active minor version of Storm unless the fixes are
> critical. That means we may not port back the bug fixes to 1.1.x after
> announcing 1.2.0 and 1.2.x-branch is cut. As we all know, it greatly
> reduces the maintenance cost. It does make sense for storm-kafka-client to
> do the backport for 1.1.x/1.0.x branches because huge changes are just
> applied (though I guess the experiment described above may resolve such
> issue), but not for others including storm-core except critical/blocker
> issues.
> 
> So in storm-mesos view, it would be better to catch up with highest
> possible version (that's why I hope to adopt storm-mesos in storm repo,
> maybe not likely to happen for now), and I understand storm-mesos can't for
> now because of Storm's issue. I wish the investigation of "Storm on X"
> would occur actively sooner than later, so that it can be included as
> earlier version of Storm 2.x (ideally 2.0.0 but it is just an ideal view).
> 
> Anyway, looks like there is no objection to announce 0.10.x/0.9.x
> explicitly EOL.
> 
> - Jungtaek Lim (HeartSaVioR)
> 
> 2018년 2월 14일 (수) 오전 6:02, Erik Weathers 님이
> 작성:
> 
>> Thanks for keeping storm-mesos in mind Stig. :)  I'd be most worried about
>> any issues we might see with the backported storm-kafka-client and how we
>> *might* need to fix bugs in 1.0.x.  At least it should be easy to
>> cherry-pick fixes back into 1.0.x after the backport-stomping of
>> STORM-2937.
>> 
>> Look forward to working with Bobby to get a long term plan for storm to run
>> on mesos in 2.x+.
>> 
>> - Erik
>> 
>> On Tue, Feb 13, 2018 at 11:26 AM, Stig Rohde Døssing <
>> stigdoess...@gmail.com
>>> wrote:
>> 
>>> +1 to maintain 3 version lines, though we may want to look at what we can
>>> do for storm mesos, which I think it currently stuck on 1.0.x.
>>> 
>>> 2018-02-13 20:17 GMT+01:00 Hugo Da Cruz Louro :
>>> 
 +1 to maintain 3 version lines. Let’s properly announce that in our
>>> portal
 and users list such that users know what’s coming.
 
 Agree with focusing on 2.0 which has a lot of improvements, rather than
 1.x, x >= 3.
 
> On Feb 13, 2018, at 10:43 AM, Alexandre Vermeerbergen <
 avermeerber...@gmail.com> wrote:
> 
> +1 (non binding) to maintaining less version lines, provided that
> 1.2.x branch is maintained long enough to allow progressive adoption
> of 2.x
> 
> Alexandre Vermeerbergen
> 
> 2018-02-13 19:38 GMT+01:00 Priyank Shah :
>> +1 to maintaining 3 version lines as suggested by Jungtaek.
>> 
>> On 2/13/18, 9:51 AM, "Arun Iyer on behalf of Arun Mahadevan" <
 ai...@hortonworks.com on behalf of ar...@apache.org> wrote:
>> 
>>   +1 to maintain 3 version lines.
>> 
>>   I think the next focus should be 2.0.0 than 1.3.0.
>> 
>> 
>> 
>> 
>>   On 2/12/18, 11:40 PM, "Jungtaek Lim"  wrote:
>> 
>>> Hi devs,
>>> 
>>> I've noticed that we are providing 4 different version lines
>> (1.1.x,
 1.0.x,
>>> 0.10.x, 0.9.x) in download page, and I expect we will add one more
>>> for
>>> 1.2.0. Moreover, we have one more develop version line (2.0.0 -
>>> master)
>>> which most of development happens there.
>>> 
>>> Recently we're releasing 3 version lines (1.0.6 / 1.1.2 / 1.2.0)
>>> simultaneously and it took heavy effort to track all the RCs and
 verify all
>>> of them. I guess release manager would take more overhead of
 releasing, and
>>> it doesn't make sense for me if we continue maintaining all of
>> them.
>>> 
>>> Ideally I'd like to propose maintaining three version lines: 2.0.0
 (next
>>> major) / 1.3.0 (next minor - may not happen) / 1.2.1 (next bugfix)
>>> and

[ANNOUNCE] Apache Storm 1.2.0 Released

[P. Taylor Goetz]

The Apache Storm community is pleased to announce the release of Apache Storm 
version 1.2.0.

Storm is a distributed, fault-tolerant, and high-performance realtime 
computation system that provides strong guarantees on the processing of data. 
You can read more about Storm on the project website:

http://storm.apache.org

Downloads of source and binary distributions are listed in our download
section:

http://storm.apache.org/downloads.html

You can read more about this release in the following blog post:

http://storm.apache.org/2018/02/15/storm120-released.html

Distribution artifacts are available in Maven Central at the following 
coordinates:

groupId: org.apache.storm
artifactId: storm-core
version: 1.2.0

The full list of changes is available here[1]. Please let us know [2] if you 
encounter any problems.

Regards,

The Apache Storm Team

[1]: http://www.us.apache.org/dist/storm/apache-storm-1.2.0/RELEASE_NOTES.html
[2]: https://issues.apache.org/jira/browse/STORM

[ANNOUNCE] Apache Storm 1.1.2 Released

[P. Taylor Goetz]

The Apache Storm community is pleased to announce the release of Apache Storm 
version 1.1.2.

Storm is a distributed, fault-tolerant, and high-performance realtime 
computation system that provides strong guarantees on the processing of data. 
You can read more about Storm on the project website:

http://storm.apache.org

Downloads of source and binary distributions are listed in our download
section:

http://storm.apache.org/downloads.html

You can read more about this release in the following blog post:

http://storm.apache.org/2018/02/15/storm112-released.html

Distribution artifacts are available in Maven Central at the following 
coordinates:

groupId: org.apache.storm
artifactId: storm-core
version: 1.1.2

The full list of changes is available here[1]. Please let us know [2] if you 
encounter any problems.

Regards,

The Apache Storm Team

[1]: http://www.us.apache.org/dist/storm/apache-storm-1.1.2/RELEASE_NOTES.html
[2]: https://issues.apache.org/jira/browse/STORM

[ANNOUNCE] Apache Storm 1.0.6 Released

[P. Taylor Goetz]

The Apache Storm community is pleased to announce the release of Apache Storm 
version 1.0.6.

Storm is a distributed, fault-tolerant, and high-performance realtime 
computation system that provides strong guarantees on the processing of data. 
You can read more about Storm on the project website:

http://storm.apache.org

Downloads of source and binary distributions are listed in our download
section:

http://storm.apache.org/downloads.html

You can read more about this release in the following blog post:

http://storm.apache.org/2018/02/14/storm106-released.html

Distribution artifacts are available in Maven Central at the following 
coordinates:

groupId: org.apache.storm
artifactId: storm-core
version: 1.0.5

The full list of changes is available here[1]. Please let us know [2] if you 
encounter any problems.

Regards,

The Apache Storm Team

[1]: http://www.us.apache.org/dist/storm/apache-storm-1.0.6/RELEASE_NOTES.html
[2]: https://issues.apache.org/jira/browse/STORM

Re: [VOTE] Release Apache Storm 1.2.0 (rc4)

[P. Taylor Goetz]

Apologies for the delay in release announcements. I’m working with infra on an 
issue that’s preventing updates to the Storm’s, website.

It looks like the gitpubsub process hung. So while the changes to the website 
are in place, they haven’t been published.

I’m inclined to wait until tomorrow to ask INFRA to what I call “poking 
gitpubsub”, rather than rush it and have a release announcement in the middle 
of the night.

-Taylor

> On Feb 7, 2018, at 5:24 PM, P. Taylor Goetz <ptgo...@gmail.com> wrote:
> 
> This is a call to vote on releasing Apache Storm 1.2.0 (rc4)
> 
> Note that the only difference between rc4 and rc3 is the fix for 
> https://issues.apache.org/jira/browse/STORM-2942 
> <https://issues.apache.org/jira/browse/STORM-2942>.
> 
> Full list of changes in this release:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.0-rc4/RELEASE_NOTES.html
>  
> <https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.0-rc4/RELEASE_NOTES.html>
> 
> The tag/commit to be voted upon is v1.2.0:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=cef4d49e222e53656f38c40d754d4f41799cd9a9;hb=2a0097f9a20b9df494caadb87c87d4e4db01a7ed
>  
> <https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=cef4d49e222e53656f38c40d754d4f41799cd9a9;hb=2a0097f9a20b9df494caadb87c87d4e4db01a7ed>
> 
> The source archive being voted upon can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.0-rc4/apache-storm-1.2.0-src.tar.gz
>  
> <https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.0-rc4/apache-storm-1.2.0-src.tar.gz>
> 
> Other release files, signatures and digests can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.0-rc4/ 
> <https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.0-rc4/>
> 
> The release artifacts are signed with the following key:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
>  
> <https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd>
> 
> The Nexus staging repository for this release is:
> 
> https://repository.apache.org/content/repositories/orgapachestorm-1058 
> <https://repository.apache.org/content/repositories/orgapachestorm-1058>
> 
> Please vote on releasing this package as Apache Storm 1.2.0.
> 
> When voting, please list the actions taken to verify the release.
> 
> This vote will be open for at least 72 hours.
> 
> [ ] +1 Release this package as Apache Storm 1.2.0
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
> 
> Thanks to everyone who contributed to this release.
> 
> -Taylor



signature.asc
Description: Message signed with OpenPGP

Re: [DISCUSS] consider EOL for version lines

[P. Taylor Goetz]

This (3 version lines) is effectively what we’ve been doing — when a new 
version comes out major/minor version comes out, we stop updating/supporting 
the oldest previous version. For example, if we release 2.0 or 1.3 
(hypothetical), we would EOL 1.0.x. In some cases, like a security 
vulnerability, we may revisit an older release, but that’s fairly rare.

I agree that making it more explicit would help users. There’s not much to do 
other than update the downloads page and clean up dist.a.o.

-Taylor

> On Feb 13, 2018, at 4:45 PM, Jungtaek Lim  wrote:
> 
> We're in discussion to split out storm-kafka-client to have separate
> release version and cycle. Since we have applied necessary changes to
> storm-core of 1.1.x/1.0.x, unless storm-kafka-client needs more changes on
> storm-core, storm-core 1.1.x/1.0.x should be compatible with
> storm-kafka-client be compatible with storm-core 1.x.
> 
> I'm OK to keep the 1.0.x version lines specifically for storm-mesos (and
> then we would end up keeping 1.1.x version line too) if we can't avoid the
> case, but I couldn't guarantee all the bug fixes should be ported back to
> 1.0.x. We even often don't port back the bug fixes to 1.0.x version lines
> when 1.1 is the active minor version of Storm unless the fixes are
> critical. That means we may not port back the bug fixes to 1.1.x after
> announcing 1.2.0 and 1.2.x-branch is cut. As we all know, it greatly
> reduces the maintenance cost. It does make sense for storm-kafka-client to
> do the backport for 1.1.x/1.0.x branches because huge changes are just
> applied (though I guess the experiment described above may resolve such
> issue), but not for others including storm-core except critical/blocker
> issues.
> 
> So in storm-mesos view, it would be better to catch up with highest
> possible version (that's why I hope to adopt storm-mesos in storm repo,
> maybe not likely to happen for now), and I understand storm-mesos can't for
> now because of Storm's issue. I wish the investigation of "Storm on X"
> would occur actively sooner than later, so that it can be included as
> earlier version of Storm 2.x (ideally 2.0.0 but it is just an ideal view).
> 
> Anyway, looks like there is no objection to announce 0.10.x/0.9.x
> explicitly EOL.
> 
> - Jungtaek Lim (HeartSaVioR)
> 
> 2018년 2월 14일 (수) 오전 6:02, Erik Weathers 님이
> 작성:
> 
>> Thanks for keeping storm-mesos in mind Stig. :)  I'd be most worried about
>> any issues we might see with the backported storm-kafka-client and how we
>> *might* need to fix bugs in 1.0.x.  At least it should be easy to
>> cherry-pick fixes back into 1.0.x after the backport-stomping of
>> STORM-2937.
>> 
>> Look forward to working with Bobby to get a long term plan for storm to run
>> on mesos in 2.x+.
>> 
>> - Erik
>> 
>> On Tue, Feb 13, 2018 at 11:26 AM, Stig Rohde Døssing <
>> stigdoess...@gmail.com
>>> wrote:
>> 
>>> +1 to maintain 3 version lines, though we may want to look at what we can
>>> do for storm mesos, which I think it currently stuck on 1.0.x.
>>> 
>>> 2018-02-13 20:17 GMT+01:00 Hugo Da Cruz Louro :
>>> 
 +1 to maintain 3 version lines. Let’s properly announce that in our
>>> portal
 and users list such that users know what’s coming.
 
 Agree with focusing on 2.0 which has a lot of improvements, rather than
 1.x, x >= 3.
 
> On Feb 13, 2018, at 10:43 AM, Alexandre Vermeerbergen <
 avermeerber...@gmail.com> wrote:
> 
> +1 (non binding) to maintaining less version lines, provided that
> 1.2.x branch is maintained long enough to allow progressive adoption
> of 2.x
> 
> Alexandre Vermeerbergen
> 
> 2018-02-13 19:38 GMT+01:00 Priyank Shah :
>> +1 to maintaining 3 version lines as suggested by Jungtaek.
>> 
>> On 2/13/18, 9:51 AM, "Arun Iyer on behalf of Arun Mahadevan" <
 ai...@hortonworks.com on behalf of ar...@apache.org> wrote:
>> 
>>   +1 to maintain 3 version lines.
>> 
>>   I think the next focus should be 2.0.0 than 1.3.0.
>> 
>> 
>> 
>> 
>>>   On 2/12/18, 11:40 PM, "Jungtaek Lim"  wrote:
>>> 
>>> Hi devs,
>>> 
>>> I've noticed that we are providing 4 different version lines
>> (1.1.x,
 1.0.x,
>>> 0.10.x, 0.9.x) in download page, and I expect we will add one more
>>> for
>>> 1.2.0. Moreover, we have one more develop version line (2.0.0 -
>>> master)
>>> which most of development happens there.
>>> 
>>> Recently we're releasing 3 version lines (1.0.6 / 1.1.2 / 1.2.0)
>>> simultaneously and it took heavy effort to track all the RCs and
 verify all
>>> of them. I guess release manager would take more overhead of
 releasing, and
>>> it doesn't make sense for me if we continue maintaining all of
>> them.
>>> 
>>> Ideally I'd like to propose maintaining three version lines: 2.0.0

Re: [VOTE] Release Apache Storm 1.0.6 (rc3)

[P. Taylor Goetz]

This vote is now closed and passes with 3 binding +1 votes, and no 0 or -1 
votes.

Vote tally:

+1:
- Bobby Evans
- Jungtaek Lim
- P. Taylor Goetz

I will release the staged artifacts and announce the release after 24 hours.

-Taylor

> On Feb 8, 2018, at 2:22 PM, P. Taylor Goetz <ptgo...@gmail.com> wrote:
> 
> This is a call to vote on releasing Apache Storm 1.0.6 (rc3)
> 
> Full list of changes in this release:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.0.6-rc3/RELEASE_NOTES.html
> 
> The tag/commit to be voted upon is v1.0.6:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=e68365f9f947ddd1794b2edef2149fdfaa1590a2;hb=7993db01580ce62d44866dc00e0a7266984638d0
> 
> The source archive being voted upon can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.0.6-rc3/apache-storm-1.0.6-src.tar.gz
> 
> Other release files, signatures and digests can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.0.6-rc3/
> 
> The release artifacts are signed with the following key:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
> 
> The Nexus staging repository for this release is:
> 
> https://repository.apache.org/content/repositories/orgapachestorm-1060
> 
> Please vote on releasing this package as Apache Storm 1.0.6.
> 
> When voting, please list the actions taken to verify the release.
> 
> This vote will be open for at least 72 hours.
> 
> [ ] +1 Release this package as Apache Storm 1.0.6
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
> 
> Thanks to everyone who contributed to this release.
> 
> -Taylor



signature.asc
Description: Message signed with OpenPGP

[RESULT] [VOTE] Release Apache Storm 1.1.2 (rc3)

[P. Taylor Goetz]

This vote is now closed and passes with 3 binding +1 votes and no -1 or 0 votes.

Vote tally:

+1:
- Bobby Evans
- Jungtaek Lim
- P. Taylor Goetz

I will release the staged artifacts and announce the release after 24 hours.

-Taylor

> On Feb 8, 2018, at 12:48 PM, P. Taylor Goetz <ptgo...@gmail.com> wrote:
> 
> This is a call to vote on releasing Apache Storm 1.1.2 (rc3)
> 
> Full list of changes in this release:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.1.2-rc3/RELEASE_NOTES.html
> 
> The tag/commit to be voted upon is v1.1.2:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=3aab00d053d3576d3f8a37bcc3c7e51072ead22e;hb=0bb7a66a9b26ad96afc81b27dd45f93ae8969c44
> 
> The source archive being voted upon can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.1.2-rc3/apache-storm-1.1.2-src.tar.gz
> 
> Other release files, signatures and digests can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.1.2-rc3/
> 
> The release artifacts are signed with the following key:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
> 
> The Nexus staging repository for this release is:
> 
> https://repository.apache.org/content/repositories/orgapachestorm-1059
> 
> Please vote on releasing this package as Apache Storm 1.1.2.
> 
> When voting, please list the actions taken to verify the release.
> 
> This vote will be open for at least 72 hours.
> 
> [ ] +1 Release this package as Apache Storm 1.1.2
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
> 
> Thanks to everyone who contributed to this release.
> 
> -Taylor



signature.asc
Description: Message signed with OpenPGP

Re: [VOTE] Release Apache Storm 1.1.2 (rc3)

[P. Taylor Goetz]

+1 (binding)

-Taylor

> On Feb 8, 2018, at 12:48 PM, P. Taylor Goetz <ptgo...@gmail.com> wrote:
> 
> This is a call to vote on releasing Apache Storm 1.1.2 (rc3)
> 
> Full list of changes in this release:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.1.2-rc3/RELEASE_NOTES.html
> 
> The tag/commit to be voted upon is v1.1.2:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=3aab00d053d3576d3f8a37bcc3c7e51072ead22e;hb=0bb7a66a9b26ad96afc81b27dd45f93ae8969c44
> 
> The source archive being voted upon can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.1.2-rc3/apache-storm-1.1.2-src.tar.gz
> 
> Other release files, signatures and digests can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.1.2-rc3/
> 
> The release artifacts are signed with the following key:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
> 
> The Nexus staging repository for this release is:
> 
> https://repository.apache.org/content/repositories/orgapachestorm-1059
> 
> Please vote on releasing this package as Apache Storm 1.1.2.
> 
> When voting, please list the actions taken to verify the release.
> 
> This vote will be open for at least 72 hours.
> 
> [ ] +1 Release this package as Apache Storm 1.1.2
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
> 
> Thanks to everyone who contributed to this release.
> 
> -Taylor



signature.asc
Description: Message signed with OpenPGP

Re: [VOTE] Release Apache Storm 1.0.6 (rc3)

[P. Taylor Goetz]

+1 (binding)

-Taylor

> On Feb 8, 2018, at 2:22 PM, P. Taylor Goetz <ptgo...@gmail.com> wrote:
> 
> This is a call to vote on releasing Apache Storm 1.0.6 (rc3)
> 
> Full list of changes in this release:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.0.6-rc3/RELEASE_NOTES.html
> 
> The tag/commit to be voted upon is v1.0.6:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=e68365f9f947ddd1794b2edef2149fdfaa1590a2;hb=7993db01580ce62d44866dc00e0a7266984638d0
> 
> The source archive being voted upon can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.0.6-rc3/apache-storm-1.0.6-src.tar.gz
> 
> Other release files, signatures and digests can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.0.6-rc3/
> 
> The release artifacts are signed with the following key:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
> 
> The Nexus staging repository for this release is:
> 
> https://repository.apache.org/content/repositories/orgapachestorm-1060
> 
> Please vote on releasing this package as Apache Storm 1.0.6.
> 
> When voting, please list the actions taken to verify the release.
> 
> This vote will be open for at least 72 hours.
> 
> [ ] +1 Release this package as Apache Storm 1.0.6
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
> 
> Thanks to everyone who contributed to this release.
> 
> -Taylor



signature.asc
Description: Message signed with OpenPGP

[RESULT] [VOTE] Release Apache Storm 1.2.0 (rc4)

[P. Taylor Goetz]

This vote is now closed and passes with 4 binding +1 votes, 1 non-binding +1, 
and no 0 or -1 votes.

Vote tally (* indicates a binding vote):

+1:
- Jungtaek Lim*
- Satish Duggana*
- Arun Iyer*
- Alexandre Vermeerbergen
- Bobby Evans*

I will release the staged artifacts and announce the release after the 24 hour 
waiting period.

-Taylor

> On Feb 7, 2018, at 5:24 PM, P. Taylor Goetz <ptgo...@gmail.com> wrote:
> 
> This is a call to vote on releasing Apache Storm 1.2.0 (rc4)
> 
> Note that the only difference between rc4 and rc3 is the fix for 
> https://issues.apache.org/jira/browse/STORM-2942 
> <https://issues.apache.org/jira/browse/STORM-2942>.
> 
> Full list of changes in this release:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.0-rc4/RELEASE_NOTES.html
>  
> <https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.0-rc4/RELEASE_NOTES.html>
> 
> The tag/commit to be voted upon is v1.2.0:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=cef4d49e222e53656f38c40d754d4f41799cd9a9;hb=2a0097f9a20b9df494caadb87c87d4e4db01a7ed
>  
> <https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=cef4d49e222e53656f38c40d754d4f41799cd9a9;hb=2a0097f9a20b9df494caadb87c87d4e4db01a7ed>
> 
> The source archive being voted upon can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.0-rc4/apache-storm-1.2.0-src.tar.gz
>  
> <https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.0-rc4/apache-storm-1.2.0-src.tar.gz>
> 
> Other release files, signatures and digests can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.0-rc4/ 
> <https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.0-rc4/>
> 
> The release artifacts are signed with the following key:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
>  
> <https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd>
> 
> The Nexus staging repository for this release is:
> 
> https://repository.apache.org/content/repositories/orgapachestorm-1058 
> <https://repository.apache.org/content/repositories/orgapachestorm-1058>
> 
> Please vote on releasing this package as Apache Storm 1.2.0.
> 
> When voting, please list the actions taken to verify the release.
> 
> This vote will be open for at least 72 hours.
> 
> [ ] +1 Release this package as Apache Storm 1.2.0
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
> 
> Thanks to everyone who contributed to this release.
> 
> -Taylor



signature.asc
Description: Message signed with OpenPGP

Re: [VOTE] Release Apache Storm 1.0.6 (rc3)

[P. Taylor Goetz]

Doh! I didn’t even think consider that it was likely autogenerated by an IDE 
and likely identical to what the JDK would generate.

I agree with Bobby, let’s leave it there and continue with the RC.

Thanks for pointing that out Bobby.

-Taylor

> On Feb 9, 2018, at 4:07 PM, Bobby Evans <ev...@oath.com.INVALID> wrote:
> 
> Actually it is set properly.  Do NOT change it.  It works just fine the way
> it is.
> 
> $ git checkout f6f35dd98d2492a38aa4d61da7f6caee4ec2f31a # The git version
> right before this change on branch-1.x
> $ mvn clean install -DskipTests
> $ serialver -classpath ./storm-core/target/storm-core-1.1.0-SNAPSHOT.jar
> org.apache.storm.tuple.Fields
> org.apache.storm.tuple.Fields:private static final long
> serialVersionUID = -3377931843059975424L;
> 
> This is the same version that we set it to as a part of the change.
> 
> - Bobby
> 
> On Fri, Feb 9, 2018 at 3:00 PM Bobby Evans <ev...@oath.com> wrote:
> 
>> Fields changing will cause problems if it is serialized as part of a
>> bolt/spout or as part of a custom grouping.  I have not checked explicitly,
>> but removing that line is the wrong thing to do.  By default the 
>> serialVersionUID
>> is generated from the class itself, so removing it, but leaving in the
>> modified code would still break backwards compatibility.
>> 
>> I'll take a look and see what you need to set it to so you don't break
>> backwards compatibility on 1.x
>> 
>> On Fri, Feb 9, 2018 at 10:19 AM P. Taylor Goetz <ptgo...@gmail.com> wrote:
>> 
>>> What are others’ opinions on removing the serialversionUid an moving
>>> ahead with an RC4?
>>> 
>>> -Taylor
>>> 
>>>> On Feb 9, 2018, at 7:21 AM, Jungtaek Lim <kabh...@gmail.com> wrote:
>>>> 
>>>> I just went ahead verifying current RC except serialization UID issue in
>>>> Fields. I could also vote for RC4 immediately if necessary.
>>>> 
>>>> +1 (binding)
>>>> 
>>>>> source
>>>> 
>>>> - verify file (signature, MD5, SHA)
>>>> -- source, tar.gz : OK
>>>> -- source, zip : OK
>>>> 
>>>> - extract file
>>>> -- source, tar.gz : OK
>>>> -- source, zip : OK
>>>> 
>>>> - diff-ing extracted files between tar.gz and zip : OK
>>>> 
>>>> - build source with JDK 7
>>>> -- source, tar.gz : OK
>>>> 
>>>> - build source dist
>>>> -- source, tar.gz : OK
>>>> 
>>>> - build binary dist
>>>> -- source, tar.gz : OK
>>>> 
>>>>> binary
>>>> 
>>>> - verify file (signature, MD5, SHA)
>>>> -- binary, tar.gz : OK
>>>> -- binary, zip : OK
>>>> 
>>>> - extract file
>>>> -- binary, tar.gz : OK
>>>> -- binary, zip : OK
>>>> 
>>>> - diff-ing extracted files between tar.gz and zip : OK
>>>> 
>>>> - launch daemons : OK
>>>> 
>>>> - run RollingTopWords (local) : OK
>>>> 
>>>> - run RollingTopWords (remote) : OK
>>>> - activate / deactivate / rebalance / kill : OK
>>>> - logviewer (worker dir, daemon dir) : OK
>>>> - change log level : OK
>>>> - thread dump, heap dump, restart worker : OK
>>>> - log search : OK
>>>> 
>>>> Thanks,
>>>> Jungtaek Lim (HeartSaVioR)
>>>> 
>>>> 2018년 2월 9일 (금) 오후 6:18, Erik Weathers <eweath...@groupon.com.invalid>님이
>>> 작성:
>>>> 
>>>>> I'm fine submitting a PR to back that line out (or any of you committer
>>>>> folks could just rip it out).
>>>>> 
>>>>> But I'd like to understand Storm a bit better as part of making this
>>>>> decision. :-)  Am I correct in assuming it would only be a problem if
>>> the
>>>>> serialized Fields were stored somewhere (e.g., ZooKeeper, local
>>> filesystem)
>>>>> and then read back in after the Nimbus/Workers are brought back up
>>> after
>>>>> the upgrade?  Seems Fields is used in a *lot* of places, and I don't
>>> know
>>>>> precisely what is serialized for reused upon Storm Nimbus/Worker daemon
>>>>> restarts.  I believe there are examples of Fields being used to create
>>>>> Spout or Bolt objects that are used to create the StormTopology object,
>>>>> which I believe is serialized into ZooKeeper.  But