+1, thank you, Haejoon
Kent

On 2024/09/11 06:12:19 Gengliang Wang wrote:
> +1
> 
> On Mon, Sep 9, 2024 at 6:01 PM Wenchen Fan <cloud0...@gmail.com> wrote:
> 
> > +1
> >
> > On Tue, Sep 10, 2024 at 7:42 AM Rui Wang <rui.w...@databricks.com.invalid>
> > wrote:
> >
> >> +1 (non-binding)
> >>
> >>
> >> -Rui
> >>
> >> On Mon, Sep 9, 2024 at 4:22 PM Hyukjin Kwon <gurwls...@apache.org> wrote:
> >>
> >>> +1
> >>>
> >>> On Tue, Sep 10, 2024 at 5:39 AM Haejoon Lee
> >>> <haejoon....@databricks.com.invalid> wrote:
> >>>
> >>>> Hi, dev!
> >>>>
> >>>> Please vote on releasing the following candidate as Apache Spark
> >>>> version 3.5.3 (RC3).
> >>>>
> >>>> The vote is open for next 72 hours, 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.5.3
> >>>> [ ] -1 Do not release this package because ...
> >>>>
> >>>> To learn more about Apache Spark, please see https://spark.apache.org/
> >>>>
> >>>> The tag to be voted on is v3.5.3-rc3 (commit
> >>>> 32232e9ed33bb16b93ad58cfde8b82e0f07c0970):
> >>>> https://github.com/apache/spark/tree/v3.5.3-rc3
> >>>>
> >>>> The release files, including signatures, digests, etc. can be found at:
> >>>> https://dist.apache.org/repos/dist/dev/spark/v3.5.3-rc3-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-1467/
> >>>>
> >>>> The documentation corresponding to this release can be found at:
> >>>> https://dist.apache.org/repos/dist/dev/spark/v3.5.3-rc3-docs/
> >>>>
> >>>> The list of bug fixes going into 3.5.3 can be found at the following
> >>>> URL:
> >>>> https://issues.apache.org/jira/projects/SPARK/versions/12354954
> >>>>
> >>>> 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 via "pip install
> >>>> https://dist.apache.org/repos/dist/dev/spark/v3.5.3-rc3-bin/pyspark-3.5.3.tar.gz
> >>>> "
> >>>> 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.5.3?
> >>>> ===========================================
> >>>>
> >>>> The current list of open tickets targeted at 3.5.3 can be found at:
> >>>> https://issues.apache.org/jira/projects/SPARK and search for
> >>>> "Target Version/s" = 3.5.3
> >>>>
> >>>> 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.
> >>>>
> >>>> Thanks!
> >>>> Haejoon Lee
> >>>>
> >>>
> 

---------------------------------------------------------------------
To unsubscribe e-mail: dev-unsubscr...@spark.apache.org

Reply via email to