+1 I have tested it and looks good! Best Regards, Ryan
On Sun, Apr 21, 2019 at 8:49 PM Wenchen Fan <cloud0...@gmail.com> wrote: > Yea these should be mentioned in the 2.4.1 release notes. > > It seems we only have one ticket that is labeled as "release-notes" for > 2.4.2: https://issues.apache.org/jira/browse/SPARK-27419 . I'll mention > it when I write release notes. > > On Mon, Apr 22, 2019 at 5:46 AM Sean Owen <sro...@gmail.com> wrote: > >> One minor comment: for 2.4.1 we had a couple JIRAs marked 'release-notes': >> >> https://issues.apache.org/jira/browse/SPARK-27198?jql=project%20%3D%20SPARK%20and%20fixVersion%20%20in%20(2.4.1%2C%202.4.2)%20and%20labels%20%3D%20%27release-notes%27 >> >> They should be mentioned in >> https://spark.apache.org/releases/spark-release-2-4-1.html possibly >> like "Changes of behavior" in >> https://spark.apache.org/releases/spark-release-2-4-0.html >> >> I can retroactively update that page; is this part of the notes for >> the release process though? I missed this one for sure as it's easy to >> overlook with all the pages being updated per release. >> >> On Thu, Apr 18, 2019 at 9:51 PM Wenchen Fan <cloud0...@gmail.com> wrote: >> > >> > Please vote on releasing the following candidate as Apache Spark >> version 2.4.2. >> > >> > The vote is open until April 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.2 >> > [ ] -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.2-rc1 (commit >> a44880ba74caab7a987128cb09c4bee41617770a): >> > https://github.com/apache/spark/tree/v2.4.2-rc1 >> > >> > The release files, including signatures, digests, etc. can be found at: >> > https://dist.apache.org/repos/dist/dev/spark/v2.4.2-rc1-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-1322/ >> > >> > The documentation corresponding to this release can be found at: >> > https://dist.apache.org/repos/dist/dev/spark/v2.4.2-rc1-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/12344996 >> > >> > 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.2? >> > =========================================== >> > >> > The current list of open tickets targeted at 2.4.2 can be found at: >> > https://issues.apache.org/jira/projects/SPARK and search for "Target >> Version/s" = 2.4.2 >> > >> > 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. >> >
