I don’t think we need a formal vote for the plan, since there appears to be 
consensus among all those involved (i.e. no one on the PMC or dev@ list has 
expressed a negative opinion). That being said, I’m +1.

Thank you Bobby for doing all the JIRA work to make sure everything gets 
tracked.

As far as starting some of the migration work now, I think that’s okay, but any 
corresponding pull requests will have to wait until the 1.x branch is created. 
I’d rather the short term focus be on getting 1.0 out the door before we jump 
too far into the merge work.

-Taylor


> On Nov 23, 2015, at 4:40 PM, Bobby Evans <[email protected]> wrote:
> 
> Sorry for spaming everyone with all the JIRA creations today.  I have filed 
> all of the JIRA corresponding to the plan for JStorm merger listed here.
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61328109
> The bylaws 
> https://github.com/apache/storm/blob/master/docs/documentation/BYLAWS.md 
> don't cover a vote on the direction of the project like this.  They cover the 
> merger of each pull request that would be made, but not a direction change. 
> As such this vote is more symbolic than anything, and I would love to hear 
> from everyone involved.
> 
> The current plan is to finish merging in features for a 1.0 release.
> 
> https://cwiki.apache.org/confluence/display/STORM/Storm+Release+1.0
> is supposed to cover this, but I think it is missing some features others 
> want, so please let us know if you really want to get your feature in before 
> this happens.  As such the time frame is a bit flexible but I would like to 
> shoot for doing a storm-1.0 release before mid December.
> After that we would begin merging in the clojure->java transition JIRA.  Once 
> those are complete the feature freeze would be lifted and JStorm features 
> would be merged in along with other features.  Hopefully we would have a 
> Storm 2.0 release by mid February to mid March, depending on how things go.
> 
> I am +1 on this plan (if you couldn't tell)
>  - Bobby

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

Reply via email to