+1 (non-binding)

Passed integration test with Apache Kyuubi.

Thanks for driving this release.

Thanks,
Cheng Pan


> On Aug 11, 2023, at 06:36, L. C. Hsieh <vii...@gmail.com> wrote:
> 
> +1
> 
> Thanks Yuming.
> 
> On Thu, Aug 10, 2023 at 3:24 PM Dongjoon Hyun <dongj...@apache.org> wrote:
>> 
>> +1
>> 
>> Dongjoon
>> 
>> On 2023/08/10 07:14:07 yangjie01 wrote:
>>> +1
>>> Thanks, Jie Yang
>>> 
>>> 
>>> 发件人: Yuming Wang <yumw...@apache.org>
>>> 日期: 2023年8月10日 星期四 13:33
>>> 收件人: Dongjoon Hyun <dongjoon.h...@gmail.com>
>>> 抄送: dev <dev@spark.apache.org>
>>> 主题: Re: [VOTE] Release Apache Spark 3.3.3 (RC1)
>>> 
>>> +1 myself.
>>> 
>>> On Tue, Aug 8, 2023 at 12:41 AM Dongjoon Hyun 
>>> <dongjoon.h...@gmail.com<mailto:dongjoon.h...@gmail.com>> wrote:
>>> Thank you, Yuming.
>>> 
>>> Dongjoon.
>>> 
>>> On Mon, Aug 7, 2023 at 9:30 AM yangjie01 
>>> <yangji...@baidu.com<mailto:yangji...@baidu.com>> wrote:
>>> HI,Dongjoon and Yuming
>>> 
>>> I submitted a PR a few days ago to try to fix this issue: 
>>> https://github.com/apache/spark/pull/42167<https://mailshield.baidu.com/check?q=zJC5kBC6NRCGy3lXApap3GX6%2bKB9Gi%2b%2fTr0LBfwtxiuVHIiRznzQ7iofG2KJFsJB>.
>>>  The reason for the failure is that the branch daily test and the master 
>>> use the same yml file.
>>> 
>>> Jie Yang
>>> 
>>> 发件人: Dongjoon Hyun <dongjoon.h...@gmail.com<mailto:dongjoon.h...@gmail.com>>
>>> 日期: 2023年8月8日 星期二 00:18
>>> 收件人: Yuming Wang <yumw...@apache.org<mailto:yumw...@apache.org>>
>>> 抄送: dev <dev@spark.apache.org<mailto:dev@spark.apache.org>>
>>> 主题: Re: [VOTE] Release Apache Spark 3.3.3 (RC1)
>>> 
>>> Hi, Yuming.
>>> 
>>> One of the community GitHub Action test pipelines is unhealthy consistently 
>>> due to Python mypy linter.
>>> 
>>> https://github.com/apache/spark/actions/workflows/build_branch33.yml<https://mailshield.baidu.com/check?q=zL6yo8WBsL15wzkqifGHCZlkv7KqucJxpuNp8neenIT6Re6167OIO8%2fCYlTH0k%2b29wZ%2fDuFIdfwQCHRIDBzTS292DGk6EvIh>
>>> 
>>> It seems due to the pipeline difference between the same Python mypy linter 
>>> already pass in commit build,
>>> 
>>> Dongjoon.
>>> 
>>> 
>>> On Fri, Aug 4, 2023 at 8:09 PM Yuming Wang 
>>> <yumw...@apache.org<mailto:yumw...@apache.org>> wrote:
>>> Please vote on releasing the following candidate as Apache Spark version 
>>> 3.3.3.
>>> 
>>> The vote is open until 11:59pm Pacific time August 10th 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.3.3
>>> [ ] -1 Do not release this package because ...
>>> 
>>> To learn more about Apache Spark, please see 
>>> https://spark.apache.org<https://mailshield.baidu.com/check?q=cUpKoLnajWahunV4UDIAXHiHyx%2f5wSVGtwwdag%3d%3d>
>>> 
>>> The tag to be voted on is v3.3.3-rc1 (commit 
>>> 8c2b3319c6734250ff9d72f3d7e5cab56b142195):
>>> https://github.com/apache/spark/tree/v3.3.3-rc1<https://mailshield.baidu.com/check?q=8FCIKpLCdZkaDTtrM2i6z6MozYaNPIUxXbtoz6UY4Dd9HDZ%2fGD1yoiMERdI6DE0Tv%2bgl0w%3d%3d>
>>> 
>>> The release files, including signatures, digests, etc. can be found at:
>>> https://dist.apache.org/repos/dist/dev/spark/v3.3.3-rc1-bin<https://mailshield.baidu.com/check?q=E6K9wCUIl7R2GWg35cz6FTdyOlAIldH1DzrC5lMm5vEz7tsnGbtOoOh3Xhjgt%2bKmRTfJyMzbsWs8FQuvjrnyEw%3d%3d>
>>> 
>>> Signatures used for Spark RCs can be found in this file:
>>> https://dist.apache.org/repos/dist/dev/spark/KEYS<https://mailshield.baidu.com/check?q=E6fHbSXEWw02TTJBpc3bfA9mi7ea0YiWcNHkm%2fDJxwlaWinGnMdaoO1PahHhgj00vKwcbElpuHA%3d>
>>> 
>>> The staging repository for this release can be found at:
>>> https://repository.apache.org/content/repositories/orgapachespark-1445<https://mailshield.baidu.com/check?q=qwIV%2bgL7su%2fhDHaSq3L7D4SvWg6hop35lQ6SmnXKIqkCT%2b5Z2apQOzuDyyPx6aoUTTbwled13%2b5ajYiObU6S6Fie%2bMXccPyMOLOrKg%3d%3d>
>>> 
>>> The documentation corresponding to this release can be found at:
>>> https://dist.apache.org/repos/dist/dev/spark/v3.3.3-rc1-docs<https://mailshield.baidu.com/check?q=8J9mpKGDzLZWyCARq00pdYmMTZ7Xg2gOIhMdnfDmdhOphsDhxGAe3BboUHQltnOgRUrIx2ycA8%2b%2fDX2SG1gd6g%3d%3d>
>>> 
>>> The list of bug fixes going into 3.3.3 can be found at the following URL:
>>> https://s.apache.org/rjci4<https://mailshield.baidu.com/check?q=CDSiusCyO4bcrg80RMEGb9gnL5P2xcxAWMuq6OOUhbc%3d>
>>> 
>>> This release is using the release script of the tag v3.3.3-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 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.3.3?
>>> ===========================================
>>> The current list of open tickets targeted at 3.3.3 can be found at:
>>> https://issues.apache.org/jira/projects/SPARK<https://mailshield.baidu.com/check?q=4UUpJqq41y71Gnuj0qTUYo6hTjqzT7oytN6x%2fvgC5XUtQUC8MfJ77tj7K70O%2f1QMmNoa1A%3d%3d>
>>>  and search for "Target Version/s" = 3.3.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.
>>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
>> 
> 
> ---------------------------------------------------------------------
> To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
> 


---------------------------------------------------------------------
To unsubscribe e-mail: dev-unsubscr...@spark.apache.org

Reply via email to