You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by "Lee moon soo (JIRA)" <ji...@apache.org> on 2015/09/17 06:08:45 UTC
[jira] [Created] (ZEPPELIN-311) Release 0.5.5
Lee moon soo created ZEPPELIN-311:
-------------------------------------
Summary: Release 0.5.5
Key: ZEPPELIN-311
URL: https://issues.apache.org/jira/browse/ZEPPELIN-311
Project: Zeppelin
Issue Type: Task
Reporter: Lee moon soo
Fix For: 0.5.5
having a intermediate release before 0.6.0 is discussed at http://apache-zeppelin-incubating-dev-mailing-list.75694.x6.nabble.com/DISCUSS-Upcoming-release-td1463.html
I think version name can be 0.5.5, by considering changes since 0.5.0 and 0.6.0 roadmap.
* Create release branch
* Add fix version 0.5.5 to related JIRA issue
is the main action items to the release.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: [jira] [Created] (ZEPPELIN-311) Release 0.5.5
Posted by moon soo Lee <mo...@apache.org>.
Hi Guillaume,
One of the reason 0.5.5-incubating is released from master branch
(0.6.0-SNAPSHOT) with 0.5.5 version instead of 0.6.0 name is, because of it
was not closed to 0.6.0 roadmap. I think if we make release from current
master, it can be 0.5.6 instead of 0.6.0 for the same reason. Unless we
update the roadmap or release strategy.
I think roadmap published on the wiki is not something set in stone. Adding
authentication to 0.6.0 roadmap perfectly make sense to me.
About Helium, i have created proposal and proof of concept implementation
but the idea is still quite complicated and need to be simplified more.
Hope i can make proposal more simple soon, and start a discussion based on
it. I think Zeppelin now have some ways to make custom visualizations.
Helium will be another way to make custom visualizations, in pluggable way.
I think many features planned in 0.6.0 roadmap requires large code base
change. So, just after release of spark 1.6, Zeppelin can release
0.5.6-incubating from it's master branch. And then community can dive into
features of 0.6.0 roadmap that includes authentication, pluggable
visualizations and so on, which requires relatively large code base change.
Thanks,
moon
On Fri, Dec 11, 2015 at 4:04 PM tog <gu...@gmail.com> wrote:
> Hi
>
> I would like to follow-up on that email from mid-september regarding
> releases. I think it would be interesting to make sure we have a PR
> tracking the progress of all the features we want to see in the next
> release otherwise I feel it is very difficult for people to get a sense of
> where the project is heading.
>
> I know we have this issue
>
> https://issues.apache.org/jira/browse/ZEPPELIN/fixforversion/12332761/?selectedTab=com.atlassian.jira.jira-projects-plugin:version-summary-panel
> but it does not seems in sync with what the wiki states in
> https://cwiki.apache.org/confluence/display/ZEPPELIN/Zeppelin+Roadmap
>
> On top of that, I would like to understand if some important (perception
> from the community) features like:
> - authentication/authorisation : see
> https://github.com/apache/incubator-zeppelin/pull/53 and/or
> https://issues.apache.org/jira/browse/ZEPPELIN-193 shall be explicitly
> included in the roadmap (my feeling is that it should). This feature is
> triggering discussions on the mailing list on regular basis and has been
> open for quite some time. Making it "official" will probably act as an
> incentive and help the latest minor issues be solved quickly,
> - visualisation: modular visualisation is on the roadmap but this is not
> very clear (at least to me) what it includes. For example, it would be
> interesting to understand how related to Helium it is? and therefore how is
> that interfering with ZEPPELIN-157: Adding Map Visualization for Zeppelin
> which is open since July and is again something interesting the community.
>
> Cheers
> Guillaume
>
>
>
> On Thu, 17 Sep 2015 at 06:08 Lee moon soo (JIRA) <ji...@apache.org> wrote:
>
> > Lee moon soo created ZEPPELIN-311:
> > -------------------------------------
> >
> > Summary: Release 0.5.5
> > Key: ZEPPELIN-311
> > URL: https://issues.apache.org/jira/browse/ZEPPELIN-311
> > Project: Zeppelin
> > Issue Type: Task
> > Reporter: Lee moon soo
> > Fix For: 0.5.5
> >
> >
> > having a intermediate release before 0.6.0 is discussed at
> >
> http://apache-zeppelin-incubating-dev-mailing-list.75694.x6.nabble.com/DISCUSS-Upcoming-release-td1463.html
> >
> > I think version name can be 0.5.5, by considering changes since 0.5.0 and
> > 0.6.0 roadmap.
> >
> > * Create release branch
> > * Add fix version 0.5.5 to related JIRA issue
> >
> > is the main action items to the release.
> >
> >
> >
> > --
> > This message was sent by Atlassian JIRA
> > (v6.3.4#6332)
> >
>
Re: [jira] [Created] (ZEPPELIN-311) Release 0.5.5
Posted by Corneau Damien <co...@gmail.com>.
I can reply for the visualizations.
I'm currently working on having ZEPPELIN-157 being merged.
For the modular visualizations, it is in some way possible using %angular
or %html.
But we were at first thinking to have a set of core functions to facilitate
bringing visualizations in the same way as ZEPPELIN-157, and with it a
better way to select the visualization.
However, I think it will switch to rely more on Helium (By being able to
package custom %angular and %html code). We would then have a more
pluggable visualization system, which would allow us to not be annoyed by
possible licensing issues, and make the release lighter (compared to having
every visualization included).
However we would still need to have a core module to handle visualization
packages. For now we are making a few tests using Helium to see what is
needed and how we can interact from data to visualization.
On Fri, Dec 11, 2015 at 4:04 PM, tog <gu...@gmail.com> wrote:
> Hi
>
> I would like to follow-up on that email from mid-september regarding
> releases. I think it would be interesting to make sure we have a PR
> tracking the progress of all the features we want to see in the next
> release otherwise I feel it is very difficult for people to get a sense of
> where the project is heading.
>
> I know we have this issue
>
> https://issues.apache.org/jira/browse/ZEPPELIN/fixforversion/12332761/?selectedTab=com.atlassian.jira.jira-projects-plugin:version-summary-panel
> but it does not seems in sync with what the wiki states in
> https://cwiki.apache.org/confluence/display/ZEPPELIN/Zeppelin+Roadmap
>
> On top of that, I would like to understand if some important (perception
> from the community) features like:
> - authentication/authorisation : see
> https://github.com/apache/incubator-zeppelin/pull/53 and/or
> https://issues.apache.org/jira/browse/ZEPPELIN-193 shall be explicitly
> included in the roadmap (my feeling is that it should). This feature is
> triggering discussions on the mailing list on regular basis and has been
> open for quite some time. Making it "official" will probably act as an
> incentive and help the latest minor issues be solved quickly,
> - visualisation: modular visualisation is on the roadmap but this is not
> very clear (at least to me) what it includes. For example, it would be
> interesting to understand how related to Helium it is? and therefore how is
> that interfering with ZEPPELIN-157: Adding Map Visualization for Zeppelin
> which is open since July and is again something interesting the community.
>
> Cheers
> Guillaume
>
>
>
> On Thu, 17 Sep 2015 at 06:08 Lee moon soo (JIRA) <ji...@apache.org> wrote:
>
> > Lee moon soo created ZEPPELIN-311:
> > -------------------------------------
> >
> > Summary: Release 0.5.5
> > Key: ZEPPELIN-311
> > URL: https://issues.apache.org/jira/browse/ZEPPELIN-311
> > Project: Zeppelin
> > Issue Type: Task
> > Reporter: Lee moon soo
> > Fix For: 0.5.5
> >
> >
> > having a intermediate release before 0.6.0 is discussed at
> >
> http://apache-zeppelin-incubating-dev-mailing-list.75694.x6.nabble.com/DISCUSS-Upcoming-release-td1463.html
> >
> > I think version name can be 0.5.5, by considering changes since 0.5.0 and
> > 0.6.0 roadmap.
> >
> > * Create release branch
> > * Add fix version 0.5.5 to related JIRA issue
> >
> > is the main action items to the release.
> >
> >
> >
> > --
> > This message was sent by Atlassian JIRA
> > (v6.3.4#6332)
> >
>
Re: [jira] [Created] (ZEPPELIN-311) Release 0.5.5
Posted by tog <gu...@gmail.com>.
Hi
I would like to follow-up on that email from mid-september regarding
releases. I think it would be interesting to make sure we have a PR
tracking the progress of all the features we want to see in the next
release otherwise I feel it is very difficult for people to get a sense of
where the project is heading.
I know we have this issue
https://issues.apache.org/jira/browse/ZEPPELIN/fixforversion/12332761/?selectedTab=com.atlassian.jira.jira-projects-plugin:version-summary-panel
but it does not seems in sync with what the wiki states in
https://cwiki.apache.org/confluence/display/ZEPPELIN/Zeppelin+Roadmap
On top of that, I would like to understand if some important (perception
from the community) features like:
- authentication/authorisation : see
https://github.com/apache/incubator-zeppelin/pull/53 and/or
https://issues.apache.org/jira/browse/ZEPPELIN-193 shall be explicitly
included in the roadmap (my feeling is that it should). This feature is
triggering discussions on the mailing list on regular basis and has been
open for quite some time. Making it "official" will probably act as an
incentive and help the latest minor issues be solved quickly,
- visualisation: modular visualisation is on the roadmap but this is not
very clear (at least to me) what it includes. For example, it would be
interesting to understand how related to Helium it is? and therefore how is
that interfering with ZEPPELIN-157: Adding Map Visualization for Zeppelin
which is open since July and is again something interesting the community.
Cheers
Guillaume
On Thu, 17 Sep 2015 at 06:08 Lee moon soo (JIRA) <ji...@apache.org> wrote:
> Lee moon soo created ZEPPELIN-311:
> -------------------------------------
>
> Summary: Release 0.5.5
> Key: ZEPPELIN-311
> URL: https://issues.apache.org/jira/browse/ZEPPELIN-311
> Project: Zeppelin
> Issue Type: Task
> Reporter: Lee moon soo
> Fix For: 0.5.5
>
>
> having a intermediate release before 0.6.0 is discussed at
> http://apache-zeppelin-incubating-dev-mailing-list.75694.x6.nabble.com/DISCUSS-Upcoming-release-td1463.html
>
> I think version name can be 0.5.5, by considering changes since 0.5.0 and
> 0.6.0 roadmap.
>
> * Create release branch
> * Add fix version 0.5.5 to related JIRA issue
>
> is the main action items to the release.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
>