+1

I verified the same steps like previous RCs.

Dongjoon.


On Sat, Apr 8, 2023 at 7:47 PM Mridul Muralidharan <mri...@gmail.com> wrote:

>
> +1
>
> Signatures, digests, etc check out fine.
> Checked out tag and build/tested with -Phive -Pyarn -Pmesos -Pkubernetes
>
> Regards,
> Mridul
>
>
> On Sat, Apr 8, 2023 at 12:13 PM L. C. Hsieh <vii...@gmail.com> wrote:
>
>> +1
>>
>> Thanks Xinrong.
>>
>> On Sat, Apr 8, 2023 at 8:23 AM yangjie01 <yangji...@baidu.com> wrote:
>> >
>> > +1
>> >
>> >
>> >
>> > 发件人: Sean Owen <sro...@apache.org>
>> > 日期: 2023年4月8日 星期六 20:27
>> > 收件人: Xinrong Meng <xinrong.apa...@gmail.com>
>> > 抄送: dev <dev@spark.apache.org>
>> > 主题: Re: [VOTE] Release Apache Spark 3.4.0 (RC7)
>> >
>> >
>> >
>> > +1 form me, same result as last time.
>> >
>> >
>> >
>> > On Fri, Apr 7, 2023 at 6:30 PM Xinrong Meng <xinrong.apa...@gmail.com>
>> wrote:
>> >
>> > Please vote on releasing the following candidate(RC7) as Apache Spark
>> version 3.4.0.
>> >
>> > The vote is open until 11:59pm Pacific time April 12th 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.4.0
>> > [ ] -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 v3.4.0-rc7 (commit
>> 87a5442f7ed96b11051d8a9333476d080054e5a0):
>> > https://github.com/apache/spark/tree/v3.4.0-rc7
>> >
>> > The release files, including signatures, digests, etc. can be found at:
>> > https://dist.apache.org/repos/dist/dev/spark/v3.4.0-rc7-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-1441
>> >
>> > The documentation corresponding to this release can be found at:
>> > https://dist.apache.org/repos/dist/dev/spark/v3.4.0-rc7-docs/
>> >
>> > The list of bug fixes going into 3.4.0 can be found at the following
>> URL:
>> > https://issues.apache.org/jira/projects/SPARK/versions/12351465
>> >
>> > This release is using the release script of the tag v3.4.0-rc7.
>> >
>> >
>> > 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 an out of date RC going forward).
>> >
>> > ===========================================
>> > What should happen to JIRA tickets still targeting 3.4.0?
>> > ===========================================
>> > The current list of open tickets targeted at 3.4.0 can be found at:
>> > https://issues.apache.org/jira/projects/SPARK and search for "Target
>> Version/s" = 3.4.0
>> >
>> > 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.
>> >
>> > Thanks,
>> > Xinrong Meng
>>
>> ---------------------------------------------------------------------
>> To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
>>
>>

Reply via email to