Likewise, ran my usual tests on Ubuntu with yarn/hive/hive-thriftserver/hadoop-2.6 on JDK 8 and all passed. Sigs and licenses are OK. +1
On Thu, Nov 3, 2016 at 7:57 PM Herman van Hövell tot Westerflier < hvanhov...@databricks.com> wrote: > +1 > > On Thu, Nov 3, 2016 at 6:58 PM, Michael Armbrust <mich...@databricks.com> > wrote: > > +1 > > On Wed, Nov 2, 2016 at 5:40 PM, Reynold Xin <r...@databricks.com> wrote: > > Please vote on releasing the following candidate as Apache Spark version > 1.6.3. The vote is open until Sat, Nov 5, 2016 at 18:00 PDT and passes if a > majority of at least 3+1 PMC votes are cast. > > [ ] +1 Release this package as Apache Spark 1.6.3 > [ ] -1 Do not release this package because ... > > > The tag to be voted on is v1.6.3-rc2 > (1e860747458d74a4ccbd081103a0542a2367b14b) > > This release candidate addresses 52 JIRA tickets: > https://s.apache.org/spark-1.6.3-jira > > The release files, including signatures, digests, etc. can be found at: > http://people.apache.org/~pwendell/spark-releases/spark-1.6.3-rc2-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-1212/ > > The documentation corresponding to this release can be found at: > http://people.apache.org/~pwendell/spark-releases/spark-1.6.3-rc2-docs/ > > > ======================================= > == How can I help test this release? > ======================================= > 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 1.6.2. > > ================================================ > == What justifies a -1 vote for this release? > ================================================ > This is a maintenance release in the 1.6.x series. Bugs already present > in 1.6.2, missing features, or bugs related to new features will not > necessarily block this release. > > > >
