+1 (binding)
Checked md5, sha256 and gpg signatures. Glance through RELEASE_NOTES,
NOTICE, LICENSE, sampled source code files for LICENSE HEADER.
Better to update Apache copyright year to 2016 next time.
Daniel
On Wed, Jan 13, 2016 at 12:56 PM, Thejas Nair wrote:
> +1
Thanks for your votes and comments.
I'm delighted to announce that this vote passes with the following
results:
3 binding +1s:
Jean-Baptiste Onofré
Thejas Nair
Daniel Dai
1 non-binding +1s:
Wang Wei
We will remove the .sha256 file and update the Copyright to 2016 for the
next release.
+1 (binding)
Examined the LICENSE, NOTICE, README, and DISCLAIMER files. Checked
the signatures and checksum.
Like in the previous release, sha256 checksum matches what is in the
email, however, the .sha256 file seems like a different binary file.
The .md5 hash is the only hash most projects seem
+1 (binding)
Regards
JB
On 01/11/2016 02:12 PM, ooibc wrote:
Hi all,
The SINGA community has voted on and approved a proposal to release Apache
SINGA 0.2.0 (incubating). The license issues in RC1 have been fixed.
The vote thread is at:
+1 (non-binding)
The licenses can be checked using Apache Rat via
```
./autogen.sh
./configure
make rat
```
Best,
Wei
On Mon, Jan 11, 2016 at 9:12 PM, ooibc wrote:
> Hi all,
>
> The SINGA community has voted on and approved a proposal to release Apache
> SINGA 0.2.0
Hi all,
The SINGA community has voted on and approved a proposal to release
Apache
SINGA 0.2.0 (incubating). The license issues in RC1 have been fixed.
The vote thread is at: