Yes, that's proposed by Sean. This time we should publish a Scala 2.12 build, both in maven and the download page.
On Fri, Sep 28, 2018 at 11:34 AM Saisai Shao <sai.sai.s...@gmail.com> wrote: > Only "without-hadoop" profile has 2.12 binary, is it expected? > > Thanks > Saisai > > Wenchen Fan <cloud0...@gmail.com> 于2018年9月28日周五 上午11:08写道： > >> I'm adding my own +1, since all the problems mentioned in the RC1 voting >> email are all resolved. And there is no blocker issue for 2.4.0 AFAIK. >> >> On Fri, Sep 28, 2018 at 10:59 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-rc2 (commit >>> 42f25f309e91c8cde1814e3720099ac1e64783da): >>> https://github.com/apache/spark/tree/v2.4.0-rc2 >>> >>> The release files, including signatures, digests, etc. can be found at: >>> https://dist.apache.org/repos/dist/dev/spark/v2.4.0-rc2-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-1287 >>> >>> The documentation corresponding to this release can be found at: >>> https://dist.apache.org/repos/dist/dev/spark/v2.4.0-rc2-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/2.4.0 >>> >>> 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. >>> >>
