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
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
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
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
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
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
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.
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
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 deliver a decent perf boost and energy savings.
One thing I am hoping we can address before releasing Storm 2 is... to fix the
naming of the
STORM-3217 and STORM-3221 have been fixed - +1 from me for 2.0 RC.
On Wed, Sep 12, 2018 at 10:01 AM Govind Menon wrote:
> Hi all,
>
> There are some regressions that I introduced as part of STORM-1311 which
> I'm working on as part of https://issues.apache.org/jira/browse/STORM-3217
> and
Hi all,
There are some regressions that I introduced as part of STORM-1311 which
I'm working on as part of https://issues.apache.org/jira/browse/STORM-3217
and https://issues.apache.org/jira/browse/STORM-3221. These should be fixed
before a 2.x release
I have code working on the Yahoo internal
+1 for releasing 2.0.
May be the RC can be cut once critical patches are merged.
On Tue, 11 Sep 2018 at 10:28, Stig Rohde Døssing
wrote:
> +1 to cut an RC.
>
> Here are a couple of PRs that could maybe go in
>
> https://github.com/apache/storm/pull/2719
>
+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
+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
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
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)
+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:
>>>
+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.
>>
>>
+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
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
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
23 matches
Mail list logo
