Hi Kousuke, I tend to agree with Sean. It only affects the macOS developers when building Spark with the released Spark 3.2 code tarball without setting JAVA_HOME. I can mention this one as a known issue in the release note if this vote passes.
Thanks, Gengliang On Mon, Sep 27, 2021 at 11:47 PM sarutak <saru...@oss.nttdata.com> wrote: > I think it affects devs but there are some workarounds. > So, if you all don't think it's necessary to meet 3.2.0, I'm OK not to > do it. > > - Kousuke > > > Hm... it does just affect Mac OS (?) and only if you don't have > > JAVA_HOME set (which people often do set) and only affects build/mvn, > > vs built-in maven (which people often have installed). Only affects > > those building. I'm on the fence about whether it blocks 3.2.0, as it > > doesn't affect downstream users and is easily resolvable. > > > > On Mon, Sep 27, 2021 at 10:26 AM sarutak <saru...@oss.nttdata.com> > > wrote: > > > >> Hi All, > >> > >> SPARK-35887 seems to have introduced another issue that building > >> with > >> build/mvn on macOS stucks, and SPARK-36856 will resolve this issue. > >> Should we meet the fix to 3.2.0? > >> > >> - Kousuke > >> > >>> Please vote on releasing the following candidate as Apache Spark > >>> version 3.2.0. > >>> > >>> The vote is open until 11:59pm Pacific time September 29 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-rc5 (commit > >>> 49aea14c5afd93ae1b9d19b661cc273a557853f5): > >>> > >>> https://github.com/apache/spark/tree/v3.2.0-rc5 > >>> > >>> The release files, including signatures, digests, etc. can be > >> found > >>> at: > >>> > >>> https://dist.apache.org/repos/dist/dev/spark/v3.2.0-rc5-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-1392 > >>> > >>> The documentation corresponding to this release can be found at: > >>> > >>> https://dist.apache.org/repos/dist/dev/spark/v3.2.0-rc5-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-rc5. > >>> > >>> 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. > >> > >> > > --------------------------------------------------------------------- > >> To unsubscribe e-mail: dev-unsubscr...@spark.apache.org >
