Re: [VOTE] Release 0.6.0, release candidate #2

+1 (binding) - Build is OK on the tag - Checked the signature (updated) - Checked checksums - Checked ASF headers - Run tests on my samples (Java SDK) Regards JB On 03/11/2017 06:05 AM, Ahmet Altay wrote: Hi everyone, Please review and vote on the release candidate #2 for the version 0.6.0,

Re: [VOTE] Release 0.6.0, release candidate #2

Ismaël, It is my mistake, I hashed files before the rename. I fixed the two files: apache-beam-0.6.0-python.zip.md5 apache-beam-0.6.0-python.zip.sha1 Note that, there are no changes to the calculated hashes or to the zip file itself. I will document the correct procedure in my update to

Re: [VOTE] Release 0.6.0, release candidate #2

+1 Details: - Built locally with 'mvn clean install –Prelease' - Needed to change pip2 to pip2.7. This issue is known on OS X and shall not block the release in my opinion. - Sanity check on Python-SDK: - apache-beam-0.6.0.tar.gz has the same content as apache-beam-0.6.0.zip - ran

Re: [VOTE] Release 0.6.0, release candidate #2

I was able to run "mvn clean install -Prelease" command successfully, too. On Sun, Mar 12, 2017 at 12:02 AM, Ahmet Altay wrote: > Amit, > > I was able to successfully build in a clean environment with the following > commands: > > git checkout tags/v0.6.0-RC2 -b RC2 >

Re: [VOTE] Release 0.6.0, release candidate #2

I found an issue too with the .md5 and sha1 files of the python release, they refer to a different default file (a forgotten part of the renaming): curl https://dist.apache.org/repos/dist/dev/beam/0.6.0/apache-beam-0.6.0-python.zip.md5 7d4170e381ce0e1aa8d11bee2e63d151 apache-beam-0.6.0.zip This

Beam deploy uploads some artifacts twice

I've been trying to release an internal fork and found out that trying to release with maven release plugin uploads twice some artifacts - for me it was "beam-sdks-java-core", for JB (who helped me investigate this) it was a different artifact. At first I blamed release plugin, but even a simple

Re: [VOTE] Release 0.6.0, release candidate #2

Amit, I was able to successfully build in a clean environment with the following commands: git checkout tags/v0.6.0-RC2 -b RC2 mvn clean install -Prelease I am not a very familiar with maven build process, it would be great if someone else can also confirm this. Ahmet On Sat, Mar 11, 2017