Hi Tom, I will cut RC3 right after SPARK-36772 <https://issues.apache.org/jira/browse/SPARK-36772>is resolved.
Thanks, Gengliang On Fri, Sep 17, 2021 at 10:03 PM Tom Graves <tgraves...@yahoo.com> wrote: > Hey folks, > > just curious what the status was on doing an rc3? I didn't see any > blockers left since it looks like parquet change got merged. > > Thanks, > Tom > > On Thursday, September 9, 2021, 12:27:58 PM CDT, Mridul Muralidharan < > mri...@gmail.com> wrote: > > > > I have filed a blocker, SPARK-36705 > <https://issues.apache.org/jira/browse/SPARK-36705> which will need to be > addressed. > > Regards, > Mridul > > > On Sun, Sep 5, 2021 at 8:47 AM Gengliang Wang <ltn...@gmail.com> wrote: > > Hi all, > > the voting fails. > Liang-Chi reported a new block SPARK-36669 > <https://issues.apache.org/jira/browse/SPARK-36669>. We will have RC3 > when the existing issues are resolved. > > > On Thu, Sep 2, 2021 at 5:01 AM Sean Owen <sro...@gmail.com> wrote: > > This RC looks OK to me too, understanding we may need to have RC3 for the > outstanding issues though. > > The issue with the Scala 2.13 POM is still there; I wasn't able to figure > it out (anyone?), though it may not affect 'normal' usage (and is > work-around-able in other uses, it seems), so may be sufficient if Scala > 2.13 support is experimental as of 3.2.0 anyway. > > > On Wed, Sep 1, 2021 at 2:08 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 September 3 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-rc2 (commit > 6bb3523d8e838bd2082fb90d7f3741339245c044): > https://github.com/apache/spark/tree/v3.2.0-rc2 > > The release files, including signatures, digests, etc. can be found at: > https://dist.apache.org/repos/dist/dev/spark/v3.2.0-rc2-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-1389 > > The documentation corresponding to this release can be found at: > https://dist.apache.org/repos/dist/dev/spark/v3.2.0-rc2-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-rc2. > > > 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. > >
