Thanks to everyone who has voted and given their comments. The tally is as
follows:

0 binding +1s

3 non-binding +1s:
Anh Dinh (PPMC)
Wang Wei (PPMC)
Zhaojing Luo (PPMC)

No 0s or -1s.

I am delighted to announce that the proposal to release Apache SINGA
0.3.0-incubating has passed. We'll now start a vote on the general list.
Those of you in the IPMC, please recast your vote on the new thread.

Regards,
Anh.

On 17 April 2016 at 22:49, zhaojing <[email protected]> wrote:

> I checked:
> + build successful
> + Python Binding for Interactive Training (train_mnist.py and
> train_cifar10.py)
>
> Here is my vote:
> +1
>
> Best regards,
> Zhaojing.
>
>
> On 2016-04-17 14:29, Anh Dinh wrote:
>
>> Hi all,
>>
>> I have created a build for Apache SINGA 0.3.0-incubating, release
>> candidate
>> RC3.
>>
>> The artifacts to be voted on are located here:
>> https://dist.apache.org/repos/dist/dev/incubator/singa/0.3.0/
>>
>> The hashes of the artifacts are as follows:
>> MD5:  45 4C 7A BB 17 C7 D6 47  77 85 92 58 59 DF B7 F5
>>
>> Release artifacts are signed with the following key:
>> https://people.apache.org/keys/committer/dinhtta.asc
>>
>> and the signature file is:
>>
>> https://dist.apache.org/repos/dist/dev/incubator/singa/0.3.0/apache-singa-incubating-0.3.0-RC3.tar.gz.asc
>>
>> The Github tag is at:
>> https://github.com/apache/incubator-singa/releases/tag/v0.3.0-rc3
>> commit ID is: d547a861068973db7d8fc82f9c733e95307a40f1
>> Please check and vote on releasing this package. The vote is open for at
>> least 72 hours and passes if a majority of at least three +1 votes are
>> cast.
>>
>> To check the license, you can use the Apache Rat tool following
>>
>> ./configure
>> make rat
>>
>> The result is in rat_check file.
>> To install and test the new features, please read the README file.
>>
>> [ ] +1 Release this package as Apache SINGA 0.3.0-incubating
>> [ ]  0 I don't feel strongly about it, but I'm okay with the release
>> [ ] -1 Do not release this package because...
>>
>> Here is my vote:
>> +1
>>
>> Regards,
>> Anh.
>>
>
>

Reply via email to