i
> >>
> >> -----Original Message-----
> >> From: P. Taylor Goetz [mailto:ptgo...@gmail.com]
> >> Sent: Thursday, November 19, 2015 6:24 AM
> >> To: dev@storm.apache.org; Bobby Evans
> >> Subject: Re: [DISCUSS] Plan for Merging JStorm Code
> >>
Hi Taylor,
I'd like to help too, could you add me in? my id is: hustfxj
-邮件原件-
发件人: P. Taylor Goetz [mailto:ptgo...@gmail.com]
发送时间: 2015年11月24日 23:54
收件人: dev@storm.apache.org
主题: Re: [DISCUSS] Plan for Merging JStorm Code
Hi Cody,
I wasn’t able to find your username. Are you sur
gt; -Original Message-
>> From: P. Taylor Goetz [mailto:ptgo...@gmail.com]
>> Sent: Thursday, November 19, 2015 6:24 AM
>> To: dev@storm.apache.org; Bobby Evans
>> Subject: Re: [DISCUSS] Plan for Merging JStorm Code
>>
>> All I have at this point is a pl
erName: basti.lj
>
> Regards
> Basti
>
> -Original Message-
> From: P. Taylor Goetz [mailto:ptgo...@gmail.com]
> Sent: Thursday, November 19, 2015 6:24 AM
> To: dev@storm.apache.org; Bobby Evans
> Subject: Re: [DISCUSS] Plan for Merging JStorm Code
>
> All I hav
: dev@storm.apache.org; Bobby Evans
Subject: Re: [DISCUSS] Plan for Merging JStorm Code
All I have at this point is a placeholder wiki entry [1], and a lot of local
notes that likely would only make sense to me.
Let me know your wiki username and I’ll give you permissions. The same goes for
anyone else who
From:Bobby
> Evans Send Time:2015年11月20日(星期五) 06:54To:P.
> Taylor Goetz ，dev@storm.apache.org
> Subject:Re: [DISCUSS] Plan for Merging JStorm Code
> Sorry about this taking so long. I am revans2 on the cwiki. - Bobby
>
>
> On Wednesday, November 18, 2015 4:
@Taylor, I want to work with Bobby, my wiki name is "longda".
ThanksLongda--From:Bobby
Evans Send Time:2015年11月20日(星期五) 06:54To:P.
Taylor Goetz ，dev@storm.apache.org
Subject:Re: [DISCUSS] Plan for Merging JStorm Code
S
;> The release planned to be release after Nov 11th has already run online
>> stably several month in Alibaba.
>>
>> Besides this, there are many valuable internal requirements in Alibaba, the
>> fast evolution of JStorm is forseeable in next few months.
>>
>
to make it stable. Of course, we have many devs in
>> community to make the porting job faster. But it still needs a long time to
>> run many online complex topologys to find bugs and fix them. So, that is the
>> reason why I proposed to do merging and build on a stable &quo
in
> community to make the porting job faster. But it still needs a long time to
> run many online complex topologys to find bugs and fix them. So, that is the
> reason why I proposed to do merging and build on a stable "java core".
>
> -----Original Message-
>
t; community to make the porting job faster. But it still needs a long time to
> run many online complex topologys to find bugs and fix them. So, that is the
> reason why I proposed to do merging and build on a stable "java core".
>
> -----Original Message-
> From:
to do merging and build on a stable "java core".
-Original Message-
From: Bobby Evans [mailto:ev...@yahoo-inc.com.INVALID]
Sent: Wednesday, November 11, 2015 10:51 PM
To: dev@storm.apache.org
Subject: Re: [DISCUSS] Plan for Merging JStorm Code
+1 for doing a 1.0 relea
ugs and fix them. So, that is the reason
why I proposed to do merging and build on a stable "java core".
-Original Message-
From: Bobby Evans [mailto:ev...@yahoo-inc.com.INVALID]
Sent: Wednesday, November 11, 2015 10:51 PM
To: dev@storm.apache.org
Subject: Re: [DISCUSS] Plan for
> On Nov 11, 2015, at 2:04 AM, Cody Innowhere wrote:
>
>> During migration, it's probably easiest to operate with two local clones
> of the Apache Storm repo: one for working (i.e. checked out to working
> branch) > and one for reference/copying (i.e. checked out to
> "jstorm-import").
> Do you
ebase
Agree 100% this is important.
--
Derek
- Original Message -
From: Bobby Evans
To: "dev@storm.apache.org"
Cc:
Sent: Wednesday, November 11, 2015 8:51 AM
Subject: Re: [DISCUSS] Plan for Merging JStorm Code
+1 for doing a 1.0 release based off of the clojure 0.11.x co
” basing on JStorm for the “java core”.
Please correct me, if any misunderstanding.
Regards
Basti
发件人: P. Taylor Goetz [mailto:ptgo...@gmail.com]
发送时间: 2015年11月11日 5:32
收件人: dev@storm.apache.org
主题: [DISCUSS] Plan for Merging JStorm Code
Based on a number of discussions regarding merging t
me, if any misunderstanding.
>
>
>
> Regards
>
> Basti
>
>
>
> 发件人: P. Taylor Goetz [mailto:ptgo...@gmail.com]
> 发送时间: 2015年11月11日 5:32
> 收件人: dev@storm.apache.org
> 主题: [DISCUSS] Plan for Merging JStorm Code
>
>
>
> Based on a number of discussions
f any misunderstanding.
Regards
Basti
发件人: P. Taylor Goetz [mailto:ptgo...@gmail.com]
发送时间: 2015年11月11日 5:32
收件人: dev@storm.apache.org
主题: [DISCUSS] Plan for Merging JStorm Code
Based on a number of discussions regarding merging the JStorm code, I’ve tried
to distill the ideas presented and ins
any misunderstanding.
Regards
Basti
发件人: P. Taylor Goetz [mailto:ptgo...@gmail.com]
发送时间: 2015年11月11日 5:32
收件人: dev@storm.apache.org
主题: [DISCUSS] Plan for Merging JStorm Code
Based on a number of discussions regarding merging the JStorm code, I’ve tried
to distill the ideas presented
sure, I can do the
performance test, do we have any
performance test cases
?--发件人：Cody
Innowhere 发送时间：2015年11月11日(星期三) 15:04收件人：dev
主 题：Re: [DISCUSS] Plan for Merging JStorm Code
Thanks Taylor.
The plan looks good.
> Dur
Thanks Taylor.
The plan looks good.
> During migration, it's probably easiest to operate with two local clones
of the Apache Storm repo: one for working (i.e. checked out to working
branch) > and one for reference/copying (i.e. checked out to
"jstorm-import").
Do you mean two storm branches(both
+1 for 1.0.0 release.
I also like Hackathon to encourage bigger participation. It will be fun.
On 11/10/15, 3:38 PM, "Harsha" wrote:
>Thanks Taylor for putting together plan on merging JStorm code.
>Few things
>
>1. we should call 0.11.0 as 1.0.0 release since storm has security and
> nimbus
Thanks Taylor for putting together plan on merging JStorm code.
Few things
1. we should call 0.11.0 as 1.0.0 release since storm has security and
nimbus ha . Quite a lot of features and improvements added this is
going to be big release and its about time we call 1.0.0
1.1 "align package na
Based on a number of discussions regarding merging the JStorm code, I’ve tried
to distill the ideas presented and inserted some of my own. The result is below.
I’ve divided the plan into three phases, though they are not necessarily
sequential — obviously some tasks can take place in parallel.
24 matches
Mail list logo
