+1.

Noting that Suneel was +1 in the original thread (ie: you have 3
mentor/Incubator-PMC  +1s).

Hen

On Tue, Oct 24, 2017 at 11:06 PM, Sebastian <ssc.o...@googlemail.com> wrote:

> +1 (binding)
>
> Successfully built and validated the RC from source.
>
> Best,
> Sebastian
>
>
> On 25.10.2017 03:38, Meghna Baijal wrote:
>
>> Hello All,
>>
>> This is a call for releasing Apache MXNet (incubating) 0.12.0, release
>> candidate 0.
>>
>> Apache MXNet community has voted and approved the release.
>>
>> *Vote thread:*
>> https://lists.apache.org/thread.html/800402860be8a1b4055ede0
>> 75ab465af48b7f8d041b42217372a63b9@%3Cdev.mxnet.apache.org%3E
>>
>> *Result thread:*
>> https://lists.apache.org/thread.html/83ab3763f0bb84685112692
>> 66bf0c26bdc786509d2cb38a2aafe30a3@%3Cdev.mxnet.apache.org%3E
>>
>>
>> *The source tarball, including signatures, digests, etc. can be found at:*
>> https://dist.apache.org/repos/dist/dev/incubator/mxnet/0.12.0.rc0/
>>
>>
>> *The release tag can be found here: *
>> https://github.com/apache/incubator-mxnet/tree/0.12.0.rc0
>>
>>
>> *The release hash is 4f2af2d2e5216ab3a1faadcc117709b6836029dc and can be
>> found here:*
>> https://github.com/apache/incubator-mxnet/commit/4f2af2d2e52
>> 16ab3a1faadcc117709b6836029dc
>>
>>
>> *Release artifacts are signed with the following key:*
>> 69FF E8D6 1051 FFE7 E61B 02C2 80FD 81D7 703D F31B
>>
>>
>> *KEY files are available here:*
>> https://dist.apache.org/repos/dist/dev/incubator/mxnet/0.12.0.rc0/
>>
>>
>> *For information about the contents of this release, see:*
>> https://cwiki.apache.org/confluence/display/MXNET/MXNet+0.
>> 12.0+Release+Notes
>>
>>
>> The vote will be open for at least 72 hours.
>>
>> [ ] +1 Release this package as 0.12.0
>> [ ] +0 no opinion
>> [ ] -1 Do not release this package because...
>>
>> Thanks,
>> Meghna Baijal
>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Reply via email to