+1 (non-binding). Peter
On Fri, Oct 8, 2021 at 9:16 AM Cheng Su <chen...@fb.com.invalid> wrote: > +1 (non-binding). > > > > Thanks, > > Cheng Su > > > > *From: *Reynold Xin <r...@databricks.com> > *Date: *Thursday, October 7, 2021 at 11:57 PM > *To: *Yuming Wang <wgy...@gmail.com> > *Cc: *Dongjoon Hyun <dongjoon.h...@gmail.com>, 郑瑞峰 <ruife...@foxmail.com>, > Sean Owen <sro...@gmail.com>, Gengliang Wang <ltn...@gmail.com>, dev < > dev@spark.apache.org> > *Subject: *Re: [VOTE] Release Spark 3.2.0 (RC7) > > +1 > > [image: Image removed by sender.] > > > > > > On Thu, Oct 07, 2021 at 11:54 PM, Yuming Wang <wgy...@gmail.com> wrote: > > +1 (non-binding). > > > > On Fri, Oct 8, 2021 at 1:02 PM Dongjoon Hyun <dongjoon.h...@gmail.com> > wrote: > > +1 for Apache Spark 3.2.0 RC7. > > > > It looks good to me. I tested with EKS 1.21 additionally. > > > > Cheers, > > Dongjoon. > > > > > > On Thu, Oct 7, 2021 at 7:46 PM 郑瑞峰 <ruife...@foxmail.com> wrote: > > +1 (non-binding) > > > > > > ------------------ 原始邮件 ------------------ > > *发件人**:* "Sean Owen" <sro...@gmail.com>; > > *发送时间**:* 2021年10月7日(星期四) 晚上10:23 > > *收件人**:* "Gengliang Wang"<ltn...@gmail.com>; > > *抄送**:* "dev"<dev@spark.apache.org>; > > *主题**:* Re: [VOTE] Release Spark 3.2.0 (RC7) > > > > +1 again. Looks good in Scala 2.12, 2.13, and in Java 11. > > I note that the mem requirements for Java 11 tests seem to need to be > increased but we're handling that separately. It doesn't really affect > users. > > > > On Wed, Oct 6, 2021 at 11:49 AM Gengliang Wang <ltn...@gmail.com> wrote: > > Please vote on releasing the following candidate as > Apache Spark version 3.2.0. > > > > The vote is open until 11:59pm Pacific time October 11 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.2.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.2.0-rc7 (commit > 5d45a415f3a29898d92380380cfd82bfc7f579ea): > > https://github.com/apache/spark/tree/v3.2.0-rc7 > > > > The release files, including signatures, digests, etc. can be found at: > > https://dist.apache.org/repos/dist/dev/spark/v3.2.0-rc7-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-1394 > > > > The documentation corresponding to this release can be found at: > > https://dist.apache.org/repos/dist/dev/spark/v3.2.0-rc7-docs/ > > > > The list of bug fixes going into 3.2.0 can be found at the following URL: > > https://issues.apache.org/jira/projects/SPARK/versions/12349407 > > > > This release is using the release script of the tag v3.2.0-rc7. > > > > > > 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 3.2.0? > > =========================================== > > The current list of open tickets targeted at 3.2.0 can be found at: > > https://issues.apache.org/jira/projects/SPARK and search for "Target > Version/s" = 3.2.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. > > >
