Reposting for shane here [SPARK-27178] https://github.com/apache/spark/commit/342e91fdfa4e6ce5cc3a0da085d1fe723184021b
Is problematic too and it’s not in the rc8 cut https://github.com/apache/spark/commits/branch-2.4 (Personally I don’t want to delay 2.4.1 either..) ________________________________ From: Sean Owen <sro...@gmail.com> Sent: Wednesday, March 20, 2019 11:18 AM To: DB Tsai Cc: dev Subject: Re: [VOTE] Release Apache Spark 2.4.1 (RC8) +1 for this RC. The tag is correct, licenses and sigs check out, tests of the source with most profiles enabled works for me. On Tue, Mar 19, 2019 at 5:28 PM DB Tsai <d_t...@apple.com.invalid> wrote: > > Please vote on releasing the following candidate as Apache Spark version > 2.4.1. > > The vote is open until March 23 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.1 > [ ] -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.1-rc8 (commit > 746b3ddee6f7ad3464e326228ea226f5b1f39a41): > https://github.com/apache/spark/tree/v2.4.1-rc8 > > The release files, including signatures, digests, etc. can be found at: > https://dist.apache.org/repos/dist/dev/spark/v2.4.1-rc8-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-1318/ > > The documentation corresponding to this release can be found at: > https://dist.apache.org/repos/dist/dev/spark/v2.4.1-rc8-docs/ > > The list of bug fixes going into 2.4.1 can be found at the following URL: > https://issues.apache.org/jira/projects/SPARK/versions/2.4.1 > > 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.1? > =========================================== > > The current list of open tickets targeted at 2.4.1 can be found at: > https://issues.apache.org/jira/projects/SPARK and search for "Target > Version/s" = 2.4.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 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. > > > DB Tsai | Siri Open Source Technologies [not a contribution] | Apple, Inc > > > --------------------------------------------------------------------- > To unsubscribe e-mail: dev-unsubscr...@spark.apache.org > --------------------------------------------------------------------- To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
