Okay. Let's fail rc2, and I'll prepare rc3 with SPARK-26859. DB Tsai | Siri Open Source Technologies [not a contribution] | Apple, Inc
> On Feb 20, 2019, at 12:11 PM, Marcelo Vanzin <van...@cloudera.com.INVALID> > wrote: > > Just wanted to point out that > https://issues.apache.org/jira/browse/SPARK-26859 is not in this RC, > and is marked as a correctness bug. (The fix is in the 2.4 branch, > just not in rc2.) > > On Wed, Feb 20, 2019 at 12:07 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 Feb 24 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-rc2 (commit >> 229ad524cfd3f74dd7aa5fc9ba841ae223caa960): >> https://github.com/apache/spark/tree/v2.4.1-rc2 >> >> The release files, including signatures, digests, etc. can be found at: >> https://dist.apache.org/repos/dist/dev/spark/v2.4.1-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-1299/ >> >> The documentation corresponding to this release can be found at: >> https://dist.apache.org/repos/dist/dev/spark/v2.4.1-rc2-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 >> > > > -- > Marcelo > > --------------------------------------------------------------------- > To unsubscribe e-mail: dev-unsubscr...@spark.apache.org > --------------------------------------------------------------------- To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
