You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Julia Wang (QIUHE)" <Qi...@microsoft.com> on 2015/05/05 23:14:25 UTC
[VOTE] Release Apache REEF 0.11.0-incubating (rc4)
This is to call for a new vote for the source release of Apache REEF 0.11.0-incubating (rc4).
The source tar ball, including signatures, digests, etc can be found at:
https://dist.apache.org/repos/dist/dev/incubator/reef/0.11.0-incubating/
The Git tag is release-0.11.0-incubating-rc4
The Git commit ID is b89aef3ebfcf12d8c0c566be902c14dcae6bc0e2
Checksums of apache-reef-0.11.0-incubating-rc4.tar.gz:
MD5: 808e6580f7784a79e22494af2b51bdff
SHA1: ab4396c3ff0bd33fddc6c5e2ed09f121d71c9a93
SHA512: f16d1986e5250df5b785bc7db467023280829cc1877c5160d1f3eda8cdd47f38071644943b6c05899736ea01bf455503116ee017bdae913aeb1b6b094186bb2c
Release artifacts are signed with the key. The KEYS file is available here:
https://dist.apache.org/repos/dist/dev/incubator/reef/KEYS
Issues Resolved in the release
149 issues were closed/resolved for this release:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20REEF%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20resolution%20in%20(Fixed%2C%20Implemented)%20ORDER%20BY%20updated%20ASC&startIndex=150
Issue resolved in RC4:
1. Update copy right in run.cmd
2. Remove end space in ./lang/cs/Org.Apache.REEF.Driver/Evaluator/IEvaluatorRequest.cs
3. Upload release candidate to https://dist.apache.org/repos/dist/dev/incubator/reef/0.11.0-incubating/ instead of release folder
4. JIRA REEF-307 is opened to follow up for CRLF line terminator issue.
5. The key used to sign the tar file is cross signed by colleague (Markus Weimer)
The vote will be open for 72 hours. Please download the release candidate, check the hashes/signature, build it and test it, and then please vote:
[ ] +1 Release this package as Apache REEF 0.11.0-incubating
[ ] +0 no opinion
[ ] -1 Do not release this package because ...
Thanks,
Julia
RE: [VOTE] Release Apache REEF 0.11.0-incubating (rc4)
Posted by "Julia Wang (QIUHE)" <Qi...@microsoft.com>.
SHA512 file generated in my local is plain text file. After svn to the server, it becomes binary format. Not sure if it is by design? The one in release folder for 0.10.0 is the same.
Attached is the plain test SHA512 file before uploading the web server.
-----Original Message-----
From: Markus Weimer [mailto:markus@weimo.de]
Sent: Tuesday, May 5, 2015 5:55 PM
To: dev@reef.incubator.apache.org
Subject: Re: [VOTE] Release Apache REEF 0.11.0-incubating (rc4)
-1 overall for test failures. Details below:
md5, sha1 and gpg verified. sha512 did not for me, but that might be local to my machine.
Using the tar command from cygwin or msysgit created a folder I can no longer delete upon unzip. 7-zip worked though. It would be good to hear from UNIX users what their experience was.
The java build and tests passed. The .NET build passed
The .NET tests failed. I ran them using
`vstest.console.exe Org.Apache.REEF.Tests.dll /Platform:x64 *>errors`
in the folder lang\cs\bin\x64\Debug\Org.Apache.REEF.Tests after building in Visual Studio. I pasted the output here:
http://1drv.ms/1KKGxtg
Markus
On 2015-05-05 14:14, Julia Wang (QIUHE) wrote:
> This is to call for a new vote for the source release of Apache REEF 0.11.0-incubating (rc4).
>
> The source tar ball, including signatures, digests, etc can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/reef/0.11.0-incubatin
> g/
>
> The Git tag is release-0.11.0-incubating-rc4 The Git commit ID is
> b89aef3ebfcf12d8c0c566be902c14dcae6bc0e2
>
>
> Checksums of apache-reef-0.11.0-incubating-rc4.tar.gz:
>
> MD5: 808e6580f7784a79e22494af2b51bdff
>
> SHA1: ab4396c3ff0bd33fddc6c5e2ed09f121d71c9a93
>
> SHA512:
> f16d1986e5250df5b785bc7db467023280829cc1877c5160d1f3eda8cdd47f38071644
> 943b6c05899736ea01bf455503116ee017bdae913aeb1b6b094186bb2c
>
>
> Release artifacts are signed with the key. The KEYS file is available here:
>
> https://dist.apache.org/repos/dist/dev/incubator/reef/KEYS
>
>
>
> Issues Resolved in the release
>
> 149 issues were closed/resolved for this release:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20REEF%20AND%
> 20status%20in%20(Resolved%2C%20Closed)%20AND%20resolution%20in%20(Fixe
> d%2C%20Implemented)%20ORDER%20BY%20updated%20ASC&startIndex=150
>
>
>
> Issue resolved in RC4:
>
> 1. Update copy right in run.cmd
>
> 2. Remove end space in ./lang/cs/Org.Apache.REEF.Driver/Evaluator/IEvaluatorRequest.cs
>
> 3. Upload release candidate to https://dist.apache.org/repos/dist/dev/incubator/reef/0.11.0-incubating/ instead of release folder
>
> 4. JIRA REEF-307 is opened to follow up for CRLF line terminator issue.
>
> 5. The key used to sign the tar file is cross signed by colleague (Markus Weimer)
>
>
>
> The vote will be open for 72 hours. Please download the release candidate, check the hashes/signature, build it and test it, and then please vote:
>
>
>
> [ ] +1 Release this package as Apache REEF 0.11.0-incubating
>
> [ ] +0 no opinion
>
> [ ] -1 Do not release this package because ...
>
>
>
> Thanks,
>
> Julia
>
>
Re: [VOTE] Release Apache REEF 0.11.0-incubating (rc4)
Posted by Markus Weimer <ma...@weimo.de>.
-1 overall for test failures. Details below:
md5, sha1 and gpg verified. sha512 did not for me, but that might be
local to my machine.
Using the tar command from cygwin or msysgit created a folder I can no
longer delete upon unzip. 7-zip worked though. It would be good to hear
from UNIX users what their experience was.
The java build and tests passed. The .NET build passed
The .NET tests failed. I ran them using
`vstest.console.exe Org.Apache.REEF.Tests.dll /Platform:x64 *>errors`
in the folder lang\cs\bin\x64\Debug\Org.Apache.REEF.Tests after building
in Visual Studio. I pasted the output here:
http://1drv.ms/1KKGxtg
Markus
On 2015-05-05 14:14, Julia Wang (QIUHE) wrote:
> This is to call for a new vote for the source release of Apache REEF 0.11.0-incubating (rc4).
>
> The source tar ball, including signatures, digests, etc can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/reef/0.11.0-incubating/
>
> The Git tag is release-0.11.0-incubating-rc4
> The Git commit ID is b89aef3ebfcf12d8c0c566be902c14dcae6bc0e2
>
>
> Checksums of apache-reef-0.11.0-incubating-rc4.tar.gz:
>
> MD5: 808e6580f7784a79e22494af2b51bdff
>
> SHA1: ab4396c3ff0bd33fddc6c5e2ed09f121d71c9a93
>
> SHA512: f16d1986e5250df5b785bc7db467023280829cc1877c5160d1f3eda8cdd47f38071644943b6c05899736ea01bf455503116ee017bdae913aeb1b6b094186bb2c
>
>
> Release artifacts are signed with the key. The KEYS file is available here:
>
> https://dist.apache.org/repos/dist/dev/incubator/reef/KEYS
>
>
>
> Issues Resolved in the release
>
> 149 issues were closed/resolved for this release:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20REEF%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20resolution%20in%20(Fixed%2C%20Implemented)%20ORDER%20BY%20updated%20ASC&startIndex=150
>
>
>
> Issue resolved in RC4:
>
> 1. Update copy right in run.cmd
>
> 2. Remove end space in ./lang/cs/Org.Apache.REEF.Driver/Evaluator/IEvaluatorRequest.cs
>
> 3. Upload release candidate to https://dist.apache.org/repos/dist/dev/incubator/reef/0.11.0-incubating/ instead of release folder
>
> 4. JIRA REEF-307 is opened to follow up for CRLF line terminator issue.
>
> 5. The key used to sign the tar file is cross signed by colleague (Markus Weimer)
>
>
>
> The vote will be open for 72 hours. Please download the release candidate, check the hashes/signature, build it and test it, and then please vote:
>
>
>
> [ ] +1 Release this package as Apache REEF 0.11.0-incubating
>
> [ ] +0 no opinion
>
> [ ] -1 Do not release this package because ...
>
>
>
> Thanks,
>
> Julia
>
>
RE: [VOTE] Release Apache REEF 0.11.0-incubating (rc4)
Posted by "Julia Wang (QIUHE)" <Qi...@microsoft.com>.
It is made by:
$ sha512sum apache-reef-0.11.0-incubating-rc4.tar.gz > apache-reef-0.11.0-incubating-rc4.tar.gz.sha512
When I check, I got the result:
$ sha512sum -c apache-reef-0.11.0-incubating-rc4.tar.gz.sha512
apache-reef-0.11.0-incubating-rc4.tar.gz: OK
-----Original Message-----
From: Markus Weimer [mailto:markus@weimo.de]
Sent: Tuesday, May 5, 2015 3:41 PM
To: dev@reef.incubator.apache.org
Subject: Re: [VOTE] Release Apache REEF 0.11.0-incubating (rc4)
Hi,
how's the sha512 made? I got the following in cygwin:
> $ sha512sum.exe -c apache-reef-0.11.0-incubating-rc4.tar.gz.sha512
> sha512sum: apache-reef-0.11.0-incubating-rc4.tar.gz.sha512: no properly formatted SHA512 checksum lines found
Markus
Re: [VOTE] Release Apache REEF 0.11.0-incubating (rc4)
Posted by Markus Weimer <ma...@weimo.de>.
Hi,
how's the sha512 made? I got the following in cygwin:
> $ sha512sum.exe -c apache-reef-0.11.0-incubating-rc4.tar.gz.sha512
> sha512sum: apache-reef-0.11.0-incubating-rc4.tar.gz.sha512: no properly formatted SHA512 checksum lines found
Markus