+1

-----邮件原件-----
发件人: Cody Innowhere [mailto:[email protected]] 
发送时间: 2015年11月24日 17:41
收件人: [email protected]
抄送: Bobby Evans
主题: Re: [VOTE] Storm 2.0 plan

+1 for this plan.

Also +1 for starting evaluation solutions of major feature differences
early before starting migration to avoid unnecessary re-work.

On Tue, Nov 24, 2015 at 3:26 PM, 刘键(Basti Liu) <[email protected]>
wrote:

> +1 for this plan.
>
> @Taylor
> Could you help to update the reference branch "jstorm-import" with latest
> JStorm version(2.1.0), since some JStorm features
> listed in the plan of phase 2 are not included? Thanks.
>
> @Bobby and the devs who are interested in this migration
> We will try to add some design documents for the features related to
> "JStorm evaluate/port" JIAR of phase 2 by the end of week.
> If the JIRA might cause much rework during phase 2, we will also comment
> the solution on relative JIRA of phase 1. Hope we can
> have an evaluation together before starting migration, to avoid some
> unnecessary rework.
> If any comments for "JStorm" part, please feel free to tell us.
>
> Regards
> Basti
>
> -----Original Message-----
> From: Bobby Evans [mailto:[email protected]]
> Sent: Tuesday, November 24, 2015 5:40 AM
> To: Dev
> Subject: [VOTE] Storm 2.0 plan
>
> 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
>
>

Reply via email to