+1 (non-binding) So far I've successfully checked: * signatures and digests * source releases file layouts * no binaries included in the source release * matched git tag * NOTICE and LICENSE files * license headers * clean build (Java 1.8.0_91, Maven 3.3.9, Python 2.7.12+, Debian amd64)
BTW, some minor things: * 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. * I've noticed the build take much more time than previous releases. * 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 * Notice the current Python SDK may require sudo permissions in some environments Cheers, On Fri, Mar 10, 2017 at 1:07 AM, Ahmet Altay <[email protected]> wrote: > Hi everyone, > > Please review and vote on the release candidate #1 for the version 0.6.0, > as follows: > [ ] +1, Approve the release > [ ] -1, Do not approve the release (please provide specific comments) > > The complete staging area is available for your review, which includes: > * JIRA release notes [1], > * the official Apache source release to be deployed to dist.apache.org > [2], > which is signed with the key with fingerprint 6096FA00 [3], > * all artifacts to be deployed to the Maven Central Repository [4], > * source code tag "v0.6.0-RC1" [5], > * website pull request listing the release and publishing the API reference > manual [6]. > * python artifacts are deployed along with the source release to to > dist.apache.org [2]. > > A suite of Jenkins jobs: > * PreCommit_Java_MavenInstall [7], > * PostCommit_Java_MavenInstall [8], > * PostCommit_Java_RunnableOnService_Apex [9], > * PostCommit_Java_RunnableOnService_Flink [10], -> ran into a known issue > [14] > * PostCommit_Java_RunnableOnService_Spark [11], > * PostCommit_Java_RunnableOnService_Dataflow [12] -> timed out at 100 > minutes, the logs are good up to that point [15] is for increasing this > timeout. > * PostCommit_Python_Verify [13] > > The vote will be open for at least 72 hours. It is adopted by majority > approval, with at least 3 PMC affirmative votes. > > Thanks, > Ahmet > > [1] > https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje > ctId=12319527&version=12339256 > [2] https://dist.apache.org/repos/dist/dev/beam/0.6.0/ > [3] https://dist.apache.org/repos/dist/dev/beam/KEYS > [4] https://repository.apache.org/content/repositories/orgapachebeam-1012/ > [5] > https://git-wip-us.apache.org/repos/asf?p=beam.git;a=tag;h=r > efs/tags/v0.6.0-RC1 > [6] https://github.com/apache/beam-site/pull/175 > [7] > https://builds.apache.org/view/Beam/job/beam_PreCommit_Java_ > MavenInstall/8281/ > [8] > https://builds.apache.org/view/Beam/job/beam_PostCommit_Java > _MavenInstall/2858/ > [9] > https://builds.apache.org/view/Beam/job/beam_PostCommit_Java > _RunnableOnService_Apex/717/ > [10] > https://builds.apache.org/view/Beam/job/beam_PostCommit_Java > _RunnableOnService_Flink/1874/ > [11] > https://builds.apache.org/view/Beam/job/beam_PostCommit_Java > _RunnableOnService_Spark/1184/ > [12] > https://builds.apache.org/view/Beam/job/beam_PostCommit_Java > _RunnableOnService_Dataflow/2511/ > [13] > https://builds.apache.org/view/Beam/job/beam_PostCommit_Pyth > on_Verify/1466/ > [14] https://issues.apache.org/jira/browse/BEAM-1674 > [15] https://github.com/apache/beam/pull/2197 > -- Sergio Fernández Partner Technology Manager Redlink GmbH m: +43 6602747925 <+43%20660%202747925> e: [email protected] w: http://redlink.co
