Re: Release Planning for 1.1.1 and others?

Those some of the one’s I’ve been tracking for 1.1.1. I’ll do another run through JIRA to see if there’s anything else pending that needs to be included. I would encourage others to do so as well. -Taylor > On Jul 18, 2017, at 2:27 PM, Hugo Da Cruz Louro > wrote: >

Re: Release Planning for 1.1.1 and others?

Hi Jungtaek, Currently there are 2 critical bugs and no blocker bugs. https://issues.apache.org/jira/browse/STORM-2342- I still need to investigate it. It may or may not be a bug. It is a bit surprising that such basic functionality is not working.

Re: Release Planning for 1.1.1 and others?

I think a month seems realistic, yes. Thanks for clarifying when it is okay to skip the waiting period. 2017-07-18 13:44 GMT+02:00 Jungtaek Lim : > Thanks for following up Stig. > > According to your explanation, only a few issues are left for bug fix. I > feel they could be

Re: Release Planning for 1.1.1 and others?

Thanks for following up Stig. According to your explanation, only a few issues are left for bug fix. I feel they could be resolved around a month, and then we can track them as epic issue from now on, and release once they're resolved. Make sense? Btw, if my understanding is right, you don't

Re: Release Planning for 1.1.1 and others?

Hi Jungtaek, I think we're not too far off for most of the issues I'm aware of. I'd like to get some fixes around topic compaction ( https://github.com/apache/storm/pull/2221 and https://github.com/apache/storm/pull/2217) in for 1.1.1. They should be mergeable once the 24 hour period has passed.

Release Planning for 1.1.1 and others?

Hi devs, We released Storm 1.1.0 at the late March, and we didn't have short plan for next release. (We discussed Storm 2.0.0, and I think we're getting closer, a bit slowly but steady.) While we still have some issues and pull requests for storm-kafka-client which I think should be included to