+1 (non-binding)

On Mon, Apr 10, 2023 at 7:07 AM yangjie01 <yangji...@baidu.com> wrote:

> +1 (non-binding)
>
>
>
> *发件人**: *Sean Owen <sro...@apache.org>
> *日期**: *2023年4月10日 星期一 21:19
> *收件人**: *Dongjoon Hyun <dongj...@apache.org>
> *抄送**: *"dev@spark.apache.org" <dev@spark.apache.org>
> *主题**: *Re: [VOTE] Release Apache Spark 3.2.4 (RC1)
>
>
>
> +1 from me
>
>
>
> On Sun, Apr 9, 2023 at 7:19 PM Dongjoon Hyun <dongj...@apache.org> wrote:
>
> I'll start with my +1.
>
> I verified the checksum, signatures of the artifacts, and documentations.
> Also, ran the tests with YARN and K8s modules.
>
> Dongjoon.
>
> On 2023/04/09 23:46:10 Dongjoon Hyun wrote:
> > Please vote on releasing the following candidate as Apache Spark version
> > 3.2.4.
> >
> > The vote is open until April 13th 1AM (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 3.2.4
> > [ ] -1 Do not release this package because ...
> >
> > To learn more about Apache Spark, please see https://spark.apache.org/
> <https://mailshield.baidu.com/check?q=iR6md5rYrz%2bpTPJlEXXlR6NN3aGjunZT0DADO3Pcgs0%3d>
> >
> > The tag to be voted on is v3.2.4-rc1 (commit
> > 0ae10ac18298d1792828f1d59b652ef17462d76e)
> > https://github.com/apache/spark/tree/v3.2.4-rc1
> <https://mailshield.baidu.com/check?q=aM%2biUnDuINfMt3gSiEoeO%2f3rOURRhcI1K3w2wXLBsmwpOhUnhXALteGFgnDF87YBRmXrDw%3d%3d>
> >
> > The release files, including signatures, digests, etc. can be found at:
> > https://dist.apache.org/repos/dist/dev/spark/v3.2.4-rc1-bin/
> <https://mailshield.baidu.com/check?q=PLuZhGOcwxq%2bBJH6w0yImyvZ8ddRFU6%2bAX%2f%2fpfUsY%2b0YTwWHciYcNtxbBG6QVJUOhbvIvV%2btWzE8EVWX7VLdpA%3d%3d>
> >
> > Signatures used for Spark RCs can be found in this file:
> > https://dist.apache.org/repos/dist/dev/spark/KEYS
> <https://mailshield.baidu.com/check?q=E6fHbSXEWw02TTJBpc3bfA9mi7ea0YiWcNHkm%2fDJxwlaWinGnMdaoO1PahHhgj00vKwcbElpuHA%3d>
> >
> > The staging repository for this release can be found at:
> > https://repository.apache.org/content/repositories/orgapachespark-1442/
> <https://mailshield.baidu.com/check?q=opJwdjT%2fEBNlaZIhEUT9IPb4vBaliC0eLeR5q4zjJk67ooLLzQOondvN7oZYTZfU3zXLbOMGRk1hyc0un3sao73UeM4AX05d0Tlp2A%3d%3d>
> >
> > The documentation corresponding to this release can be found at:
> > https://dist.apache.org/repos/dist/dev/spark/v3.2.4-rc1-docs/
> <https://mailshield.baidu.com/check?q=kvbgoCFOcPc90I0aHmx4TuBWn3nElJyVn7Qpr%2f5B40cdw5%2f%2b2iuCmJwJ5ecVkdMlwocJOxWtts%2bN8hBJsTiGHFZLMfk%3d>
> >
> > The list of bug fixes going into 3.2.4 can be found at the following URL:
> > https://issues.apache.org/jira/projects/SPARK/versions/12352607
> <https://mailshield.baidu.com/check?q=vJAyNbOnMz%2f4Pg0M3EIPzAd0P3uyJCALKBab%2fxP3MNPkbsCkKVe6ecemGYRhcv6xKq1%2fyxjJwEopnXkklZaQWMBOsEk%3d>
> >
> > This release is using the release script of the tag v3.2.4-rc1.
> >
> > 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 3.2.4?
> > ===========================================
> >
> > The current list of open tickets targeted at 3.2.4 can be found at:
> > https://issues.apache.org/jira/projects/SPARK
> <https://mailshield.baidu.com/check?q=4UUpJqq41y71Gnuj0qTUYo6hTjqzT7oytN6x%2fvgC5XUtQUC8MfJ77tj7K70O%2f1QMmNoa1A%3d%3d>
> and search for "Target
> > Version/s" = 3.2.4
> >
> > 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
>
>

Reply via email to