+1 R tests, package tests on r-hub. Manually check commits under R, doc etc
________________________________ From: Sean Owen <sro...@gmail.com> Sent: Saturday, April 20, 2019 11:27 AM To: Wenchen Fan Cc: Spark dev list Subject: Re: [VOTE] Release Apache Spark 2.4.2 +1 from me too. It seems like there is support for merging the Jackson change into 2.4.x (and, I think, a few more minor dependency updates) but this doesn't have to go into 2.4.2. That said, if there is another RC for any reason, I think we could include it. Otherwise can wait for 2.4.3. 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. --------------------------------------------------------------------- To unsubscribe e-mail: dev-unsubscr...@spark.apache.org