spark-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kazuaki Ishizaki" <>
Subject Re: [VOTE] Release Apache Spark 2.3.4 (RC1)
Date Tue, 27 Aug 2019 01:50:13 GMT
Thank you for pointing out the problem.
The characters and hyperlink point different URLs.

Could you please access as 
you see characters?

Sorry for your inconvenience.
Kazuaki Ishizaki,

From:   Takeshi Yamamuro <>
To:     Kazuaki Ishizaki <>
Cc:     Apache Spark Dev <>
Date:   2019/08/27 08:49
Subject:        Re: [VOTE] Release Apache Spark 2.3.4 (RC1)


Thanks for the release manage!
It seems the staging repository has not been exposed yet?

On Tue, Aug 27, 2019 at 5:28 AM Kazuaki Ishizaki <> 
Please vote on releasing the following candidate as Apache Spark version 

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

The tag to be voted on is v2.3.4-rc1 (commit 

The release files, including signatures, digests, etc. can be found at:

Signatures used for Spark RCs can be found in this file:

The staging repository for this release can be found at:

The documentation corresponding to this release can be found at:

The list of bug fixes going into 2.3.4 can be found at the following URL:


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: 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.

Takeshi Yamamuro

View raw message