Got it. Thank you for sharing the current status. Dongjoon.
On Fri, Apr 7, 2023 at 9:21 AM Xinrong Meng <xinrong.apa...@gmail.com> wrote: > Hi Dongjoon, > > Yes, it is. To be more specific, we failed to build documentation for RC7 > because of the sbt build outage. > > Xinrong > > On Fri, Apr 7, 2023 at 9:12 AM Dongjoon Hyun <dongjoon.h...@gmail.com> > wrote: > >> Hi, Xinrong. >> >> I saw the RC7 tag. Maybe, RC7 vote is blocked due to the on-going build >> outage? >> >> Dongjoon. >> >> >> On Thu, Apr 6, 2023 at 6:17 PM Xinrong Meng <xinrong.apa...@gmail.com> >> wrote: >> >>> Thank you! Let me recut the RC then. >>> >>> On Thu, Apr 6, 2023 at 6:14 PM Hyukjin Kwon <gurwls...@gmail.com> wrote: >>> >>>> Merged the fix. >>>> >>>> On Fri, 7 Apr 2023 at 10:07, Xinrong Meng <xinrong.apa...@gmail.com> >>>> wrote: >>>> >>>>> Thanks @yangjie01. I marked SPARK-39696 as a blocker. >>>>> >>>>> On Thu, Apr 6, 2023 at 4:35 PM yangjie01 <yangji...@baidu.com> wrote: >>>>> >>>>>> -1 for me due to this RC not include the fix of SPARK-39696, >>>>>> SPARK-39696 will fix a data race issue in access to >>>>>> TaskMetrics.externalAccums when using Scala 2.13.8 and this issue will >>>>>> cause high-frequency Executor crash when use Scala 2.13 distribution >>>>>> according to the user's description( >>>>>> https://github.com/apache/spark/pull/37206#issuecomment-1486861885). >>>>>> >>>>>> >>>>>> >>>>>> So I suggest wait for https://github.com/apache/spark/pull/40663 to >>>>>> merge and solve this issue although SPARK-39696 was not set as a blocker >>>>>> when reported. >>>>>> >>>>>> >>>>>> >>>>>> Yang Jie >>>>>> >>>>>> >>>>>> >>>>>> *发件人**: *Xinrong Meng <xinrong.apa...@gmail.com> >>>>>> *日期**: *2023年4月7日 星期五 05:27 >>>>>> *收件人**: *dev <dev@spark.apache.org> >>>>>> *主题**: *[VOTE] Release Apache Spark 3.4.0 (RC6) >>>>>> >>>>>> >>>>>> >>>>>> Please vote on releasing the following candidate(RC6) as Apache Spark >>>>>> version 3.4.0. >>>>>> >>>>>> The vote is open until 11:59pm Pacific time *April 11th* 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.4.0 >>>>>> [ ] -1 Do not release this package because ... >>>>>> >>>>>> To learn more about Apache Spark, please see http://spark.apache.org/ >>>>>> <https://mailshield.baidu.com/check?q=eJcUboQ1HRRomPZKEwRzpl69wA8DbI%2fNIiRNsQ%3d%3d> >>>>>> >>>>>> The tag to be voted on is *v3.4.0-rc6* (commit >>>>>> 28d0723beb3579c17df84bb22c98a487d7a72023): >>>>>> https://github.com/apache/spark/tree/v3.4.0-rc6 >>>>>> <https://mailshield.baidu.com/check?q=q6IQaCbJtLQ6BeenTgcIxG8X9dhmBvqXwDANXLSAGSMqLk0V8yyafD16ppQHzhGpcgUmjA%3d%3d> >>>>>> >>>>>> The release files, including signatures, digests, etc. can be found >>>>>> at: >>>>>> https://dist.apache.org/repos/dist/dev/spark/v3.4.0-rc6-bin/ >>>>>> <https://mailshield.baidu.com/check?q=tQmVBHbUjKNYfNLzXw4i8URH5h00R%2frIEMnaD0dUsWZe1afwugWVgkjLj0Xh%2bta1xgmQkU8wi4qmkyUN%2bgfxbA%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-1440 >>>>>> <https://mailshield.baidu.com/check?q=FEYGZCuDQUae2GKQUYlGjpDOevK3%2bbT5ls%2fRdaeOWDtf2dY%2fE%2bOFl539SrHZueShc5%2bKI%2bwUMph9QR4sDmEEytXXUL0Um4uC18Yl9w%3d%3d> >>>>>> >>>>>> The documentation corresponding to this release can be found at: >>>>>> https://dist.apache.org/repos/dist/dev/spark/v3.4.0-rc6-docs/ >>>>>> <https://mailshield.baidu.com/check?q=bkmfT83oWzXT1mkJ4V5sJlA0TxwMBjnHbtH8vGQwrw8SKDoUw50zFIgrmnSHvulztV3VSCfoQrZ%2bbigx0KeYUUJv8iU%3d> >>>>>> >>>>>> The list of bug fixes going into 3.4.0 can be found at the following >>>>>> URL: >>>>>> https://issues.apache.org/jira/projects/SPARK/versions/12351465 >>>>>> <https://mailshield.baidu.com/check?q=hdSxPMAr37WGNHJRNA4Mh1JkSlqjUL%2bM8BgEclwc23ePHCBzkAjvhgnZa0N7SPRWAcgfoLXjX43CxJXmKnDj0LIElJs%3d> >>>>>> >>>>>> This release is using the release script of the tag v3.4.0-rc6. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> 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.4.0? >>>>>> =========================================== >>>>>> The current list of open tickets targeted at 3.4.0 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.4.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. >>>>>> >>>>>> >>>>>> >>>>>> Thanks, >>>>>> >>>>>> Xinrong Meng >>>>>> >>>>>> >>>>>> >>>>>
