+1

On Tue, Jan 24, 2017 at 8:19 PM, Hyung Sung Shim <hss...@nflabs.com> wrote:

> +1
> 2017년 1월 24일 (화) 오전 1:36, Windy Qin <windyqinchaof...@163.com>님이 작성:
>
>>
>> +1
>> On 2017-01-24 17:13 (+0800), Sora Lee <sora0...@zepl.com> wrote:
>> > +1
>> >
>> > On Tue, Jan 24, 2017 at 3:09 PM Jongyoul Lee <jongy...@gmail.com>
>> wrote:
>> >
>> > > +1 (binding)
>> > >
>> > > On Tue, Jan 24, 2017 at 2:43 PM, Mina Lee <mina...@apache.org> wrote:
>> > >
>> > > I propose the following RC to be released for the Apache Zeppelin
>> 0.7.0
>> > > release.
>> > >
>> > > The commit id is 48ad70e8c62975bdb00779bed5919eaca98c5b5d which is
>> > > corresponds to the tag v0.7.0-rc3:
>> > > *https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;a=commit;h=
>> 48ad70e8c62975bdb00779bed5919eaca98c5b5d
>> > > <https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;a=commit;h=
>> 48ad70e8c62975bdb00779bed5919eaca98c5b5d>*
>> > >
>> > > The release archives (tgz), signature, and checksums are here
>> > > https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.7.0-rc3/
>> > >
>> > > The release candidate consists of the following source distribution
>> > > archive
>> > > zeppelin-0.7.0.tgz
>> > >
>> > > In addition, the following supplementary binary distributions are
>> provided
>> > > for user convenience at the same location
>> > > zeppelin-0.7.0-bin-all.tgz
>> > > zeppelin-0.7.0-bin-netinst.tgz
>> > >
>> > > The maven artifacts are here
>> > > https://repository.apache.org/content/repositories/
>> orgapachezeppelin-1024
>> > >
>> > > 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?
>> version=12336544&projectId=12316221
>> > >
>> > > Vote will be open for next 72 hours (close at 22:00 26/Jan PST).
>> > >
>> > > [ ] +1 approve
>> > > [ ] 0 no opinion
>> > > [ ] -1 disapprove (and reason why)
>> > >
>> > >
>> > >
>> > >
>> > > --
>> > > 이종열, Jongyoul Lee, 李宗烈
>> > > http://madeng.net
>> > >
>> >
>>
>

Reply via email to