Hi dev,

all blockers and subtasks tracked under
https://issues.apache.org/jira/browse/ZEPPELIN-1177 has been resolved.
I am going to start release process and will send a vote email in next few
hours.
Please test it out with your environment feel free to share your thoughts
in vote thread.

Regards,
Mina

On Fri, Jul 15, 2016 at 5:51 PM, Felix Cheung <felixcheun...@hotmail.com>
wrote:

> Don't we need the official Spark 2.0.0 artifacts in maven central repo to
> official release support for it?
>
>
>
>
>
> On Thu, Jul 14, 2016 at 5:39 PM -0700, "Vinay Shukla" <
> vinayshu...@gmail.com<mailto:vinayshu...@gmail.com>> wrote:
>
> We should not wait. I anticipate Spark 2.0 to be officially announced <
> 2weeks. Would be great to be the first notebook to support 2.0.
>
> On Thursday, July 14, 2016, Luciano Resende <luckbr1...@gmail.com> wrote:
>
> > For Spark 2.0, do we need to wait for it's official release which is
> close
> > by...
> >
> > On Thu, Jul 14, 2016 at 3:45 PM, moon soo Lee <m...@apache.org
> > <javascript:;>> wrote:
> >
> > > Hi folks,
> > >
> > > We have released 0.6.0 July 2nd. During the 0.6.0 release discussion
> [1],
> > > we could see consensus that having a release 0.6.1 when Zeppelin have
> > Spark
> > > 2.0 support.
> > >
> > > I have created a issue for 0.6.1 release [2]. The issue currently have
> > > Spark 2.0 and scala 2.11 support as a blocker.
> > >
> > > There were some bug fixes on master branch since 0.6.0 release.
> > > How about we discuss and backport some important bug fixes into
> > > branch-0.6.0? (if any)
> > > And how about we start release process of 0.6.1, as soon as all
> blockers
> > of
> > > [2] being resolved?
> > >
> > >
> > > Thanks,
> > > moon
> > >
> > > [1]
> > >
> > >
> > https://lists.apache.org/thread.html/e107c44df1a7fc4cd232144f6a24d8
> 1b32a7d988d5947093b79f05ee@1464110799@%3Cdev.zeppelin.apache.org%3E
> > > [2] https://issues.apache.org/jira/browse/ZEPPELIN-1177
> > >
> >
> >
> >
> > --
> > Luciano Resende
> > http://twitter.com/lresende1975
> > http://lresende.blogspot.com/
> >
>

Reply via email to