+1 Xiao Li
2017-07-06 22:18 GMT-07:00 Yin Huai <yh...@databricks.com>: > +1 > > On Thu, Jul 6, 2017 at 8:40 PM, Hyukjin Kwon <gurwls...@gmail.com> wrote: > >> +1 >> >> 2017-07-07 6:41 GMT+09:00 Reynold Xin <r...@databricks.com>: >> >>> +1 >>> >>> >>> On Fri, Jun 30, 2017 at 6:44 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, 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> (a2c7b2133cfee7f >>>> a9abfaa2bfbfb637155466783) >>>> >>>> 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. >>>> >>> >>> >> >
