spark-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Holden Karau <hol...@pigscanfly.ca>
Subject Re: [VOTE] Release Apache Spark 2.4.2
Date Fri, 19 Apr 2019 23:28:41 GMT
I'm a +1
- Tested PySpark venv install and checked PKG_INFO
- Tested Spark-Testing-Base with Spark 2.4.2


On Fri, Apr 19, 2019 at 1:24 PM shane knapp <sknapp@berkeley.edu> wrote:

> oh, right.  sorry...  i don't think will cause failures (at the very least
> it'll just skip the python3 tests in python/run-tests).
>
> On Fri, Apr 19, 2019 at 12:57 PM Xiao Li <lixiao@databricks.com> wrote:
>
>> Hi, Shane,
>>
>> Based on my understanding, the update of test infra scripts does not
>> block the release of 2.4.2. Let us know whether you have any concern about
>> this.
>>
>> Cheers,
>>
>> Xiao
>>
>> On Fri, Apr 19, 2019 at 12:13 PM shane knapp <sknapp@berkeley.edu> wrote:
>>
>>> -1, as i'd like to be sure that the python test infra change for jenkins
>>> is included (https://github.com/apache/spark/pull/24379)
>>>
>>> On Fri, Apr 19, 2019 at 12:01 PM Michael Armbrust <
>>> michael@databricks.com> wrote:
>>>
>>>> +1 (binding), we've test this and it LGTM.
>>>>
>>>> On Thu, Apr 18, 2019 at 7:51 PM Wenchen Fan <cloud0fan@gmail.com>
>>>> wrote:
>>>>
>>>>> Please vote on releasing the following candidate as Apache Spark
>>>>> version 2.4.2.
>>>>>
>>>>> The vote is open until April 23 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 2.4.2
>>>>> [ ] -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 v2.4.2-rc1 (commit
>>>>> a44880ba74caab7a987128cb09c4bee41617770a):
>>>>> https://github.com/apache/spark/tree/v2.4.2-rc1
>>>>>
>>>>> The release files, including signatures, digests, etc. can be found at:
>>>>> https://dist.apache.org/repos/dist/dev/spark/v2.4.2-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-1322/
>>>>>
>>>>> The documentation corresponding to this release can be found at:
>>>>> https://dist.apache.org/repos/dist/dev/spark/v2.4.2-rc1-docs/
>>>>>
>>>>> The list of bug fixes going into 2.4.1 can be found at the following
>>>>> URL:
>>>>> https://issues.apache.org/jira/projects/SPARK/versions/12344996
>>>>>
>>>>> 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 2.4.2?
>>>>> ===========================================
>>>>>
>>>>> The current list of open tickets targeted at 2.4.2 can be found at:
>>>>> https://issues.apache.org/jira/projects/SPARK and search for "Target
>>>>> Version/s" = 2.4.2
>>>>>
>>>>> 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.
>>>>>
>>>>
>>>
>>> --
>>> Shane Knapp
>>> UC Berkeley EECS Research / RISELab Staff Technical Lead
>>> https://rise.cs.berkeley.edu
>>>
>>
>>
>> --
>> [image:
>> https://databricks.com/sparkaisummit/north-america?utm_source=email&utm_medium=signature]
>>
>
>
> --
> Shane Knapp
> UC Berkeley EECS Research / RISELab Staff Technical Lead
> https://rise.cs.berkeley.edu
>


-- 
Twitter: https://twitter.com/holdenkarau
Books (Learning Spark, High Performance Spark, etc.):
https://amzn.to/2MaRAG9  <https://amzn.to/2MaRAG9>
YouTube Live Streams: https://www.youtube.com/user/holdenkarau

Mime
View raw message