+1 (binding) On Mon, 3 Jul 2017 at 11:53 Yanbo Liang <yblia...@gmail.com> wrote:
> +1 > > On Mon, Jul 3, 2017 at 5:35 AM, Herman van Hövell tot Westerflier < > hvanhov...@databricks.com> wrote: > >> +1 >> >> On Sun, Jul 2, 2017 at 11:32 PM, Ricardo Almeida < >> ricardo.alme...@actnowib.com> wrote: >> >>> +1 (non-binding) >>> >>> Built and tested with -Phadoop-2.7 -Dhadoop.version=2.7.3 -Pyarn -Phive >>> -Phive-thriftserver -Pscala-2.11 on >>> >>> - macOS 10.12.5 Java 8 (build 1.8.0_131) >>> - Ubuntu 17.04, Java 8 (OpenJDK 1.8.0_111) >>> >>> >>> >>> >>> >>> On 1 Jul 2017 02:45, "Michael Armbrust" <mich...@databricks.com> wrote: >>> >>> Please vote on releasing the following candidate as Apache Spark >>> version 2.2.0. The vote is open until Friday, July 7th, 2017 at 18:00 >>> PST and passes if a majority of at least 3 +1 PMC votes are cast. >>> >>> [ ] +1 Release this package as Apache Spark 2.2.0 >>> [ ] -1 Do not release this package because ... >>> >>> >>> To learn more about Apache Spark, please see https://spark.apache.org/ >>> >>> The tag to be voted on is v2.2.0-rc6 >>> <https://github.com/apache/spark/tree/v2.2.0-rc6> ( >>> a2c7b2133cfee7fa9abfaa2bfbfb637155466783) >>> >>> List of JIRA tickets resolved can be found with this filter >>> <https://issues.apache.org/jira/browse/SPARK-20134?jql=project%20%3D%20SPARK%20AND%20fixVersion%20%3D%202.2.0> >>> . >>> >>> The release files, including signatures, digests, etc. can be found at: >>> https://home.apache.org/~pwendell/spark-releases/spark-2.2.0-rc6-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-1245/ >>> >>> The documentation corresponding to this release can be found at: >>> https://people.apache.org/~pwendell/spark-releases/spark-2.2.0-rc6-docs/ >>> >>> >>> *FAQ* >>> >>> *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. >>> >>> *What should happen to JIRA tickets still targeting 2.2.0?* >>> >>> Committers should look at those and triage. Extremely important bug >>> fixes, documentation, and API tweaks that impact compatibility should be >>> worked on immediately. Everything else please retarget to 2.3.0 or 2.2.1. >>> >>> *But my bug isn't fixed!??!* >>> >>> In order to make timely releases, we will typically not hold the release >>> unless the bug in question is a regression from 2.1.1. >>> >>> >>> >> >> >