+1 (non-binding). Chao Sun <sunc...@apache.org> 于2022年1月12日周三 16:10写道：
> +1 (non-binding). Thanks Huaxin for driving the release! > > On Tue, Jan 11, 2022 at 11:56 PM Ruifeng Zheng <ruife...@foxmail.com> > wrote: > >> +1 (non-binding) >> >> Thanks, ruifeng zheng >> >> ------------------ Original ------------------ >> *From:* "Cheng Su" <chen...@fb.com.INVALID>; >> *Date:* Wed, Jan 12, 2022 02:54 PM >> *To:* "Qian Sun"<qian.sun2...@gmail.com>;"huaxin gao"< >> huaxin.ga...@gmail.com>; >> *Cc:* "dev"<dev@spark.apache.org>; >> *Subject:* Re: [VOTE] Release Spark 3.2.1 (RC1) >> >> +1 (non-binding). Checked commit history and ran some local tests. >> >> >> >> Thanks, >> >> Cheng Su >> >> >> >> *From: *Qian Sun <qian.sun2...@gmail.com> >> *Date: *Tuesday, January 11, 2022 at 7:55 PM >> *To: *huaxin gao <huaxin.ga...@gmail.com> >> *Cc: *dev <dev@spark.apache.org> >> *Subject: *Re: [VOTE] Release Spark 3.2.1 (RC1) >> >> +1 >> >> >> >> Looks good. All integration tests passed. >> >> >> >> Qian >> >> >> >> 2022年1月11日 上午2:09，huaxin gao <huaxin.ga...@gmail.com> 写道： >> >> >> >> Please vote on releasing the following candidate as Apache Spark version >> 3.2.1. >> >> >> The vote is open until Jan. 13th at 12 PM PST (8 PM UTC) 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.1 >> [ ] -1 Do not release this package because ... >> >> To learn more about Apache Spark, please see http://spark.apache.org/ >> >> There are currently no issues targeting 3.2.1 (try project = SPARK AND >> "Target Version/s" = "3.2.1" AND status in (Open, Reopened, "In >> Progress")) >> >> The tag to be voted on is v3.2.1-rc1 (commit >> 2b0ee226f8dd17b278ad11139e62464433191653): >> >> https://github.com/apache/spark/tree/v3.2.1-rc1 >> >> The release files, including signatures, digests, etc. can be found at: >> https://dist.apache.org/repos/dist/dev/spark/v3.2.1-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-1395/ >> >> The documentation corresponding to this release can be found at: >> https://dist.apache.org/repos/dist/dev/spark/v3.2.1-rc1-docs/ >> >> The list of bug fixes going into 3.2.1 can be found at the following URL: >> https://s.apache.org/7tzik >> >> This release is using the release script of the tag v3.2.1-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.2.1? >> =========================================== >> >> The current list of open tickets targeted at 3.2.1 can be found at: >> https://issues.apache.org/jira/projects/SPARK and search for "Target >> Version/s" = 3.2.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. >> >> >> >
