+1

I verified below:
- Run Spark, Python, R tutorial notebook
- Signature
- Built with java7


On Thu, Sep 21, 2017 at 11:10 AM, Anthony Corbacho <
anthonycorba...@apache.org> wrote:

> Tested +1 as well
>
>
>
> On Thu, Sep 21, 2017 at 10:59 AM, Hyung Sung Shim <hss...@nflabs.com>
> wrote:
>
> > +1
> > 2017년 9월 20일 (수) 오전 3:17, Krishna Pandey <krish.pande...@gmail.com>님이
> 작성:
> >
> > > +1
> > >
> > > Ran PySpark and Spark use-cases successfully.
> > > Also verified PGP, SHA-512 and MD5 signatures for all binaries.
> > >
> > > Regards,
> > > Krishna Pandey
> > >
> > > On Mon, Sep 18, 2017 at 10:35 PM, Mina Lee <mina...@apache.org> wrote:
> > >
> > > > I propose the following RC to be released for the Apache Zeppelin
> 0.7.3
> > > > release.
> > > >
> > > > The commit id is 5d246c96b054dcb8854e2beb924fc2c89b767fc1 which is
> > > > corresponds to the tag v0.7.3-rc5:
> > > > https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;h=
> > > > refs/tags/v0.7.3-rc5
> > > >
> > > > The release archives (tgz), signature, and checksums are here
> > > > https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.7.3-rc5/
> > > >
> > > > The release candidate consists of the following source distribution
> > > archive
> > > > zeppelin-0.7.3.tgz
> > > >
> > > > In addition, the following supplementary binary distributions are
> > > provided
> > > > for user convenience at the same location
> > > > zeppelin-0.7.3-bin-all.tgz
> > > > zeppelin-0.7.3-bin-netinst.tgz
> > > >
> > > > The maven artifacts are here
> > > >
> > > https://repository.apache.org/content/repositories/
> > orgapachezeppelin-1047
> > > >
> > > > You can find the KEYS file here:
> > > > https://dist.apache.org/repos/dist/release/zeppelin/KEYS
> > > >
> > > > Release notes available at
> > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?versi
> > > > on=12341035&projectId=12316221
> > > >
> > > > Vote will be open for next 72 hours (close at 10:30 21/Sep PDT).
> > > >
> > > > [ ] +1 approve
> > > > [ ] 0 no opinion
> > > > [ ] -1 disapprove (and reason why)
> > > >
> > >
> >
>

Reply via email to