spark-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hyukjin Kwon <gurwls...@gmail.com>
Subject Re: [VOTE] Release Spark 3.1.0 (RC1)
Date Wed, 06 Jan 2021 06:11:06 GMT
Seems like we have two PRs for both blockers, and one is already merged,
nice.
I will wait for a couple of days more before starting a new RC to make sure
we catch more regressions before the new RC.
Please keep testing this RC. I would appreciate it :-).

2021년 1월 6일 (수) 오후 2:28, Hyukjin Kwon <gurwls223@gmail.com>님이 작성:

> Actually, I will mark https://issues.apache.org/jira/browse/SPARK-34021
> as a blocker too. For CRAN submission, we should fix it.
>
> 2021년 1월 6일 (수) 오후 1:47, Jungtaek Lim <kabhwan.opensource@gmail.com>님이
작성:
>
>> There's an issue SPARK-33635 [1] reported due to performance regression
>> on Kafka read between Spark 2.4 vs 3.0, which sounds like a blocker. I'll
>> mark this as a blocker, unless anyone has different opinions.
>>
>> 1. https://issues.apache.org/jira/browse/SPARK-33635
>>
>> On Wed, Jan 6, 2021 at 9:01 AM Hyukjin Kwon <gurwls223@gmail.com> wrote:
>>
>>> Please vote on releasing the following candidate as Apache Spark version
>>> 3.1.0.
>>>
>>> The vote is open until January 8th 4PM 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.1.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.1.0-rc1 (commit
>>> 97340c1e34cfd84de445b6b7545cfa466a1baaf6):
>>> https://github.com/apache/spark/tree/v3.1.0-rc1
>>>
>>> The release files, including signatures, digests, etc. can be found at:
>>> https://dist.apache.org/repos/dist/dev/spark/v3.1.0-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-1363/
>>>
>>> The documentation corresponding to this release can be found at:
>>> https://dist.apache.org/repos/dist/dev/spark/v3.1.0-rc1-docs/
>>>
>>> The list of bug fixes going into 3.1.0 can be found at the following URL:
>>> https://s.apache.org/ldzzl
>>>
>>> This release is using the release script of the tag v3.1.0-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 via "pip install
>>> https://dist.apache.org/repos/dist/dev/spark/v3.1.0-rc1-bin/pyspark-3.1.0.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.1.0?
>>> ===========================================
>>>
>>> The current list of open tickets targeted at 3.1.0 can be found at:
>>> https://issues.apache.org/jira/projects/SPARK and search for "Target
>>> Version/s" = 3.1.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.
>>>
>>>

Mime
View raw message