Re: Roadmap for 0.8.0

, 2017 at 11:29 AM, Felix Cheung <felixcheun...@hotmail.com >> > wrote: >> >> +1 with latest/stable. >> >> >> >> >> -- >> *From:* moon soo Lee <m...@apache.org> >> *Sent:* Tuesday, March 21, 2017 8:4

Re: Roadmap for 0.8.0

gt; Ruslan Dautkhanov > > On Wed, Mar 22, 2017 at 11:29 AM, Felix Cheung <felixcheun...@hotmail.com> > wrote: > > +1 with latest/stable. > > > > > -- > *From:* moon soo Lee <m...@apache.org> > *Sent:* Tuesday, March 21, 2017

Re: Roadmap for 0.8.0

2017 at 11:29 AM, Felix Cheung <felixcheun...@hotmail.com> wrote: > +1 with latest/stable. > > > > > -- > *From:* moon soo Lee <m...@apache.org> > *Sent:* Tuesday, March 21, 2017 8:41:58 AM > *To:* us...@zeppelin.apache.org

Re: Roadmap for 0.8.0

+1 with latest/stable. From: moon soo Lee <m...@apache.org> Sent: Tuesday, March 21, 2017 8:41:58 AM To: us...@zeppelin.apache.org Cc: dev@zeppelin.apache.org Subject: Re: Roadmap for 0.8.0 And if i suggest simplest way for us to set quality expec

Re: Roadmap for 0.8.0

ng it unstable fits with the > ASF release process though. > > Other projects have code freeze, RC (and longer RC iteration time) etc. - > do we think those will help improve quality when the release is finally cut? > > > _____ > From: Jianfeng (Jeff)

Re: Roadmap for 0.8.0

se process though. > > Other projects have code freeze, RC (and longer RC iteration time) etc. - > do we think those will help improve quality when the release is finally cut? > > > _ > From: Jianfeng (Jeff) Zhang <jzh...@hortonworks.com> &g

Re: Roadmap for 0.8.0

__ > From: Jianfeng (Jeff) Zhang <jzh...@hortonworks.com> > Sent: Monday, March 20, 2017 6:13 PM > Subject: Re: Roadmap for 0.8.0 > To: <us...@zeppelin.apache.org>, dev <dev@zeppelin.apache.org> > > > > Strongly +1 for adding system test for different inter

Re: Roadmap for 0.8.0

? _ From: Jianfeng (Jeff) Zhang <jzh...@hortonworks.com<mailto:jzh...@hortonworks.com>> Sent: Monday, March 20, 2017 6:13 PM Subject: Re: Roadmap for 0.8.0 To: <us...@zeppelin.apache.org<mailto:us...@zeppelin.apache.org>>, dev <dev@zep

Re: Roadmap for 0.8.0

e.org<mailto:us...@zeppelin.apache.org>" <us...@zeppelin.apache.org<mailto:us...@zeppelin.apache.org>>, dev <dev@zeppelin.apache.org<mailto:dev@zeppelin.apache.org>> Subject: Re: Roadmap for 0.8.0 Great to see discussion for 0.8.0. List of features for 0.8.0 looks really go

Re: Roadmap for 0.8.0

m in as well. > > > -- > *From:* Jongyoul Lee <jongy...@gmail.com> > *Sent:* Sunday, March 19, 2017 9:03:24 PM > *To:* dev; us...@zeppelin.apache.org > *Subject:* Roadmap for 0.8.0 > > Hi dev & users, > > Recently, community submit

Re: Roadmap for 0.8.0

There are several pending visualization improvements/PRs that would be very good to get them in as well. From: Jongyoul Lee <jongy...@gmail.com> Sent: Sunday, March 19, 2017 9:03:24 PM To: dev; us...@zeppelin.apache.org Subject: Roadmap for 0.8.0 Hi dev &

Re: Roadmap for 0.8.0

Yeah, make sense. Jongyoul Lee 于2017年3月20日周一 下午7:21写道： > Thanks for letting me know. I agree almost things we should develop. > Personally, concerning refactoring it, I'm doing a bit with several PRs but > we need to restructure InterpreterFactory. At first, list up all

Re: Roadmap for 0.8.0

Thanks for letting me know. I agree almost things we should develop. Personally, concerning refactoring it, I'm doing a bit with several PRs but we need to restructure InterpreterFactory. At first, list up all issues and make some groups and handle it. How do you think? On Mon, Mar 20, 2017 at

Re: Roadmap for 0.8.0

Here's some candidates for 0.8 IMO - Restructing InterpreterFacotry https://issues.apache.org/jira/browse/ZEPPELIN-2056Although it is refactoring ticket, I feel it is pretty important thing to do. As I see many bugs are due to interpreter factory component, and I do feel it needs

Roadmap for 0.8.0

Hi dev & users, Recently, community submits very new features for Apache Zeppelin. I think it's very positive signals to improve Apache Zeppelin and its community. But in another aspect, we should focus on what the next release includes. I think we need to summarize and prioritize them. Here is