As before, release looks good, all Scala, Python tests pass. R tests fail with same issue in SPARK-21093 but it's not a blocker.
+1 (binding) On Wed, 21 Jun 2017 at 01:49 Michael Armbrust <mich...@databricks.com> wrote: > I will kick off the voting with a +1. > > On Tue, Jun 20, 2017 at 4:49 PM, 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, June 23rd, 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-rc5 >> <https://github.com/apache/spark/tree/v2.2.0-rc5> ( >> 62e442e73a2fa663892d2edaff5f7d72d7f402ed) >> >> 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-rc5-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-1243/ >> >> The documentation corresponding to this release can be found at: >> https://people.apache.org/~pwendell/spark-releases/spark-2.2.0-rc5-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. >> > >
