+1 (non-binding) On Tue, Jun 14, 2022 at 7:41 AM Dongjoon Hyun <dongjoon.h...@gmail.com> wrote:
> +1 > > Thanks, > Dongjoon. > > On Mon, Jun 13, 2022 at 3:54 PM Chris Nauroth <cnaur...@apache.org> wrote: > >> +1 (non-binding) >> >> I repeated all checks I described for RC5: >> >> https://lists.apache.org/thread/ksoxmozgz7q728mnxl6c2z7ncmo87vls >> >> Maxim, thank you for your dedication on these release candidates. >> >> Chris Nauroth >> >> >> On Mon, Jun 13, 2022 at 3:21 PM Mridul Muralidharan <mri...@gmail.com> >> wrote: >> >>> >>> +1 >>> >>> Signatures, digests, etc check out fine. >>> Checked out tag and build/tested with -Pyarn -Pmesos -Pkubernetes >>> >>> The test "SPARK-33084: Add jar support Ivy URI in SQL" in >>> sql.SQLQuerySuite fails; but other than that, rest looks good. >>> >>> Regards, >>> Mridul >>> >>> >>> >>> On Mon, Jun 13, 2022 at 4:25 PM Tom Graves <tgraves...@yahoo.com.invalid> >>> wrote: >>> >>>> +1 >>>> >>>> Tom >>>> >>>> On Thursday, June 9, 2022, 11:27:50 PM CDT, Maxim Gekk >>>> <maxim.g...@databricks.com.invalid> wrote: >>>> >>>> >>>> Please vote on releasing the following candidate as >>>> Apache Spark version 3.3.0. >>>> >>>> The vote is open until 11:59pm Pacific time June 14th 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.3.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.3.0-rc6 (commit >>>> f74867bddfbcdd4d08076db36851e88b15e66556): >>>> https://github.com/apache/spark/tree/v3.3.0-rc6 >>>> >>>> The release files, including signatures, digests, etc. can be found at: >>>> https://dist.apache.org/repos/dist/dev/spark/v3.3.0-rc6-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-1407 >>>> >>>> The documentation corresponding to this release can be found at: >>>> https://dist.apache.org/repos/dist/dev/spark/v3.3.0-rc6-docs/ >>>> >>>> The list of bug fixes going into 3.3.0 can be found at the following >>>> URL: >>>> https://issues.apache.org/jira/projects/SPARK/versions/12350369 >>>> >>>> This release is using the release script of the tag v3.3.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 a out of date RC going forward). >>>> >>>> =========================================== >>>> What should happen to JIRA tickets still targeting 3.3.0? >>>> =========================================== >>>> The current list of open tickets targeted at 3.3.0 can be found at: >>>> https://issues.apache.org/jira/projects/SPARK and search for "Target >>>> Version/s" = 3.3.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. >>>> >>>> Maxim Gekk >>>> >>>> Software Engineer >>>> >>>> Databricks, Inc. >>>> >>>
