+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
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
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
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/2806
---
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/2822
---
Github user milantracy commented on the issue:
https://github.com/apache/storm/pull/2822
@revans2 ty :)
---
Github user jacobtolar commented on the issue:
https://github.com/apache/storm/pull/2806
rebased to latest master and squashed into one commit
---
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/2821
---
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
