Re: [DISCUSS] 1.0 Release/Clojure-Java Migration

: <dev@storm.apache.org<mailto:dev@storm.apache.org>> Subject: [DISCUSS] 1.0 Release/Clojure-Java Migration I think the 1.x-branch has stabilized enough that it's safe to allow the master branch diverge in support of the JStorm merge. There's a lot of good work going on with the

Re: [DISCUSS] 1.0 Release/Clojure-Java Migration

lto:ptgo...@gmail.com>> > Reply-To: <dev@storm.apache.org<mailto:dev@storm.apache.org>> > Date: Monday, February 1, 2016 at 7:23 PM > To: <dev@storm.apache.org<mailto:dev@storm.apache.org>> > Subject: [DISCUSS] 1.0 Release/Clojure-Java Migration > > I think t

Re: [DISCUSS] 1.0 Release/Clojure-Java Migration

I agree that it has stabilized a lot recently. Taylor, in the past you have been the one that has done most of the release work.  I am fine with letting you continue that for the 1.x line if you like, or I am happy to do some of that too if you would rather off load it.  Please let me know

Re: [DISCUSS] 1.0 Release/Clojure-Java Migration

Is it possible to make the type as Epic so that remaining filed issues can be directly linked? e.g. https://issues.apache.org/jira/browse/STORM-1455 On Tue, Feb 2, 2016 at 6:53 AM, P. Taylor Goetz wrote: > I think the 1.x-branch has stabilized enough that it’s safe to allow

Re: [DISCUSS] 1.0 Release/Clojure-Java Migration

Thanks Bobby. I don’t mind doing the release prep and testing. It seems like i’ve been focused on that while you’ve had more time to forge ahead with the JStorm migration, which feels like a natural way for us to divide and conquer. So far that seems to be working out well. -Taylor > On Feb

Re: [DISCUSS] 1.0 Release/Clojure-Java Migration

Done. Thanks for the suggestion. -Taylor > On Feb 2, 2016, at 5:11 AM, Abhishek Agarwal wrote: > > Is it possible to make the type as Epic so that remaining filed issues can > be directly linked? > e.g. https://issues.apache.org/jira/browse/STORM-1455 > > On Tue, Feb 2,