FYI I believe we have an open correctness issue here: https://issues.apache.org/jira/browse/SPARK-25150
However, it needs review by another person to confirm whether it is indeed a correctness issue (and whether it still impacts this latest RC). Nick 2018년 10월 10일 (수) 오후 3:14, Jean Georges Perrin <j...@jgp.net>님이 작성: > Awesome - thanks Dongjoon! > > > On Oct 10, 2018, at 2:36 PM, Dongjoon Hyun <dongjoon.h...@gmail.com> > wrote: > > For now, you can see generated release notes. Official one will be posted > on the website when the official 2.4.0 is out. > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315420&version=12342385 > > Bests, > Dongjoon. > > > On Wed, Oct 10, 2018 at 11:29 AM Jean Georges Perrin <j...@jgp.net> wrote: > >> Hi, >> >> Sorry if it's stupid question, but where can I find the release notes of >> 2.4.0? >> >> jg >> >> On Oct 10, 2018, at 2:00 PM, Imran Rashid <iras...@cloudera.com.INVALID> >> wrote: >> >> Sorry I had messed up my testing earlier, so I only just discovered >> https://issues.apache.org/jira/browse/SPARK-25704 >> >> I dont' think this is a release blocker, because its not a regression and >> there is a workaround, just fyi. >> >> On Wed, Oct 10, 2018 at 11:47 AM Wenchen Fan <cloud0...@gmail.com> wrote: >> >>> Please vote on releasing the following candidate as Apache Spark version >>> 2.4.0. >>> >>> The vote is open until October 1 PST and passes if a majority +1 PMC >>> votes are cast, with >>> a minimum of 3 +1 votes. >>> >>> [ ] +1 Release this package as Apache Spark 2.4.0 >>> [ ] -1 Do not release this package because ... >>> >>> To learn more about Apache Spark, please see http://spark.apache.org/ >>> >>> The tag to be voted on is v2.4.0-rc3 (commit >>> 8e4a99bd201b9204fec52580f19ae70a229ed94e): >>> https://github.com/apache/spark/tree/v2.4.0-rc3 >>> >>> The release files, including signatures, digests, etc. can be found at: >>> https://dist.apache.org/repos/dist/dev/spark/v2.4.0-rc3-bin/ >>> >>> Signatures used for Spark RCs can be found in this file: >>> 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-1289 >>> >>> The documentation corresponding to this release can be found at: >>> https://dist.apache.org/repos/dist/dev/spark/v2.4.0-rc3-docs/ >>> >>> The list of bug fixes going into 2.4.0 can be found at the following URL: >>> https://issues.apache.org/jira/projects/SPARK/versions/12342385 >>> >>> 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.4.0? >>> =========================================== >>> >>> The current list of open tickets targeted at 2.4.0 can be found at: >>> https://issues.apache.org/jira/projects/SPARK and search for "Target >>> Version/s" = 2.4.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 an >>> appropriate release. >>> >>> ================== >>> 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 the previous >>> release. That being said, if there is something which is a regression >>> that has not been correctly targeted please ping me or a committer to >>> help target the issue. >>> >> >> >
