[VOTE] Release Apache Spark 3.5.3 (RC1)

[Haejoon Lee <ha...@databricks.com.INVALID>]

Hi, dev!

Please vote on releasing the following candidate as Apache Spark version
3.5.3.

The vote is open until Sep 6, 11 PM UTC, 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.5.3
[ ] -1 Do not release this package because ...

To learn more about Apache Spark, please see https://spark.apache.org/

The tag to be voted on is v3.5.3-rc1 (commit
a1cd99de04aaa56a710c5ecfbfa1dca07a012242):
https://github.com/apache/spark/tree/v3.5.3-rc1

The release files, including signatures, digests, etc. can be found at:
https://dist.apache.org/repos/dist/dev/spark/v3.5.3-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-1464/

The documentation corresponding to this release can be found at:
https://dist.apache.org/repos/dist/dev/spark/v3.5.3-rc1-docs/

The list of bug fixes going into 3.5.3 can be found at the following URL:
https://issues.apache.org/jira/projects/SPARK/versions/12354954

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 via "pip install
https://dist.apache.org/repos/dist/dev/spark/v3.5.3-rc1-bin/pyspark-3.5.3.tar.gz
"
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.5.3?
===========================================

The current list of open tickets targeted at 3.5.3 can be found at:
https://issues.apache.org/jira/projects/SPARK and search for
"Target Version/s" = 3.5.3

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!
Haejoon Lee

Re: [VOTE] Release Apache Spark 3.5.3 (RC1)

[Wenchen Fan <cl...@gmail.com>]

-1 as we found unintentional behavior changes for catalog plugins that use
DelegatingCatalogExtension: https://github.com/apache/spark/pull/47995

On Wed, Sep 4, 2024 at 11:24 AM Allison Wang
<al...@databricks.com.invalid> wrote:

> +1
>
> On Tue, Sep 3, 2024 at 4:46 PM Hyukjin Kwon <gu...@apache.org> wrote:
>
>> +1
>>
>>
>> On Wed, 4 Sept 2024 at 08:43, Haejoon Lee
>> <ha...@databricks.com.invalid> wrote:
>>
>>> Hi, dev!
>>>
>>> Please vote on releasing the following candidate as Apache Spark version
>>> 3.5.3.
>>>
>>> The vote is open until Sep 6, 11 PM UTC, 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.5.3
>>> [ ] -1 Do not release this package because ...
>>>
>>> To learn more about Apache Spark, please see https://spark.apache.org/
>>>
>>> The tag to be voted on is v3.5.3-rc1 (commit
>>> a1cd99de04aaa56a710c5ecfbfa1dca07a012242):
>>> https://github.com/apache/spark/tree/v3.5.3-rc1
>>>
>>> The release files, including signatures, digests, etc. can be found at:
>>> https://dist.apache.org/repos/dist/dev/spark/v3.5.3-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-1464/
>>>
>>> The documentation corresponding to this release can be found at:
>>> https://dist.apache.org/repos/dist/dev/spark/v3.5.3-rc1-docs/
>>>
>>> The list of bug fixes going into 3.5.3 can be found at the following URL:
>>> https://issues.apache.org/jira/projects/SPARK/versions/12354954
>>>
>>> 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 via "pip install
>>> https://dist.apache.org/repos/dist/dev/spark/v3.5.3-rc1-bin/pyspark-3.5.3.tar.gz
>>> "
>>> 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.5.3?
>>> ===========================================
>>>
>>> The current list of open tickets targeted at 3.5.3 can be found at:
>>> https://issues.apache.org/jira/projects/SPARK and search for
>>> "Target Version/s" = 3.5.3
>>>
>>> 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!
>>> Haejoon Lee
>>>
>>

Re: [VOTE] Release Apache Spark 3.5.3 (RC1)

[Allison Wang <al...@databricks.com.INVALID>]

+1

On Tue, Sep 3, 2024 at 4:46 PM Hyukjin Kwon <gu...@apache.org> wrote:

> +1
>
>
> On Wed, 4 Sept 2024 at 08:43, Haejoon Lee
> <ha...@databricks.com.invalid> wrote:
>
>> Hi, dev!
>>
>> Please vote on releasing the following candidate as Apache Spark version
>> 3.5.3.
>>
>> The vote is open until Sep 6, 11 PM UTC, 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.5.3
>> [ ] -1 Do not release this package because ...
>>
>> To learn more about Apache Spark, please see https://spark.apache.org/
>>
>> The tag to be voted on is v3.5.3-rc1 (commit
>> a1cd99de04aaa56a710c5ecfbfa1dca07a012242):
>> https://github.com/apache/spark/tree/v3.5.3-rc1
>>
>> The release files, including signatures, digests, etc. can be found at:
>> https://dist.apache.org/repos/dist/dev/spark/v3.5.3-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-1464/
>>
>> The documentation corresponding to this release can be found at:
>> https://dist.apache.org/repos/dist/dev/spark/v3.5.3-rc1-docs/
>>
>> The list of bug fixes going into 3.5.3 can be found at the following URL:
>> https://issues.apache.org/jira/projects/SPARK/versions/12354954
>>
>> 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 via "pip install
>> https://dist.apache.org/repos/dist/dev/spark/v3.5.3-rc1-bin/pyspark-3.5.3.tar.gz
>> "
>> 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.5.3?
>> ===========================================
>>
>> The current list of open tickets targeted at 3.5.3 can be found at:
>> https://issues.apache.org/jira/projects/SPARK and search for
>> "Target Version/s" = 3.5.3
>>
>> 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!
>> Haejoon Lee
>>
>

Re: [VOTE] Release Apache Spark 3.5.3 (RC1)

[Hyukjin Kwon <gu...@apache.org>]

+1


On Wed, 4 Sept 2024 at 08:43, Haejoon Lee
<ha...@databricks.com.invalid> wrote:

> Hi, dev!
>
> Please vote on releasing the following candidate as Apache Spark version
> 3.5.3.
>
> The vote is open until Sep 6, 11 PM UTC, 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.5.3
> [ ] -1 Do not release this package because ...
>
> To learn more about Apache Spark, please see https://spark.apache.org/
>
> The tag to be voted on is v3.5.3-rc1 (commit
> a1cd99de04aaa56a710c5ecfbfa1dca07a012242):
> https://github.com/apache/spark/tree/v3.5.3-rc1
>
> The release files, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/spark/v3.5.3-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-1464/
>
> The documentation corresponding to this release can be found at:
> https://dist.apache.org/repos/dist/dev/spark/v3.5.3-rc1-docs/
>
> The list of bug fixes going into 3.5.3 can be found at the following URL:
> https://issues.apache.org/jira/projects/SPARK/versions/12354954
>
> 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 via "pip install
> https://dist.apache.org/repos/dist/dev/spark/v3.5.3-rc1-bin/pyspark-3.5.3.tar.gz
> "
> 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.5.3?
> ===========================================
>
> The current list of open tickets targeted at 3.5.3 can be found at:
> https://issues.apache.org/jira/projects/SPARK and search for
> "Target Version/s" = 3.5.3
>
> 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!
> Haejoon Lee
>