+1
Tests are running fine, docs look good. Should be good to go.

Thanks and Regards,
Shrinidhi kanchi
+4915218336840

On Wed, 28 Aug 2019, 10:17 Marco Gaido, <marcogaid...@gmail.com> wrote:

> +1
>
> Il giorno mer 28 ago 2019 alle ore 06:31 Wenchen Fan <cloud0...@gmail.com>
> ha scritto:
>
>> +1
>>
>> On Wed, Aug 28, 2019 at 2:43 AM DB Tsai <dbt...@dbtsai.com.invalid>
>> wrote:
>>
>>> +1
>>>
>>> Sincerely,
>>>
>>> DB Tsai
>>> ----------------------------------------------------------
>>> Web: https://www.dbtsai.com
>>> PGP Key ID: 42E5B25A8F7A82C1
>>>
>>> On Tue, Aug 27, 2019 at 11:31 AM Dongjoon Hyun <dongjoon.h...@gmail.com>
>>> wrote:
>>> >
>>> > +1.
>>> >
>>> > I also verified SHA/GPG and tested UTs on AdoptOpenJDKu8_222/CentOS6.9
>>> with profile
>>> > "-Pyarn -Phadoop-2.7 -Pkubernetes -Pkinesis-asl -Phive
>>> -Phive-thriftserver"
>>> >
>>> > Additionally, JDBC IT also is tested.
>>> >
>>> > Thank you, Kazuaki!
>>> >
>>> > Bests,
>>> > Dongjoon.
>>> >
>>> >
>>> > On Tue, Aug 27, 2019 at 11:20 AM Sean Owen <sro...@apache.org> wrote:
>>> >>
>>> >> +1 - license and signature looks OK, the docs look OK, the artifacts
>>> >> seem to be in order. Tests passed for me when building from source
>>> >> with most common profiles set.
>>> >>
>>> >> On Mon, Aug 26, 2019 at 3:28 PM Kazuaki Ishizaki <ishiz...@jp.ibm.com>
>>> wrote:
>>> >> >
>>> >> > Please vote on releasing the following candidate as Apache Spark
>>> version 2.3.4.
>>> >> >
>>> >> > The vote is open until August 29th 2PM PST and passes if a majority
>>> +1 PMC votes are cast, with
>>> >> > a minimum of 3 +1 votes.
>>> >> >
>>> >> > [ ] +1 Release this package as Apache Spark 2.3.4
>>> >> > [ ] -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 v2.3.4-rc1 (commit
>>> 8c6f8150f3c6298ff4e1c7e06028f12d7eaf0210):
>>> >> > https://github.com/apache/spark/tree/v2.3.4-rc1
>>> >> >
>>> >> > The release files, including signatures, digests, etc. can be found
>>> at:
>>> >> > https://dist.apache.org/repos/dist/dev/spark/v2.3.4-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-1331/
>>> >> >
>>> >> > The documentation corresponding to this release can be found at:
>>> >> > https://dist.apache.org/repos/dist/dev/spark/v2.3.4-rc1-docs/
>>> >> >
>>> >> > The list of bug fixes going into 2.3.4 can be found at the
>>> following URL:
>>> >> > https://issues.apache.org/jira/projects/SPARK/versions/12344844
>>> >> >
>>> >> > 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 2.3.4?
>>> >> > ===========================================
>>> >> >
>>> >> > The current list of open tickets targeted at 2.3.4 can be found at:
>>> >> > https://issues.apache.org/jira/projects/SPARKand search for
>>> "Target Version/s" = 2.3.4
>>> >> >
>>> >> > 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
>>> >>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
>>>
>>>

Reply via email to