+1 Add two comments.(1) For some big feature of JStorm, such as
metrics/monitor/scheduler/executors, we need to do some preparation in phase 1.
Otherwise it will bring a lot of redo works.(2) Later, I will sort the wiki
job list, we can do some easier job which doesn't need discuss or need a little
discussion firstly, then start to harder
job.RegardsLongda------------------------------------------------------------------From:Bobby
Evans <[email protected]>Send Time:2015年11月24日(星期二) 05:43To:Dev
<[email protected]>Subject:[VOTE] Storm 2.0 planSorry 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=61328109The
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.0is
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
