Another issue https://issues.apache.org/jira/browse/SPARK-22479 is also critical for security. We should also merge it to 2.2.1?
2017-11-15 9:12 GMT-08:00 Xiao Li <gatorsm...@gmail.com>: > Hi, Felix, > > https://issues.apache.org/jira/browse/SPARK-22469 > > Maybe also include this regression of 2.2? It works in 2.1 > > Thanks, > > Xiao > > > > 2017-11-14 22:25 GMT-08:00 Felix Cheung <felixche...@apache.org>: > >> Please vote on releasing the following candidate as Apache Spark version >> 2.2.1. The vote is open until Monday November 20, 2017 at 23:00 UTC and >> passes if a majority of at least 3 PMC +1 votes are cast. >> >> >> [ ] +1 Release this package as Apache Spark 2.2.1 >> >> [ ] -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.1-rc1 https://github.com/apache/spar >> k/tree/v2.2.1-rc1 (41116ab7fca46db7255b01e8727e2e5d571a3e35) >> >> List of JIRA tickets resolved in this release can be found here >> https://issues.apache.org/jira/projects/SPARK/versions/12340470 >> >> >> The release files, including signatures, digests, etc. can be found at: >> https://dist.apache.org/repos/dist/dev/spark/spark-2.2.1-rc1-bin/ >> >> Release artifacts are signed with the following key: >> https://dist.apache.org/repos/dist/dev/spark/KEYS >> >> The staging repository for this release can be found at: >> https://repository.apache.org/content/repositories/orgapachespark-1256/ >> >> The documentation corresponding to this release can be found at: >> https://dist.apache.org/repos/dist/dev/spark/spark-2.2.1-rc1 >> -docs/_site/index.html >> >> >> *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. >> >> If you're working in PySpark you can set up a virtual env and install the >> current RC and see if anything important breaks, in the Java/Scala you can >> add the staging repository to your projects resolvers and test with the RC >> (make sure to clean up the artifact cache before/after so you don't end up >> building with a out of date RC going forward). >> >> *What should happen to JIRA tickets still targeting 2.2.1?* >> >> 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.2.2. >> >> *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.2.0. That being said if >> there is something which is a regression form 2.2.0 that has not been >> correctly targeted please ping a committer to help target the issue (you >> can see the open issues listed as impacting Spark 2.2.1 / 2.2.2 here >> <https://issues.apache.org/jira/issues/?jql=project%20%3D%20SPARK%20AND%20status%20%3D%20OPEN%20AND%20(affectedVersion%20%3D%202.2.1%20OR%20affectedVersion%20%3D%202.2.2)> >> . >> >> What are the unresolved issues targeted for 2.2.1 >> <https://issues.apache.org/jira/issues/?jql=project%20%3D%20SPARK%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20%22Target%20Version%2Fs%22%20%3D%202.2.1> >> ? >> >> At the time of the writing, there is one resolved SPARK-22471 >> <https://issues.apache.org/jira/browse/SPARK-22471> would help >> stability, and one in progress on joins SPARK-22042 >> <https://issues.apache.org/jira/browse/SPARK-22042> >> >> >> >> >
