spark-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jacek Laskowski <ja...@japila.pl>
Subject Re: [VOTE] Release Spark 3.1.1 (RC2)
Date Fri, 19 Feb 2021 13:14:46 GMT
Hi Hyukjin,

FYI: cloud-fan commented 3 hours ago: thanks, merging to master/3.1!

https://github.com/apache/spark/pull/31550#issuecomment-781977920

Pozdrawiam,
Jacek Laskowski
----
https://about.me/JacekLaskowski
"The Internals Of" Online Books <https://books.japila.pl/>
Follow me on https://twitter.com/jaceklaskowski

<https://twitter.com/jaceklaskowski>


On Sat, Feb 13, 2021 at 3:46 AM Hyukjin Kwon <gurwls223@gmail.com> wrote:

> I have received a ping about a new blocker, a regression on a temporary
> function in CTE - worked before but now it's broken (
> https://github.com/apache/spark/pull/31550). Thank you @Peter Toth
> <peter.toth@gmail.com>
> I tend to treat this as a legitimate blocker. I will cut another RC right
> after this fix if we're all good with it.
>
> 2021년 2월 11일 (목) 오전 9:20, Takeshi Yamamuro <linguin.m.s@gmail.com>님이
작성:
>
>> +1
>>
>> I looked around the jira tickets and I think there is no explicit blocker
>> issue on the Spark SQL component.
>> Also, I ran the tests on AWS envs and I couldn't find any issue there,
>> too.
>>
>> Bests,
>> Takeshi
>>
>> On Thu, Feb 11, 2021 at 7:37 AM Mridul Muralidharan <mridul@gmail.com>
>> wrote:
>>
>>>
>>> Signatures, digests, etc check out fine.
>>> Checked out tag and build/tested with -Pyarn -Phadoop-2.7 -Phive
>>> -Phive-thriftserver -Pmesos -Pkubernetes
>>>
>>> I keep getting test failures
>>> with org.apache.spark.sql.kafka010.KafkaDelegationTokenSuite: removing this
>>> suite gets the build through though - does anyone have suggestions on how
>>> to fix it ?
>>> Perhaps a local problem at my end ?
>>>
>>>
>>> Regards,
>>> Mridul
>>>
>>>
>>>
>>> On Mon, Feb 8, 2021 at 6:24 PM Hyukjin Kwon <gurwls223@gmail.com> wrote:
>>>
>>>> Please vote on releasing the following candidate as Apache Spark
>>>> version 3.1.1.
>>>>
>>>> The vote is open until February 15th 5PM PST and passes if a majority
>>>> +1 PMC votes are cast, with a minimum of 3 +1 votes.
>>>>
>>>> Note that it is 7 days this time because it is a holiday season in
>>>> several countries including South Korea (where I live), China etc., and I
>>>> would like to make sure people do not miss it because it is a holiday
>>>> season.
>>>>
>>>> [ ] +1 Release this package as Apache Spark 3.1.1
>>>> [ ] -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.1-rc2 (commit
>>>> cf0115ac2d60070399af481b14566f33d22ec45e):
>>>> https://github.com/apache/spark/tree/v3.1.1-rc2
>>>>
>>>> The release files, including signatures, digests, etc. can be found at:
>>>> <https://dist.apache.org/repos/dist/dev/spark/v3.1.1-rc1-bin/>
>>>> https://dist.apache.org/repos/dist/dev/spark/v3.1.1-rc2-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-1365
>>>>
>>>> The documentation corresponding to this release can be found at:
>>>> https://dist.apache.org/repos/dist/dev/spark/v3.1.1-rc2-docs/
>>>>
>>>> The list of bug fixes going into 3.1.1 can be found at the following
>>>> URL:
>>>> https://s.apache.org/41kf2
>>>>
>>>> This release is using the release script of the tag v3.1.1-rc2.
>>>>
>>>> FAQ
>>>>
>>>> ===================
>>>> What happened to 3.1.0?
>>>> ===================
>>>>
>>>> There was a technical issue during Apache Spark 3.1.0 preparation, and
>>>> it was discussed and decided to skip 3.1.0.
>>>> Please see
>>>> https://spark.apache.org/news/next-official-release-spark-3.1.1.html for
>>>> more details.
>>>>
>>>> =========================
>>>> 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.1-rc2-bin/pyspark-3.1.1.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.1?
>>>> ===========================================
>>>>
>>>> The current list of open tickets targeted at 3.1.1 can be found at:
>>>> https://issues.apache.org/jira/projects/SPARK and search for "Target
>>>> Version/s" = 3.1.1
>>>>
>>>> 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.
>>>>
>>>>
>>>>
>>
>> --
>> ---
>> Takeshi Yamamuro
>>
>

Mime
View raw message