Just noticed something before I started to run some tests. The output
of "spark-submit --version" is a little weird, in that it's missing
information (see end of e-mail).
Personally I don't think a lot of that output is super useful (like
"Compiled by" or the repo URL), but the branch and revision are.
Could be an artifact of the docker-based build scripts. I don't think
it should block the release, but we should fix that.
$ spark2-submit --version
Welcome to
____ __
/ __/__ ___ _____/ /__
_\ \/ _ \/ _ `/ __/ '_/
/___/ .__/\_,_/_/ /_/\_\ version 2.3.4
/_/
Using Scala version 2.11.8, Java HotSpot(TM) 64-Bit Server VM, 1.8.0_111
Branch
Compiled by user on 2019-08-26T08:09:33Z
Revision
Url
Type --help for more information.
On Mon, Aug 26, 2019 at 1: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.
>
--
Marcelo
---------------------------------------------------------------------
To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
