Sounds good to me. The list in JIRA also looks fine to me. It might make sense to get https://github.com/apache/storm/pull/2443 in before doing https://issues.apache.org/jira/browse/STORM-2972, so the first might effectively block removing storm-kafka.
I think even if we can't remove everything listed in https://issues.apache.org/jira/browse/STORM-2947, it would be good to delete as much as possible before releasing 2.0.0. I might take a look at it soon, unless you're already working on it. 2018-07-10 8:18 GMT+02:00 Jungtaek Lim <kabh...@gmail.com>: > 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) >
