I agree with the sentiment that we should build a new release candidate. BEAM-1674 problem. I have a fix for it in this PR: > https://github.com/apache/beam/pull/2217 > > I'm afraid we have to cancel the release yet again because this is a real > bug that people can run into. >
+1 -- let's take this PR. > * As I already commented on past release votes, formally it's better to > include commit id referencing the release, since git tags can be changed. > Just take that into account for upcoming releases. > +1 -- let's do this for the next release candidate. We should update the release guide, so we don't forget it next time. > 1. The https://dist.apache.org/repos/dist/dev/beam/0.6.0/apache-bea > m-0.6.0.tar.gz should be name apache-beam-0.6.0-python.tar.gz > +1 -- let's fix this. > 2. The distribution archives are not consistents: the source distribution > is a zip archive, the python distribution is tar.gz. I would provide both > tar.gz and zip for both. > +1 -- let's fix this. * Also I got this minor warning on the Maven build: > > [WARNING] Some problems were encountered while building the effective model > for org.apache.beam:beam-runners-google-cloud-dataflow-java:jar:0.6.0 > [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' > must be unique: org.apache.beam:beam-runners-core-construction-java:jar -> > duplicate declaration of version (?) @ org.apache.beam:beam-runners-g > oogle-cloud-dataflow-java:[unknown-version], > /home/wikier/tmp/beam/apache-b > eam-0.6.0/runners/google-cloud-dataflow-java/pom.xml, line 360, column 19 > +1 -- let's fix this. 3. Python should contain a README to start with. > This would be great, but no reason to block a release for it, right? * I've noticed the build take much more time than previous releases. > This is the first time with the Python SDK in the release, as well as several new IOs, so I'd expect it to take longer. Do you perhaps have any breakdown where the time is going? No reason to block a release, right? * Notice the current Python SDK may require sudo permissions in some > environments > Ahmet, any thoughts here? Would be good to fix, if feasible.
