+1 On Sun, Sep 25, 2016 at 1:16 PM Yin Huai <yh...@databricks.com> wrote:
> +1 > > On Sun, Sep 25, 2016 at 11:40 AM, Dongjoon Hyun <dongj...@apache.org> > wrote: > >> +1 (non binding) >> >> RC3 is compiled and tested on the following two systems, too. All tests >> passed. >> >> * CentOS 7.2 / Oracle JDK 1.8.0_77 / R 3.3.1 >> with -Pyarn -Phadoop-2.7 -Pkinesis-asl -Phive -Phive-thriftserver >> -Dsparkr >> * CentOS 7.2 / Open JDK 1.8.0_102 >> with -Pyarn -Phadoop-2.7 -Pkinesis-asl -Phive -Phive-thriftserver >> >> Cheers, >> Dongjoon >> >> >> >> On Saturday, September 24, 2016, Reynold Xin <r...@databricks.com> wrote: >> >>> Please vote on releasing the following candidate as Apache Spark version >>> 2.0.1. The vote is open until Tue, Sep 27, 2016 at 15:30 PDT and passes if >>> a majority of at least 3+1 PMC votes are cast. >>> >>> [ ] +1 Release this package as Apache Spark 2.0.1 >>> [ ] -1 Do not release this package because ... >>> >>> >>> The tag to be voted on is v2.0.1-rc3 >>> (9d28cc10357a8afcfb2fa2e6eecb5c2cc2730d17) >>> >>> This release candidate resolves 290 issues: >>> https://s.apache.org/spark-2.0.1-jira >>> >>> The release files, including signatures, digests, etc. can be found at: >>> http://people.apache.org/~pwendell/spark-releases/spark-2.0.1-rc3-bin/ >>> >>> Release artifacts are signed with the following key: >>> https://people.apache.org/keys/committer/pwendell.asc >>> >>> The staging repository for this release can be found at: >>> https://repository.apache.org/content/repositories/orgapachespark-1201/ >>> >>> The documentation corresponding to this release can be found at: >>> http://people.apache.org/~pwendell/spark-releases/spark-2.0.1-rc3-docs/ >>> >>> >>> Q: How can I help test this release? >>> A: If you are a Spark user, you can help us test this release by taking >>> an existing Spark workload and running on this release candidate, then >>> reporting any regressions from 2.0.0. >>> >>> Q: What justifies a -1 vote for this release? >>> A: This is a maintenance release in the 2.0.x series. Bugs already >>> present in 2.0.0, missing features, or bugs related to new features will >>> not necessarily block this release. >>> >>> Q: What fix version should I use for patches merging into branch-2.0 >>> from now on? >>> A: Please mark the fix version as 2.0.2, rather than 2.0.1. If a new RC >>> (i.e. RC4) is cut, I will change the fix version of those patches to 2.0.1. >>> >>> >>> >
